BC bridge-stablecoin
Build USDC bridging with Circle Bridge Kit SDK and Crosschain Transfer Protocol (CCTP). Supports bridging USDC between EVM chains, between EVM chains and Solana, and between any two chains on Circle Wallets (i.e Developer-Controlled Wallets or Programmable wallets). Use when: bridge USDC, setting up Bridge Kit adapters (Viem, Ethers, Solana Kit, Circle Wallets), handling bridge events, collecting custom fees, configuring transfer speed, or using the Forwarding Service. Triggers on: Bridge Kit, bridge USDC, crosschain transfer, CCTP, move USDC between chains, @circle-fin/bridge-kit, adapter-viem, adapter-ethers, adapter-solana-kit, forwarding service, bridge routes.
As a process C 64/100 · Has gaps — weak spots: result and completion, running it twice
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 purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Risky intent
intent-wallet-secretsSKILL.md:33Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetPRIVATE_KEY= # EVM wallet private key (hex, 0x-prefixed)
-
medium Risky intent
intent-wallet-secretsSKILL.md:35Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetSOLANA_PRIVATE_KEY= # Solana wallet private key (base58)
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:78High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"address": "0x74…44e",
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:87High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0x74…44e",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:149High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)recipientAddress: "0x74…44e",
quoted
Files scanned: 5. 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
- 30Running it twice. 7 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
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2543 tokens
- 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 673: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.