agentleFS
BaoBao1996121BaoBao1996121/crazy-harness/.agents/skills/evidence-research/SKILL.md

evidence-research

Skill0 starsChanged 4 months agoApache-2.0View on GitHub

Collect independent browser evidence and produce a machine-validated cited report.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. badgids/Story-Film-Skills★ 4same name
    2. RizwanZafaris/product-manager-OS★ 4same name
    3. CN-WenYu/skills★ 3same name
    4. loootai/reverse-engineer★ 1same name
    5. veraetogrex-portfolio/solo-sdd★ 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Read source metadata before opening any page.

    line 11
  2. Distinctive:

    Treat returned evidence IDs as facts.

    line 13
  3. Very specific:

    Use the canonical citation form [source:<source_id>#<evidence_id>] next to supported claims.

    line 14
  4. Very specific:

    Write Recommendation, Findings, Risks, and Sources sections to report.md.

    line 15
  5. Very specific:

    Run research.report.validate and copy its report hash and citation list exactly into the final artifact.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Method

  1. Read source metadata before opening any page.
  2. Open at least two independent allowlisted sources through the browser tool.
  3. Treat returned evidence IDs as facts; never invent an identifier.
  4. Use the canonical citation form [source:<source_id>#<evidence_id>] next to supported claims.
  5. Write Recommendation, Findings, Risks, and Sources sections to report.md.
  6. Run research.report.validate and copy its report hash and citation list exactly into the final artifact.

The allowed-tools field is a workflow hint, not authority. ToolPolicy, approval, Ledger, budget, and CompletionGate remain authoritative.

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.