Skills

Lore

SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex...

Install

npx skills add specstoryai/getspecstory --skill lore -g -a claude-code -y
Category
AI and agents
Updated
5d ago
License
Apache-2.0
Context cost
Mediumabout 3,000 tokens
Runs scripts
Yes, review before use

What it does

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.

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 final act only: creating the skills the user selected (Step 4). Never describe mining, judging, or candidates as "forge-…" anything.

OUTPUT CONTRACT - three LAWS, read before emitting anything to the user

Named failure mode #1 (2026-06-09, BearClaude run): the agent indexed, deep-mined four skills, then jumped straight to AskUserQuestion with bare option labels - ZERO dossiers rendered in chat. The user declined every question because they had nothing to judge by. The entire mining run was wasted.

Read the whole SKILL.md on GitHub

More in AI and agents