Enforcing review separation
Skill casioreview20-glitch/forge-os/skills-v2/kernel/enforcing-review-separation
Use when artifact, code, finding, provider, or release approval requires independent review across principal, role, team, or trust-domain boundaries.From its SKILL.md
npx -y skills add casioreview20-glitch/forge-os --skill enforcing-review-separationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 17 days oldThe repository was created 17 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.9 KB, 94 tokens by cl100k_base, as published. Nobody here has run it
Enforcing Review Separation
Core principle
Resolve producer, resolver, evaluator, closer, and signer trust domains. Bind the authorized reviewer and evidence set to the reviewed subject. 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
- A0 prototype policy explicitly permits self-review
- the action is a reversible draft with no assurance claim
What ships with it: 9 files
11.6 KB alongside SKILL.md
evaluators/
- baseline.json476 B
- cases.json701 B
- rubric.json416 B
sections/
- decision-tables.md391 B
- examples.md362 B
- failure-modes.md228 B
- procedure.md537 B
- verification.md260 B
- manifest.json8.3 KB