AC aotrust-notarize
Issue a cryptographic proof (PDR) that a digital artifact existed at a specific time. Pay $0.01 USDC on Base via x402. Anchored daily to NEAR blockchain. Publicly verifiable. ONLY invoke when the user explicitly requests notarization or proof-of-existence for a specific artifact. This skill performs a paid external API call ($0.01 USDC, irreversible). Do NOT invoke proactively or as part of unrelated workflows.
Issue a cryptographic proof (PDR) that a digital artifact existed at a specific time.
As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:156High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"payTo": "0x97…800",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:157High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"asset": "0x83…913",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:171High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `asset`: USDC contract on Base (`0x83…913`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:242High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"near_anchor_tx": "H4Ma…AGp"
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (aotrust-notarize) differs from the folder (aotrust-pdr-notarization)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 85Steps. 53 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 3502 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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 414: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.