Stats
Actions
Tags
From forgeproof
Verify a ForgeProof provenance bundle (.rpack file). Use when the user asks to "verify a bundle", "check provenance", "validate an rpack", "verify forgeproof", or wants to confirm that AI-generated code has not been tampered with since signing. Supports verifying bundles from other repositories or PRs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/forgeproof:forgeproof-verify [path-to-rpack][path-to-rpack]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify the cryptographic integrity of a ForgeProof `.rpack` provenance bundle.
Verify the cryptographic integrity of a ForgeProof .rpack provenance bundle.
The provenance engine script is at ${CLAUDE_PLUGIN_ROOT}/skills/forgeproof/scripts/forgeproof.py.
If $ARGUMENTS contains a path, use it directly.
If $ARGUMENTS is empty, look for .rpack files:
ls .forgeproof/*.rpack 2>/dev/null
If multiple bundles exist, list them and ask the user which to verify. If none exist, tell the user no bundles were found.
python ${CLAUDE_PLUGIN_ROOT}/skills/forgeproof/scripts/forgeproof.py verify --rpack <path>
Parse the JSON output. Present the results clearly to the user:
If verified (no errors): Report that the bundle integrity is confirmed. Show:
If verification failed (errors present): Report each error clearly. Common failure scenarios:
For each error, explain what it means in plain language and what the user should do about it.
npx claudepluginhub ryanjmichie-git/forgeproof-plugin --plugin forgeproofProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.