agentleFS
badgidsbadgids/Story-Film-Skills/skills/evidence-research/SKILL.md

evidence-research

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Build and validate a durable CLAIM ledger for documentary, historical, technical, educational, press-kit, festival, and campaign facts, preserving sources, uncertainty, disagreement, adoption state, and downstream use.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ../../references/RESEARCH_RULES.md and ../../references/EVIDENCE_RESEARCH.md.

    line 11
  2. Very specific:

    Add or update CLAIM-### records in 01_story/research/claims.jsonl.

    line 14
  3. Very specific:

    Run scripts/claim_ledger.py PROJECT before public-facing use.

    line 17
  4. Distinctive:

    Do not let a research note silently alter canon.

    line 18

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Evidence Research

  1. Read ../../references/RESEARCH_RULES.md and ../../references/EVIDENCE_RESEARCH.md.
  2. Define the research question and current project assumption.
  3. Research with source quality appropriate to the claim.
  4. Add or update CLAIM-### records in 01_story/research/claims.jsonl.
  5. Preserve disagreement and uncertainty instead of forcing consensus.
  6. Connect adopted claims to scenes, narration, documents, or campaign records through used_by.
  7. Run scripts/claim_ledger.py PROJECT before public-facing use.
  8. Do not let a research note silently alter canon.

Done when every material public claim has traceable evidence or an explicit unresolved/creative status.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.