agentleFS
Sign inStart free
indyforgeindyforge/knowledge-forge/.agents/skills/capture-fixture-verification/SKILL.md

capture-fixture-verification

Skill0 starsChanged 5 months agoMITView on GitHub

Verify capture fixtures, Markdown output, manifests, hashes, and evidence-gap behavior after capture-related changes.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when code changes affect capture behavior, source text extraction, manifests, hashes, fixtures, or Markdown output.

    line 8
  2. Distinctive:

    Do not mark capture work complete until tests and smoke output match the expected provenance model.

    line 18

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

Capture Fixture Verification

Use this skill when code changes affect capture behavior, source text extraction, manifests, hashes, fixtures, or Markdown output.

Checklist

  1. Run npm test.
  2. Run npm run smoke.
  3. Inspect .tmp/capture/note.md and .tmp/capture/manifest.json.
  4. Confirm the note includes source URL, hashes, evidence gaps, and source excerpt.
  5. Confirm the manifest keeps schemaVersion, sourceUrl, capturedAt, hashes, textExcerpt, evidenceGaps, and storage.

Do not mark capture work complete until tests and smoke output match the expected provenance model.

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.

Check your setup, free