reset-edu
Skill9 starsChanged 2 months agoMITView on GitHub
Explicitly delete the global education database after showing its resolved path and obtaining confirmation. Keeps project files and configuration.
In this repository15 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- asciiSkill
- challengeSkill
- compareSkill
- demoSkill
- excalidrawSkill
- flashcardsSkill
- init-eduSkill
- motivateSkill
- progressSkill
- quiz-meSkill
- researchSkill
- roadmapSkill
- save-progressSkill
- summarySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read ${CLAUDE_PLUGIN_ROOT}/references/education-data.md and resolve <education-db> from CLAUDE_TEACHER_DB or the documented default before …
- Distinctive: line 15
If the database is already absent, say so and stop.
- Very specific: line 21
Ask: “Type YES to permanently delete this database.” Wait for a new response.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reset Education Data
Read ${CLAUDE_PLUGIN_ROOT}/references/education-data.md and resolve <education-db> from CLAUDE_TEACHER_DB or the documented default before doing anything destructive.
1. Inspect the deletion target
Resolve the canonical absolute path and inspect its contents. Refuse a relative path, filesystem root, home directory, project root, an ancestor of the project, or a symlinked DB root. Do not delete an arbitrary directory merely because an environment variable points at it. A valid target contains only the expected education entries: student.json, dashboard.json, topics/, quizzes/, sessions/, and docs/. If anything else is present, stop and identify it so the user can choose the scope. Do not follow symlinks inside the DB into other directories.
If the database is already absent, say so and stop.
2. Confirm the concrete scope
Show the resolved path and explain that its student profile, quiz records, topic progress, session logs, and global saved explanations will be permanently removed across all learning projects using this DB. State that project-local docs/, CLAUDE.md, settings, and learning markers remain.
Ask: “Type YES to permanently delete this database.” Wait for a new response; only YES (case-insensitive) confirms. Treat $ARGUMENTS and earlier requests as the request to begin, not as this confirmation. Any other response cancels.
3. Delete and verify
Recheck that the canonical target and contents still match what was shown. Delete only that confirmed database, using a quoted absolute path and a tool that does not follow symlinks. Never interpolate the path into shell source or use broad wildcards. Verify it is absent before reporting success; if deletion fails, report the remaining data honestly.
Tell the student /claude-teacher:init-edu starts fresh. Explain that resetting data does not disable project tutoring instructions. To pause hook reminders, set enabled: false in .claude/claude-teacher.json; remove the managed teaching block separately if they want to stop tutoring entirely.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.