BF verifiable-data
Use the Cryptowerk Verifiable Data skill to implement an "Agent Flight Recorder" that creates an immutable, cryptographically verifiable audit trail for OpenClaw agent executions. Register execution hashes to maintain privacy, fetch blockchain seals, and verify proofs for AI workflows, decisions, and data artifacts. Use when the user requires deterministic, proof-carrying agent operations with local sidecar artifacts and no SDK dependency. This skill securely acquires service credentials and exclusively handles proof APIs without executing unrelated account actions or purchases.
Use the Cryptowerk Verifiable Data skill to implement an "Agent Flight Recorder" that creates an immutable, cryptographically verifiable audit trail for…
As a process F 42/100 · Will not run — References files that are not bundled: scripts/register.py, scripts/getseal.py, scripts/verify.py
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/register.py - warning
missing-refreference to a missing file: scripts/getseal.py - warning
missing-refreference to a missing file: scripts/verify.py - warning
missing-refreference to a missing file: references/cryptowerk-api-notes.md - warning
missing-refreference to a missing file: references/storage-and-state.md
Process rating: all ten parameters 42/100
- 0Tools and files. 5 referenced file(s) missing: scripts/register.py, scripts/getseal.py, scripts/verify.py
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (verifiable-data) differs from the folder (agent-flight-recorder)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 26 steps
- 100Execution cost. Instruction body is 376 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 585: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.