lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user wants to turn past AI coding sessions into reusable skills, asks "what could I make into a skill", "mine my lore", "forge skills from my history", or points at a .specstory/history directory.
npx skills add specstoryai/getspecstory --skill lore --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lore Your sessions are your lore. This skill turns a user's real coding history into installed skills. A deterministic engine (`scripts/mine-skills.mjs`) parses their SpecStory transcripts - from **every agent** SpecStory captures (Claude Code, Codex CLI, Cursor CLI, Gemini CLI, Factory Droid, DeepSeek, Antigravity, ...) - into a persistent corpus of **beats**, and returns corroborated candidates. You - the calling agent, whichever harness you are - supply all judgment: name them, discard the generic ones, and interactively forge the good ones into `SKILL.md` packages grounded in the user's own commands. The engine does the retrieval and counting; **you do the synthesis.** Do not try to read raw transcripts yourself - they can be hundreds of thousands of lines. Run the engine and work from its output. This skill is **harness-portable** (agentskills.io format). Where it names a specific tool (e.g. `AskUserQuestion`), treat that as "use your harness's equivalent; fall back to plain chat." **Voice:** when narrating to the user, talk about *mining their lore* and *skill candidates* - e.g. "I'll mine your lore here in <project> for skill candidates." Reserve the word **forge** for the
- OUTPUT CONTRACT - three LAWS, read before emitting anything to the user
- What makes a candidate skill-worthy
- Steps
- Verification
- Failure modes
- Notes
- Output contract
find . -type d -path '*/.specstory/history' -not -path '*/node_modules/*' 2>/dev/null | head node "<skill-dir>/scripts/mine-skills.mjs" index --dir <history-dir> node "<skill-dir>/scripts/mine-skills.mjs" index --projects <parent-dir-of-repos> node "<skill-dir>/scripts/mine-skills.mjs" report --min-sessions 3 --top 10 node "<skill-dir>/scripts/mine-skills.mjs" forged check --emit json cached themes first - sweeps are once-per-corpus-state, not once-per-run node "<skill-dir>/scripts/mine-skills.mjs" theme list # or `theme render` for the human-readable cards Claude Code: run the bundled workflow (six thematic lenses + adversarial verification) Other harnesses: spawn one subagent per lens with the same briefs, sampling via: node "<skill-dir>/scripts/mine-skills.mjs" beats --project <name> --shape conversation --max 30 --min-intent-len 40
What does the lore skill do?
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user wants to turn past AI coding sessions into reusable skills, asks "what could I make into a skill", "mine my lore", "forge skills from my history", or points at a .specstory/history directory.
How do I install it?
Run `npx skills add specstoryai/getspecstory --skill lore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From specstoryai/getspecstory, a repository with 1,295 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.