AC crypto-research-checklist
Run a fundamentals checklist on any crypto project before you invest. Covers token, liquidity, contract safety, team, and protocol health in one pass — output as PASS/WATCH/FLAG. Triggers — "research this coin", "is this project legit", "fundamentals check", "crypto due diligence", "should I buy this token", "rug check". Free trial at /v1/query, then $0.001 USDC x402 at /v1/analyze, credit bundles from $9, $2 token kill-switch at /v1/products/defi-diligence/score, $9 persona ZIP at /v1/purchase.
Run a fundamentals checklist on any crypto project before you invest.
As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, 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.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
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)- Base: `0x7F…C38`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:88High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Solana: `5igX…m4Z`
quoted
Files scanned: 2. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1361 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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 500: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.