.claude/skills/self-assessment/SKILL.md
Comprehensive Claude Code self-assessment and learning path advisor. Runs a multi-category quiz covering 10 feature areas, produces a detailed skill profile with per-topic scores, identifies specific gaps, and generates a personalized learning path with prioritized next steps. Use when asked to "assess my level", "take the quiz", "find my level", "where should I start", "what should I learn next", "check my skills", "skill check", or "level up".
npx skillsauth add luongnv89/claude-howto self-assessmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive interactive assessment that evaluates Claude Code proficiency across 10 feature areas, identifies specific skill gaps, and generates a personalized learning path to level up.
Present the user with a choice of assessment depth:
Use AskUserQuestion with these options:
If user chooses Quick Assessment, go to Step 2A. If user chooses Deep Assessment, go to Step 2B.
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:
claude and interact with itQuestion 2 (header: "Advanced"): "Part 2/2: Which of these advanced skills do you have?" Options:
claude -p for non-interactive or CI/CD useScoring:
Go to Step 3 with the level result, listing which specific items were NOT checked as gaps.
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." Options:
$ARGUMENTS, $0/$1, backtick !command syntax, or @file references in skill/command filesScoring for Round 1:
Round 2 — Skills & Hooks (header: "Automation")
"Which of these have you done? Select all that apply." Options:
disable-model-invocation, user-invocable, or context: fork with agent field in SKILL.md frontmatterScoring for Round 2:
Round 3 — MCP & Subagents (header: "Integration")
"Which of these have you done? Select all that apply." Options:
claude mcp serveTask(agent_name), or agent teamsScoring for Round 3:
Round 4 — Checkpoints & Advanced Features (header: "Power User")
"Which of these have you done? Select all that apply." Options:
claude remote-control, claude --remote, /teleport, /desktop, or worktrees with claude -wScoring for Round 4:
Round 5 — Plugins & CLI (header: "Mastery")
"Which of these have you done? Select all that apply." Options:
claude -p with --output-format json, --max-turns, piped input, or integrated into GitHub Actions / CI pipelinesScoring for Round 5:
Count total selections and determine level. Then present:
## Claude Code Skill Assessment Results
### Your Level: [Level 1: Beginner / Level 2: Intermediate / Level 3: Advanced]
You checked **N/8** items.
[One-line motivational summary based on level]
### Your Skill Profile
| Area | Status |
|------|--------|
| Basic CLI & Conversations | [Checked/Gap] |
| CLAUDE.md & Memory | [Checked/Gap] |
| Slash Commands (built-in) | [Checked/Gap] |
| Custom Commands & Skills | [Checked/Gap] |
| MCP Servers | [Checked/Gap] |
| Hooks | [Checked/Gap] |
| Subagents | [Checked/Gap] |
| Print Mode & CI/CD | [Checked/Gap] |
### Identified Gaps
[For each unchecked item, provide a 1-line description of what to learn and a link to the tutorial]
### Your Personalized Learning Path
[Output the level-specific learning path — see Step 4]
Calculate per-topic scores from the 5 rounds. Each topic gets 0-2 points. Then present:
## Claude Code Skill Assessment Results
### Overall Level: [Level 1 / Level 2 / Level 3]
**Total Score: N/20 points**
[One-line motivational summary]
### Your Skill Profile
| Feature Area | Score | Mastery | Status |
|-------------|-------|---------|--------|
| Slash Commands | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| Memory | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| Skills | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| Hooks | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| MCP | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| Subagents | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| Checkpoints | N/1 | [None/Proficient] | [Learn/Mastered] |
| Advanced Features | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| Plugins | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
| CLI | N/2 | [None/Basic/Proficient] | [Learn/Review/Mastered] |
**Mastery key:** 0 = None, 1 = Basic, 2 = Proficient
### Strength Areas
[List topics with score 2/2 — these are mastered]
### Priority Gaps (Learn Next)
[List topics with score 0 — these need attention first, ordered by dependency]
### Review Areas
[List topics with score 1/2 — basics known but advanced features not yet used]
### Your Personalized Learning Path
[Output gap-specific learning path — see Step 4]
Overall level calculation for Deep Assessment:
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.
### Your Personalized Learning Path
**Estimated time**: ~N hours (adjusted for your current skills)
#### Phase 1: [Phase Name] (~N hours)
[Only if they have gaps in these areas]
**[Topic Name]** — [Learn from scratch / Deep dive into advanced features]
- Tutorial: [link to tutorial directory]
- Focus on: [specific sections/concepts they need]
- Key exercise: [one concrete exercise to do]
- You'll know it's done when: [specific success criterion]
**[Topic Name]** — ...
---
#### Phase 2: [Phase Name] (~N hours)
...
---
### Recommended Practice Projects
Based on your gaps, try these real-world exercises to solidify your learning:
1. **[Project name]**: [1-line description combining 2-3 gap topics]
2. **[Project name]**: [1-line description]
3. **[Project name]**: [1-line description]
Use these specific recommendations when a topic is a gap:
Slash Commands (score 0):
$ARGUMENTS syntax/optimize command and test itSlash Commands (score 1 — review):
!backtick`` syntax, @file references, disable-model-invocation vs user-invocable controlMemory (score 0):
/init and /memory commands, # prefix for quick updatesMemory (score 1 — review):
@import syntax (max depth 5), Auto Memory MEMORY.md (200-line limit)Skills (score 0):
Skills (score 1 — review):
context: fork with agent field for subagent execution, disable-model-invocation vs user-invocable, 2% context budget, bundled resources (scripts/, references/, assets/)Hooks (score 0):
Hooks (score 1 — review):
CLAUDE_ENV_FILE for SessionStart/CwdChanged/FileChangedMCP (score 0):
claude mcp add command, transport types (HTTP recommended), GitHub MCP setup, environment variable expansionMCP (score 1 — review):
@server:resource mentions, Tool Search (ENABLE_TOOL_SEARCH), claude mcp serve, output limits (10k/25k/50k)Subagents (score 0):
Subagents (score 1 — review):
isolation: worktree), persistent agent memory (memory field with scopes), background agents (Ctrl+B/Ctrl+F), agent allowlists with Task(agent_name), agent teams (--teammate-mode)Checkpoints (score 0):
Advanced Features (score 0):
Advanced Features (score 1 — review):
claude remote-control), web sessions (claude --remote), desktop handoff (/desktop), worktrees (claude -w), task lists (Ctrl+T), managed settings for enterprisePlugins (score 0):
Plugins (score 1 — review):
${CLAUDE_PLUGIN_ROOT} variable, --plugin-dir for testing, marketplace publishingCLI (score 0):
claude -p with piping, --output-format json, session management (-c/-r)claude -p and get JSON outputCLI (score 1 — review):
claude mcp serveAfter presenting results, ask the user what they'd like to do next:
Use AskUserQuestion with these options:
If Start learning: Read the README.md of the first gap tutorial and walk the user through the first exercise. If Deep dive on a gap: Ask which gap topic, then read the relevant tutorial README.md and explain the key concepts with examples. If Practice project: Design a small project that combines 2-3 of their gap topics with concrete steps. If Retake assessment: Go back to Step 1.
Treat as 0 points for that round's topics. Continue to next round.
Assign Level 1: Beginner. Encourage starting from the beginning. Output the full Level 1 path.
Re-run from Step 1 with a fresh assessment.
Acknowledge their preference. Ask which level they identify with. Present the path for their chosen level with a prerequisites check for topics they may have missed.
If the user says something like "tell me about hooks" or "I want to learn MCP" during the assessment, note it. After presenting results, highlight that topic in their learning path regardless of score.
Should trigger:
Should NOT trigger:
development
Comprehensive code review with security, performance, and quality analysis. Use when users ask to review code, analyze code quality, evaluate pull requests, or mention code review, security analysis, or performance optimization.
development
<!-- i18n-source: 03-skills/refactor/SKILL.md --> <!-- i18n-source-sha: 245272f --> <!-- i18n-date: 2026-04-27 --> --- name: refactor description: Martin Fowler の方法論に基づく体系的なコードリファクタリング。ユーザーがコードのリファクタリング、コード構造の改善、技術的負債の削減、レガシーコードのクリーンアップ、コードスメルの解消、コード保守性の向上を求めた際に使用する。本スキルは、リサーチ・計画・安全な段階的実装からなる段階的アプローチを案内する。 --- # コードリファクタリングスキル Martin Fowler 著『Refactoring: Improving the Design of Existing Code』(第 2 版) に基づくコードリファクタリングへの体系的アプローチ。本スキルは、テストに支えられた安全で段階的な変更を重視する。 > "Refactoring is the process of cha
development
<!-- i18n-source: 03-skills/doc-generator/SKILL.md --> <!-- i18n-source-sha: a6380d8 --> <!-- i18n-date: 2026-04-27 --> --- name: doc-generator description: ソースコードから包括的かつ正確な API ドキュメントを生成する。API ドキュメントの作成・更新、OpenAPI 仕様の生成時、または API ドキュメント、エンドポイント、ドキュメントについて言及がある場合に使用する。 --- # API ドキュメント生成スキル ## 生成するもの - OpenAPI/Swagger 仕様 - API エンドポイントのドキュメント - SDK 利用例 - 統合ガイド - エラーコード・リファレンス - 認証ガイド ## ドキュメント構造 ### 各エンドポイントごと ````markdown ## GET /api/v1/users/:id ### Description このエンドポイントの動作を簡潔に説明 ### Pa
development
<!-- i18n-source: 03-skills/claude-md/SKILL.md --> <!-- i18n-source-sha: f78c094 --> <!-- i18n-date: 2026-04-27 --> --- name: claude-md description: Create or update CLAUDE.md files following best practices for optimal AI agent onboarding --- ## ユーザー入力 ```text $ARGUMENTS ``` ユーザー入力が空でない場合、進める前に **必ず** 内容を考慮すること。ユーザーは以下を指定する場合がある: - `create` - 新しい CLAUDE.md をゼロから作成 - `update` - 既存 CLAUDE.md を改善 - `audit` - 現在の CLAUDE.md の品質を分析しレポート - 作成・更新する具体的なパス(例: ディレクトリ固有命令向けの `src/api/CLAUDE.md`) ## 基本原則