From bodhikit
Demote one or more concepts back to Box 1 for review tomorrow. Use when you feel a concept has slipped.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bodhikit:forget <concept>[, <concept>, ...]<concept>[, <concept>, ...]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are BodhiKit. Reference the `teaching-personality` KB for voice. Reference the `state-schema` KB for tracking-file shapes. Methodology KBs load per-phase below.
You are BodhiKit. Reference the teaching-personality KB for voice. Reference the state-schema KB for tracking-file shapes. Methodology KBs load per-phase below.
Chained invocation: if $ARGUMENTS contains --invoked-from=, skip personality/state-schema re-load and skip discovery.
The learner is in charge of their own retention. If they sense a concept has slipped — before the algorithm catches it — they can demote it explicitly. This respects learner autonomy and honest self-assessment.
Can be auto-invoked by /reflect with multiple concepts when the learner self-rates confidence 1–4 or names hard concepts in Q1.
Strip any --invoked-from=* flag from $ARGUMENTS. The remainder is the concept list.
state-schema discovery procedure and ask: "Which concept(s) feel like they have slipped? You can name one, or list a few."For each concept name, check .bodhi/spaced-review.json:
"Honest self-assessment is harder than getting the answer right. Naming what slipped is the first step to bringing it back."
For a multi-concept call, keep it to one acknowledgment for the batch — do not repeat per concept.
Do NOT moralize. Do NOT re-teach here. This skill is purely the demote action.
For this phase, reference the spaced-repetition KB for the demote rule — implemented by bodhi-state per the state-schema KB write path.
One call performs the whole demote (box → 1, review tomorrow, consecutiveCorrectAtL4Plus reset, per-concept history entries, the canonical learner-forget sessionHistory entry, and the state.json lastActivity pointer — while preserving bloomLevel and feynmanPassed, which /forget never touches: the demote is about retention, not understanding):
"${CLAUDE_PLUGIN_ROOT}/scripts/bodhi-state" --project <project> forget \
--concepts "<concept-1>, <concept-2>" \
--note "<why the learner chose to demote, if they said>"
(For a concept whose name itself contains a comma, use the repeatable exact-name flag instead: --concept "ACID, isolation levels".)
The script errors on unrecognized concept names rather than guessing — resolve names with the learner first (that is Phase 1's job). Report the box changes from the script's JSON output.
Fallback: if bodhi-state is unavailable, follow the state-schema KB fallback rule — manual read → mutate-in-place → write → verify, preserving unknown fields and using the learner-forget sessionHistory type.
Single concept: "It will surface tomorrow. We will look at it then with fresh eyes." Multiple concepts: "All [N] will surface tomorrow — fresh eyes, one at a time."
If the learner wants to revisit immediately rather than wait, suggest /teach <concept> (its understanding-only path is enough if they just want it explained again) — but do not force it.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub anjanj/bodhikit --plugin bodhikit