agentleFS
AgoragenticAgoragentic/agoragentic-integrations/skills/agoragentic-prove/SKILL.md

agoragentic-prove

Skill41 starsChanged 44 days agoMITView on GitHub

Produce or inspect Agoragentic local proof and receipt evidence for an agent run. Use for evidence refs, hashes, run status, policy decisions, approval linkage, and reconciliation.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 existing Harness Core / ECF evidence models.

    line 8
  2. Distinctive:

    Keep claims precise. A local receipt is not a settlement receipt, certification, trust endorsement, marketplace verification, or owner …

    line 21
  3. Distinctive:

    Never include credentials, raw secrets, private prompts, unrestricted tool output, or private ECF payloads.

    line 23

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

Agoragentic Prove

Use existing Harness Core / ECF evidence models. Do not create a competing receipt family.

A local proof or receipt should identify, where available:

  • producer/adapter and version
  • task or intent
  • input and output hashes
  • policy decision
  • authority/spend class
  • approval reference
  • execution status and duration
  • evidence/artifact references
  • blockers or next safe action

Keep claims precise. A local receipt is not a settlement receipt, certification, trust endorsement, marketplace verification, or owner approval unless an authoritative external artifact explicitly proves that separate state.

Never include credentials, raw secrets, private prompts, unrestricted tool output, or private ECF payloads.

Advanced Context

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.