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.
Profile →npx skills add casioreview20-glitch/forge-os --skill certifying-release-evidence --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Core principle
- Do not activate when
What does the certifying-release-evidence skill do?
Use when a source archive, package, container, skill registry, or product release needs reproducible proof bound to the exact bytes being distributed.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill certifying-release-evidence --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From casioreview20-glitch/forge-os, a repository with 11 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.