agentleFS
forsvn-labsforsvn-labs/meta-skills/skills/knowledge-review/SKILL.md

knowledge-review

Skill14 starsChanged 3 months agoMITView on GitHub

Audit the authority, freshness, and uncertainty of the sources and claims behind a decision, and reconcile conflicting evidence. Use for research synthesis, factual-claim checks, or reframing a recommendation built on weak sourcing. This is knowledge review, never code review.

2 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

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check that a decision rests on credible, current, and honestly uncertain evidence.

    line 11

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

Knowledge review

Check that a decision rests on credible, current, and honestly uncertain evidence.

Clarify what is being claimed

State the factual claim or decision the review must support. Enumerate the sources and data the work currently leans on. Distinguish observed evidence, reasonable inference, and assumption before judging any of them.

Assess each source

For every source and claim, record:

  • authority: primary or secondary, provenance, perspective, and known bias;
  • freshness: an explicit date or how current this category of claim is;
  • uncertainty: confidence, sample, and what could change the finding.

Build the contradiction matrix

For each key claim, put sources as rows and record what each asserts, its authority, date, and uncertainty. Mark every direct contradiction explicitly so conflicts are visible rather than merged.

Resolve

Reconcile conflicts by weighing authority, recency, and causal plausibility—not by counting or averaging sources. Label the resolved position and why the competing evidence lost.

Surviving unknowns and recheck trigger

List what remains unknown and set a recheck trigger: a date, event, or condition when the claim must be verified again. Do not let an unknown silently age into a fact.

Scope

This reviews knowledge, sources, and factual claims—not code. Do not use it to review an implementation, a diff, or a codebase; use a code-review path for that. Keep the review proportional to the decision and never fabricate or pad sources.

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.