agentleFS
electrohireelectrohire/spec-kit-aee/.github/skills/speckit-aee-verify/SKILL.md

speckit-aee-verify

Skill4 starsChanged 54 days agoMITView on GitHub

Verify the tamper-evident AEE ledger

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify every link in the AEE SHA-256 JSONL ledger.

    line 14
  2. Very specific:

    Use .specify/extensions/aee/ledger/epistemic-ledger.jsonl unless ledger=<path> is given.

    line 22

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

Aee Verify Skill

AEE Verify

Verify every link in the AEE SHA-256 JSONL ledger.

User input

$ARGUMENTS

Use .specify/extensions/aee/ledger/epistemic-ledger.jsonl unless ledger=<path> is given. Resolve it inside the project root, refuse symlinked components, and run:

python .specify/extensions/aee/scripts/python/run_aee.py verify --ledger "<path>"

Report validity, entry count, head hash, and every error. State explicitly that a valid chain proves continuity of the retained records only—not truth, identity, trusted time, completeness before the first record, or compliance.

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.