Claude Skills by LH8PPL

THE USER'S QUESTION exposed a real conflict in the CLI-route fix (2026-06-24): kiro-cli and Kiro IDE are SEPARATE surfaces (IDE: .kiro/hooks/ + .kiro/skills/ + .kiro/settings/mcp.json in PROJECT; kiro-cli: ~/.kiro/agents/cmk.json in HOME — the IDE does NOT read the agent config, confirmed). So my agent-PROMPT change (use cmk remember CLI) is correctly kiro-cli-ONLY. BUT a conflict remains: in kiro-cli, the agent has BOTH (a) my prompt saying 'use cmk remember CLI' AND (b) access to the .kiro/...

Scaffolds the core-memory-kit directory structure (context/, scripts/, cron/jobs/) into the current project. Idempotent — never overwrites existing files. Run once per project after installing the plugin. Use when the user says "bootstrap the memory system", "set up memory here", or "scaffold the memory kit".

Searches the project's recorded memory (core-memory-kit) — decisions, conventions, architecture, the reasoning behind choices, and where things live — and returns a curated, cited summary. Fire whenever the answer might be something the project already established in past work, HOWEVER the question is phrased — any prior decision, convention, rationale, or "how/where/why is it this way" question, including oblique or roundabout asks ("why is everything so spread out?", "remind me what we sett...

Captures a durable fact to project memory through the kit's safe write path (Poison_Guard secret/injection screening + home-path sanitization + dedup + conflict detection) — preferring the cmk MCP tools (mk_remember / mk_forget / mk_trust) when connected, falling back to the cmk CLI. Use when the user says "remember this", "note this", "save this", "from now on", "going forward", "I prefer", "I don't like", "we decided", "we agreed", or otherwise states a durable preference, decision, or envi...

Diagnoses and repairs core-memory-kit itself when the memory system is broken — the per-failure-code repair book. Fire whenever a "⚠ [core-memory-kit]" whisper appears on the prompt (it names the failure and points here), or when the user reports a kit symptom however they phrase it: memory is not being saved, nothing was remembered from last session, the session-start snapshot did not appear, a cmk command or an mk_ tool is erroring, search returns nothing it should have found, or "is my mem...

Searches the project's recorded memory (core-memory-kit) — decisions, conventions, architecture, the reasoning behind choices, and where things live — and returns a curated, cited summary. Fire whenever the answer might be something the project already established in past work, HOWEVER the question is phrased — any prior decision, convention, rationale, or "how/where/why is it this way" question, including oblique or roundabout asks ("why is everything so spread out?", "remind me what we sett...

Captures a durable fact to project memory through the kit's safe write path (Poison_Guard secret/injection screening + home-path sanitization + dedup + conflict detection) — preferring the cmk MCP tools (mk_remember / mk_forget / mk_trust) when connected, falling back to the cmk CLI. Use when the user says "remember this", "note this", "save this", "from now on", "going forward", "I prefer", "I don't like", "we decided", "we agreed", or otherwise states a durable preference, decision, or envi...

Diagnoses and repairs core-memory-kit itself when the memory system is broken — the per-failure-code repair book. Fire whenever a "⚠ [core-memory-kit]" whisper appears on the prompt (it names the failure and points here), or when the user reports a kit symptom however they phrase it: memory is not being saved, nothing was remembered from last session, the session-start snapshot did not appear, a cmk command or an mk_ tool is erroring, search returns nothing it should have found, or "is my mem...