From lore
Record a dead-end — an approach tried that didn't work, with a revive condition. Use for /dead-end, "that didn't work", "mark this as a dead end", "don't try this again".
How this skill is triggered — by the user, by Claude, or both
Slash command
/lore:dead-endThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather the following from the user conversationally, asking only for what is missing:
Gather the following from the user conversationally, asking only for what is missing:
YYYY-MM-DD; defaults to today)Dead-ends are universal (not project-specific). Once you have the title at minimum, run:
lore new dead-end \
--title "<title>" \
[--subsystems "<sub1>,<sub2>"] \
[--revive-condition "<condition>"] \
[--tried "<YYYY-MM-DD>"] \
[--vault "$LORE_VAULT"]
Then open the written file, fill in the body sections with the user's answers, and confirm the note path.
If no session note exists the CLI will print a skip notice — that is expected; continue normally.
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 tduffield/lore --plugin lore