issuing-trusted-execution-receipts
Use when a command, test, scanner, brokered tool, or sandbox run must produce evidence whose pass status and digest cannot be chosen by the requesting agent.
Profile →npx skills add casioreview20-glitch/forge-os --skill issuing-trusted-execution-receipts --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.
# Issuing Trusted Execution Receipts ## Core principle Authorize the evidence type and bind the request to a subject hash. Sign or content-address the immutable receipt before returning metadata. 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 - a human opinion is the evidence type - the provider is not authorized for the requested evidence method
- Core principle
- Do not activate when
What does the issuing-trusted-execution-receipts skill do?
Use when a command, test, scanner, brokered tool, or sandbox run must produce evidence whose pass status and digest cannot be chosen by the requesting agent.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill issuing-trusted-execution-receipts --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.