AC fomo-research
Smart money research via Fomo social graph. Track top traders, monitor live trades, build watchlists — all from your agent. Powered by fomo.family, built by cope.capital. Use when: (1) user asks about smart money, whale wallets, or top traders, (2) user wants to track specific Fomo handles or crypto traders, (3) user asks "what are the best traders buying", "who's profitable on fomo", (4) user wants real-time trade alerts or wallet monitoring, (5) user says "fomo research", "check fomo", "smart money", "wallet tracker". NOT for: executing trades, managing funds, or anything requiring private keys.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/api.md:24High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"wallet": "A5SE…ZSk",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/api.md:27High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"token_mint": "DezX…ump",
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "primaryEnv" - note
frontmatter-keyunknown frontmatter key "env"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 4181 tokens
- 100Steps. 50 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 604: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (21 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.