BC crow
Agent payment service via CrowPay — gives your agent a wallet to pay for APIs and services. Use this skill whenever the agent needs to handle HTTP 402 Payment Required responses, pay for an API, buy credits or subscriptions, pay a merchant with a credit card, set up an agent wallet, or manage spending rules. Also use when the user mentions CrowPay, Crow, agent payments, USDC, x402, or buying anything on the internet for the agent — even if they don't say "Crow" by name.
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions
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 · 15
✓ No critical or high findings
Medium and low: 15
-
low Secrets in code
secret-high-entropy-tokenreferences/api-reference.md:55High-entropy token-like string (may be an id, hash or a credential) (placeholder value)"paymentRequired": {"x402Version":2,"resource":{"url":"..."},"accepts":[{"scheme":"exact","network":"eip155:8453","amount":"1000000","asset":"0x83…913","payTo":"0x...placeholder -
low Secrets in code
secret-high-entropy-tokenreferences/api-reference.md:88High-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-tokenreferences/api-reference.md:114High-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-tokenreferences/api-reference.md:450High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC contract (Base mainnet) | `0x83…913` |
table -
low Secrets in code
secret-password-literalreferences/card-payments.md:15Hard-coded password / key literal (may be an example) (placeholder value)-H "X-API-Key: crow…..." \
placeholder -
low Secrets in code
secret-password-literalreferences/card-payments.md:70Hard-coded password / key literal (may be an example) (placeholder value)-H "X-API-Key: crow…..."
placeholder -
low Secrets in code
secret-high-entropy-tokenreferences/error-handling.md:154High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC contract (Base) | `0x83…913` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/x402-flow.md:27High-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-password-literalreferences/x402-flow.md:43Hard-coded password / key literal (may be an example) (placeholder value)-H "X-API-Key: crow…..." \
placeholder -
low Secrets in code
secret-high-entropy-tokenreferences/x402-flow.md:53High-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-password-literalreferences/x402-flow.md:125Hard-coded password / key literal (may be an example) (placeholder value)-H "X-API-Key: crow…..."
placeholder -
low Secrets in code
secret-password-literalreferences/x402-flow.md:153Hard-coded password / key literal (may be an example) (placeholder value)-H "X-API-Key: crow…..." \
placeholder -
low Secrets in code
secret-high-entropy-tokenreferences/x402-flow.md:167High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- USDC contract: `0x83…913`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:134High-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:308High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC contract:** `0x83…913`
quoted
Files scanned: 6. 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 64/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 40 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2981 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 474: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.