skills/fact-extraction/SKILL.md
Extracting factual state changes from written chapters into the kb. Use when a chapter needs its canon, timeline, character state, and terminology captured.
npx skillsauth add haowjy/creative-writing-skills fact-extractionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read written chapters and extract the factual state diff: anything the chapter made true that wasn't before, and anything it changed about what was already true.
Common categories to look for, but don't treat as exhaustive:
If something the chapter establishes doesn't fit the common categories but still feels load-bearing, capture it anyway. Closed taxonomies lose information.
Update existing entries rather than creating duplicates. A character entry should grow chapter by chapter as their state evolves: each chapter adds to their entry rather than creating a new file.
Cross-link between entries. If a chapter establishes a relationship change between two characters, both character entries should reflect it, and the timeline entry should reference the event.
Check for conflicts between what the chapter establishes and what's already in the kb. If the chapter contradicts existing canon or uses a term differently from the relevant vocab file, flag it in your report; preserve the existing record until the author or orchestrator resolves the conflict. The contradiction may be an error in the chapter, an intentional retcon, or a vocabulary decision that needs recording.
Entries are compressed, annotated, factual. "The protagonist learned that the mentor's secret project started three years before her arrival [Ch. 7]" is specific, sourced, factual. Treat vocab cautiously: update existing vocab entries only when the canonical term is already settled. Otherwise report candidate terms, aliases actually used, and chapter sources for the author or orchestrator to ratify. Future agents read these to maintain continuity; vague entries create vague continuity.
tools
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
development
Load when building a static HTML artifact — single page or multi-page site — to make structured information explorable through layout and navigation.
testing
User-invoked pause before reporting to check intent vs literal completion, surface adjacent wins, and route knowledge capture.
development
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.