Use when the user asks to practice programming with dsh-tui, or wants to level up a specific skill through guided exercises.
NewMaintained
Automatic
◆Tutoring & Education pack
Last verified 9/9/2026
What it changes
Passed 9 of 22 test cases with the skill, and 13 of 22 without it.
Without skill60%
With skill40%
Checks it passed that the model alone missed
Presents exactly one micro-exercise rather than a multi-step curriculum.
Evaluates the submitted result before introducing a harder exercise variation.
2 fixed9 passed either way8 still failing3 broke
Pass-rate lift
-20 pp
Tokens
-32%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 9/9/2026v211 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I just completed the basic string reversal exercise in Go. I'm ready for the next step.
What was checked, without and with the skill
Checked
Without skill
With skill
Evaluates the submitted result before introducing a harder exercise variation.
Missed
Passed
case-10 · gemini-3.6-flash · 9/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md10 linessingle file
Help the user learn one concept through a small exercise and feedback. Use their stated goal, level, and time budget; ask only when the missing context changes the exercise.
Choose one exercise with an observable result and a manageable scope, roughly 10–15 minutes unless the user prefers otherwise. Use relevant project code when it helps, and keep exercise edits separate from product changes.
Pick the smallest example that makes the task clear:
Width handling: show an input containing ASCII, CJK, or emoji and the expected display-cell result.
Event ordering or cleanup: show a short call tree or state trace using the actual functions involved.
Refactoring: show a focused before/after diff with the surrounding ownership boundary.
Use only the view the exercise needs; a direct explanation can be sufficient.
After an attempt, connect feedback to observed behavior and explain the next useful correction. Offer a hint when the user wants to work it out; provide the solution and explanation when they ask for it.
Check the exercise's result before offering a harder variation. Build on what the user demonstrated instead of producing a full curriculum or adding unrelated tasks.
Use when asked to check for security vulnerabilities, or when the /vuln-check command runs — scan the project for known vulnerable dependencies and security anti-patterns.