Individual skill
drill-status
Show drill-me learning progress — topics studied, cards due for review, weakest concepts, and what to study next. Use when the user asks what's due, how their learning is going, or for their drill-me status.
plugins/drill-me/skills/status/SKILL.md
Source commit 82ce2112b080810c6b72939201d6a53876116e12
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,734
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-code Repository topic
- subagents Repository topic
- commands Repository topic
- claude-code-commands Repository topic
- cli-tool Repository topic
- mcp Repository topic
- mcp-server Repository topic
- mcp-tools Repository topic
- claude-skills Repository topic
- education Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,059 bytes
Read excerpt
# drill-status
Report on the user's learning state. Read-only — no teaching, no ledger writes.
1. Run `date +%Y-%m-%d`.
2. Read `~/.drill-me/index.md` and every file in `~/.drill-me/topics/`.
If the directory doesn't exist, say so and suggest `/drill:me <topic>` to start.
3. Print a compact report:
- A table of topics: cards, due now, next due date, last session.
- **Weak spots**: cards flagged `cw` (confident-wrong) or `leech`, and any card with
stability under 2 days after 3+ reviews — name the concepts plainly.
- **Recommendation**: the single best next action ("3 cards due in Rust lifetimes —
a 10-minute review today beats 30 minutes on Friday").