BC self-hosted-crypto-payments
Add self-custodied crypto payment checkout to a Next.js + Supabase app. Accepts ETH, BTC, SOL, USDC, USDT and 25+ coins across 9 chains. No payment processor fees — HD wallet derivation, on-chain polling, zero third-party dependency. Use when: user asks to add crypto payments, accept Bitcoin/Ethereum/Solana, Web3 checkout, self-hosted crypto, no-middleman payments, blockchain payments, accept USDC/USDT.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Write Edit Glob Grep
-
low Secrets in code
secret-high-entropy-tokenresources/crypto-wallets.ts:55High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)eth: '0xA0…B48',
quoted -
low Secrets in code
secret-high-entropy-tokenresources/crypto-wallets.ts:56High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)base: '0x83…913',
quoted -
low Secrets in code
secret-high-entropy-tokenresources/crypto-wallets.ts:57High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)polygon: '0x3c…359',
quoted -
low Secrets in code
secret-high-entropy-tokenresources/crypto-wallets.ts:58High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)arbitrum: '0xaf…831',
quoted -
low Secrets in code
secret-high-entropy-tokenresources/crypto-wallets.ts:59High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)optimism: '0x0b…f85',
quoted
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "env"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 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. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (self-hosted-crypto-payments) differs from the folder (self-hosted-crypto)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 14 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1682 tokens
- 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
- +2Single-language instructions
- +3Description length 406: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.