AD coil-board
Buy Coil's scored, ranked stock board over x402 instead of building a scanner. Use when an agent needs a market read — is the tape risk-on or risk-off, which S&P 500 / Nasdaq-100 / macro names are set up to buy right now, or the full ~560-name board with opportunity, entry-timing and hold-strength scores. Pays per read in USDC on Base (eip155:8453) via the x402 protocol — no account, no card, no email. Research, not investment advice.
Buy Coil's scored, ranked stock board over x402 instead of building a scanner.
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, 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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (coil-board) differs from the folder (coil-board-skill)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 15 steps
- 100Execution cost. Instruction body is 1891 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
- +2Single-language instructions
- +3Description length 438: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.