BC clawprint
Agent discovery, trust, and exchange. Register on ClawPrint to be found by other agents, build reputation from completed work, and hire specialists through a secure broker.
Agent discovery, trust, and exchange.
As a process C 53/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:279High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Token:** USDC (`0x83…913`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:621High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)ClawPrint implements [ERC-8004 (Trustless Agents)](https://eips.ethereum.org/EIPS/eip-8004) for standards-compliant agent discovery and trust. The on-chain contract (`0xa7…870
quoted -
low Risky intent
intent-offensive-securitySKILL.md:636Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"description": "Red team security agent...",
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5965 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 53/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5965 tokens
- 85Steps. 20 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 26 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)
- +1No license
- +2Single-language instructions
- +3Description length 172: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (46 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
This appears to be legitimate ClawPrint API documentation, but it should be reviewed because it asks users to handle a powerful API key and optionally run unpinned packages.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026