story-research
Skill4 starsChanged 3 months agoApache-2.0View on GitHub
Research factual, historical, technical, cultural, location, or craft details needed by a story or screenplay, recording source type, confidence, conflicts, contradictions, gaps, and production-relevant implications.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- JacksonHe04/storytellingtheir own version, first seen Sep 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- JacksonHe04/storytelling★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository139 other files it gives its agents.
- 3d-animation-short-generatorSkill
- ace-step-xlSkill
- adapt-screenplaySkill
- asset-approvalSkill
- audience-simSkill
- audio-masterSkill
- batch-recoverySkill
- beat-sheetSkill
- book-planSkill
- brand-promo-video-generatorSkill
- campaign-brandSkill
- campaign-deliverySkill
- character-bibleSkill
- character-simSkill
- comfyui-api-v2Skill
- comfyui-assetsSkill
- comfyui-binding-auditSkill
- comfyui-cliSkill
- comfyui-discoverSkill
- comfyui-handoffSkill
- comfyui-mcpSkill
- comfyui-offline-batchSkill
- comfyui-runSkill
- comfyuiSkill
- comfyui-troubleshootSkill
- comfyui-workflowSkill
- content-repurposeSkill
- context-shardsSkill
- continuity-checkSkill
- co-op-game-intro-generatorSkill
- creative-pressure-testSkill
- creative-production-specSkill
- crew-reviewSkill
- decision-tree-interviewSkill
- delivery-qcSkill
- design-systemSkill
- dialogue-audio-authoritySkill
- dialogue-timing-preflightSkill
- dialogue-voiceSkill
- director-bookSkill
- documented-creative-discoverySkill
- edit-assistSkill
- editorial-packageSkill
- editorial-reconciliationSkill
- editor-project-exportSkill
- edit-planSkill
- evidence-researchSkill
- ffmpegSkill
- film-completenessSkill
- film-masterSkill
- generation-budgetSkill
- generation-model-setupSkill
- generation-packSkill
- generation-workflow-setupSkill
- guided-production-wizardSkill
- h3-prompt-writingSkill
- handdrawn-live-video-generatorSkill
- imagemagickSkill
- kdenlive-exportSkill
- krea-2Skill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use when a creative decision depends on real-world facts or when the project needs grounded detail it does not yet have.
- Very specific: line 15
Read ../../references/CORE_CONTRACT.md, ../../references/RESEARCH_RULES.md, the brief, and the story assumptions relevant to the question.
- Distinctive: line 16
Write the exact research questions before searching.
- Distinctive: line 17
Prefer primary, official, scholarly, or practitioner sources according to the question.
- Distinctive: line 21
Update canon only for facts or creative decisions the project has explicitly adopted.
- Distinctive: line 25
Every adopted factual constraint names its source or evidence class, uncertainty is visible, and the writer can use the note without …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Story Research
Use when a creative decision depends on real-world facts or when the project needs grounded detail it does not yet have.
Workflow
- Read
../../references/CORE_CONTRACT.md,../../references/RESEARCH_RULES.md, the brief, and the story assumptions relevant to the question. - Write the exact research questions before searching.
- Prefer primary, official, scholarly, or practitioner sources according to the question. Use current sources when the fact can change.
- Separate verified fact, supported interpretation, contested claim, anecdotal detail, creative inspiration, and project decision.
- Record credible disagreements instead of flattening them into one answer.
- Save
01_story/research/<topic>.mdwith: question, usable findings, source notes, confidence, conflicts, contradictions with current story assumptions, gaps, and story implications. - Update canon only for facts or creative decisions the project has explicitly adopted.
Done
Every adopted factual constraint names its source or evidence class, uncertainty is visible, and the writer can use the note without repeating the research.
Evidence ledger handoff
When research will support documentary narration, historical claims, press materials, social copy, a pitch, a treatment presented as factual, or any other public factual statement, route adopted claims through evidence-research and 01_story/research/claims.jsonl. Research notes may remain richer than the ledger. The ledger exists to make public-use evidence and uncertainty machine-checkable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

