Sensei check
Validate Sensei setup — confirms CONFIG.md, character, safeword, ROADMAP.md, and PROGRESS.md are presentFrom its SKILL.md
npx -y skills add jreynolds-dev/sensei --skill sensei-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
Check the current project's Sensei setup and print a validation summary.
Look for the following in the current working directory and report the status of each:
.sensei/CONFIG.md— Does it exist? Does it contain a## Character:line? What character is selected?- Safeword — Does
.sensei/CONFIG.mdcontain a## Safeword:line? What is the configured safeword? - Demo Trigger — Does
.sensei/CONFIG.mdcontain a## Demo Trigger:line? What is the configured trigger? ROADMAP.md— Does it exist in the project root?.sensei/PROGRESS.md— Does it exist? If so, how many skill domains are tracked?.sensei/COMMANDS.md— Does it exist?
Print results in this format, substituting actual values:
Sensei — Setup Check
──────────────────────────────
Config file found: ✓ / ✗
Character selected: ✓ splinter / ✗ not configured
Safeword configured: ✓ hamato / ✗ not set
Demo trigger configured: ✓ show me, sensei / ✗ not set
ROADMAP.md found: ✓ / ✗
Progress file found: ✓ (N domains tracked) / ✗ (created on first /dojo-open)
Commands file found: ✓ / ✗
──────────────────────────────
If any item shows ✗ that would block teaching, add a one-line fix hint below the table. For example:
- Missing
.sensei/CONFIG.md→ "Run/setupto initialize the dojo." - Character not configured → "Run
/setupto select a character." - Missing ROADMAP.md → "Run
/setupto generate a learning roadmap."
Do not invent values. Only report what you can confirm by reading the files.