lore

1# Lore
2 
3Your sessions are your lore. This skill turns a user's real coding history into installed skills.
4A deterministic engine (`scripts/mine-skills.mjs`) parses their SpecStory transcripts - from **every
5agent** SpecStory captures (Claude Code, Codex CLI, Cursor CLI, Gemini CLI, Factory Droid, DeepSeek,
6Antigravity, ...) - into a persistent corpus of **beats**, and returns corroborated candidates.
7You - the calling agent, whichever harness you are - supply all judgment: name them, discard the
8generic ones, and interactively forge the good ones into `SKILL.md` packages grounded in the user's
9own commands.
10 
11The engine does the retrieval and counting; **you do the synthesis.** Do not try to read raw
12transcripts yourself - they can be hundreds of thousands of lines. Run the engine and work from
13its output.
14 
15This skill is **harness-portable** (agentskills.io format). Where it names a specific tool
16(e.g. `AskUserQuestion`), treat that as "use your harness's equivalent; fall back to plain chat."
17 
18**Voice:** when narrating to the user, talk about *mining their lore* and *skill candidates* -
19e.g. "I'll mine your lore here in <project> for skill candidates." Reserve the word **forge** for
20the final act only: creating the skills the user selected (Step 4). Never describe mining, judging,
21or candidates as "forge-…" anything.
22 
23## OUTPUT CONTRACT - three LAWS, read before emitting anything to the user
24…