Evidence Freshness
Bind a check or action to the input snapshot it actually used. Use before relying on cached verification, consuming a reviewed batch, acting while inputs may change, or retrying an operation with an ambiguous result.
Install
/plugin marketplace add okgrit/done-is-a-claimThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add okgrit/done-is-a-claim --skill evidence-freshnessgit clone --depth 1 https://github.com/okgrit/done-is-a-claim.git /tmp/done-is-a-claim
mkdir -p ~/.claude/skills
cp -r /tmp/done-is-a-claim/skills/evidence-freshness ~/.claude/skills/evidence-freshnessPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Evidence freshness Evidence remains a statement about its measured snapshot. It supports a later decision only to the extent that the decision uses that snapshot and relevant conditions. These are operational safeguards, not a new incident record. ## Pin what the check consumes 1. Identify the input tree and relevant configuration, dependencies, datasets, generated inputs, flags and environment. Record the revision and dirty state; a commit alone does not describe uncommitted or untracked input. 2. Before the run, hash the selected inputs or a manifest of them. Say what the selection excludes; matching a few hashes cannot certify the whole repository or an external service. Freeze batch lists into a separate snapshot rather than checking a list that remains open for append. 3. Run the named check against that snapshot. Record command, outcome, time and evidence location. Retain the tested inputs or enough identifiers to reproduce them without treating a log summary as the input identity. 4. Compare the revision, dirty state and selected hashes after the run. Changed inputs make the result ambiguous for the new tree. A formatter or fixer that mutates its inputs does not certify its resulting tree; run acceptance again on the stable result. Distinguish produced outputs from changed inputs. 5. Equal before/after hashes can miss edits made and restored during a run. When a result gates a consequential action, use isolated immutable inputs
Details
- Skill name
evidence-freshness- Repository
- okgrit/done-is-a-claim
- Path
skills/evidence-freshness/SKILL.md- License
- Apache-2.0
- Repo updated
- 25 October 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Evidence Freshness skill do?
Bind a check or action to the input snapshot it actually used. Use before relying on cached verification, consuming a reviewed batch, acting while inputs may change, or retrying an operation with an ambiguous result.
How do I install the Evidence Freshness skill?
Claude Code plugin: /plugin marketplace add okgrit/done-is-a-claim. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Evidence Freshness popular?
It lives in okgrit/done-is-a-claim, which has 33 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Acceptance Design
33okgrit/done-is-a-claim
Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.
Checking Delivery
33okgrit/done-is-a-claim
Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.
Collecting Worker Results
33okgrit/done-is-a-claim
Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.
Executing Plans
33okgrit/done-is-a-claim
Carry an actionable change plan through implementation, checks, review and an evidence-backed report. Use when executing several planned steps or integrating bounded worker returns, within existing authorization.
Daily Brief
48amplitude/mcp-marketplace
Delivers a daily briefing of the most important changes across your Amplitude instance. Use when the user asks for a "daily download", "morning briefing", "what's happening", "anything I should know", or wants a summary of recent metric changes, experiments, and user feedback.
History Hygiene
45Azure-Samples/agent-skills-dotnet-demo
Record final outcomes to history.md, not intermediate requests or reversed decisions
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.