Certifying release evidence
Skill casioreview20-glitch/forge-os/skills-v2/kernel/certifying-release-evidence
Use when a source archive, package, container, skill registry, or product release needs reproducible proof bound to the exact bytes being distributed.From its SKILL.md
npx -y skills add casioreview20-glitch/forge-os --skill certifying-release-evidenceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
0.8 KB, 85 tokens by cl100k_base, as published. Nobody here has run it
Certifying Release Evidence
Core principle
Freeze the source manifest and all release subjects. Publish claims boundaries and residual risks alongside evidence. The runtime owns deterministic scope, coverage, policy, and evidence checks; the agent owns only the judgment that cannot be reduced safely to code.
Do not activate when
- an uncommitted experiment has no release subject
- verification ran on a different source tree or archive
What ships with it: 9 files
11.4 KB alongside SKILL.md
evaluators/
- baseline.json466 B
- cases.json668 B
- rubric.json416 B
sections/
- decision-tables.md391 B
- examples.md358 B
- failure-modes.md210 B
- procedure.md540 B
- verification.md239 B
- manifest.json8.2 KB