self assessment

Engineering Community v2.3.0

Skill notes

Step 1: Welcome & Choose Assessment Mode

Present the user with a choice of assessment depth: Use AskUserQuestion with these options: Quick Assessment — "8 questions, ~2 minutes. Determines your overall level (Beginner/Intermediate/Advanced) and gives a learning path." Deep Assessment — "5 categories with detailed questions, ~5 minutes. Gives per-topic skill scores, identifies specific gaps, and builds a prioritized learning path." If user chooses Quick Assessment, go to Step 2A.

Step 2A: Quick Assessment

Present TWO multi-select questions (AskUserQuestion supports max 4 options each): Question 1 (header: "Basics"): "Part 1/2: Which of these Claude Code skills do you already have?" Options: "Start Claude Code and chat" — I can run claude and interact with it

Step 2B: Deep Assessment

Present 5 rounds of questions, one AskUserQuestion call per round. Each round covers 2 related feature areas. Use multi-select for all rounds. IMPORTANT: AskUserQuestion supports max 4 options per question. Each round has exactly 1 question with 4 options covering 2 topics (2 options per topic). Round 1 — Slash Commands & Memory (header: "Commands") "Which of these have you done? Select all that apply."

Step 3: Calculate & Present Results

3A: For Quick Assessment Count total selections and determine level. Then present: 3B: For Deep Assessment Calculate per-topic scores from the 5 rounds. Each topic gets 0-2 points. Then present: Overall level calculation for Deep Assessment:

Step 4: Generate Personalized Learning Path

Based on the assessment results, generate a learning path that is specific to the user's gaps. Do NOT just repeat the generic level path — adapt it. Rules for Path Generation Skip mastered topics: If a topic scored 2/2, do not include it in the path. Prioritize by dependency order: Slash Commands before Skills, Memory before Subagents, etc. The dependency order is: Slash Commands (no deps) -> Skills (depends on Slash Commands)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@luongnv89 · v2.3.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview self-assessment.preview
# Step 3: Calculate & Present Results

#### 3A: For Quick Assessment Count total selections and determine level. Then present: ```markdown

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.