Menü
Change your curriculum experience level (beginner / intermediate / advanced) mid-course. Takes effect immediately.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | experience |
| description | Change your curriculum experience level (beginner / intermediate / advanced) mid-course. Takes effect immediately. |
| disable-model-invocation | true |
The learner picked an experience level during /start onboarding. This skill lets them adjust it mid-course without restarting. Level changes are normal — treat them as a calibration, not a confession of difficulty. Do NOT say "no shame in either direction" or similar framing to the user; the skill should just make the change and confirm it.
Read CLAUDE.local.md from the cc-self-train root. Find the Experience Level line (e.g., Experience Level: beginner). If the file doesn't exist, say: "I don't see an active project yet. Run /start first — it collects your experience level as part of onboarding."
Ask using AskUserQuestion:
New — "Bootcamp grad, student, or first dev tools. We'll explain every concept and pace slowly."Some experience — "1-3 years professional. We'll skip git basics and setup, move faster."Experienced — "3+ years, comfortable with terminals/git/package managers. Straight to CC-specific depth."Map the choice to a level:
New → beginnerSome experience → intermediateExperienced → advancedUpdate CLAUDE.local.md. Rewrite the Experience Level: line with the new value. If the file contains an Effective Level: line, rewrite that to match too — the adaptive system may re-adjust Effective Level on the next module boundary based on engagement patterns, and that's fine. This just resets the baseline.
Print ONE short confirmation line:
"Got it — I'll teach at the level from here. Change again anytime with
/experience."
Where <new level> is beginner, intermediate, or advanced (lowercase).
Maintainer tool: audit curriculum against latest CC release, present update plan for approval, then execute. Does NOT commit.
Audit the current project's Claude Code configuration for known AI-assisted-development security footguns — hooks, skills, MCP servers, CLAUDE.md — and report findings with severity and remediation.
Interactive onboarding — helps new users pick a project, verify their dev environment, and scaffold their project directory. Run this when someone first opens Claude Code in this repo.
Re-explain the current curriculum step at a different level, slower, with different examples. Use whenever you feel lost — no judgment, no "try harder."
Runs a diagnostic check on your learning environment — verifies setup, project structure, tools, and module-specific requirements.
Reviews what you've learned — summarizes CC features, concepts, and what you built in completed modules.