BF elfa-api
Interact with the Elfa API — a crypto social intelligence platform that provides real-time sentiment, trending tokens, narrative tracking, and AI-powered market analysis from Twitter/X and Telegram. Use this skill whenever the user wants to query crypto social data, check trending tokens or narratives, look up mentions for a ticker or keyword, get smart stats for a Twitter account, retrieve token news, find trending contract addresses, or chat with Elfa's AI for market analysis. Also trigger when the user asks how to integrate the Elfa API, wants example code or curl commands for Elfa endpoints, or mentions "elfa" in the context of crypto data. This skill covers both making live API calls (via API key or x402 keyless payments) and generating correct code snippets for developers integrating the Elfa API into their own products. Supports two access modes: traditional API key authentication and x402 pay-per-request via USDC on Base (no registration required).
As a process F 49/100 · Will not run — References files that are not bundled: references/api-reference.md
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
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Risky intent
intent-wallet-secretsSKILL.md:151Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Never ask the user to share their wallet private key or seed phrase in the conversation.
-
low Exfiltration
net-credential-useSKILL.md:131Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s -H "x-elfa-api-key: $ELFA_API_KEY" "https://api.elfa.ai/v2/aggregations/trending-tokens?timeWindow=24h&pageSize=10"
vendor-host -
low Risky intent
intent-wallet-secretsSKILL.md:149Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)- The user's wallet private key is used only locally by the x402 library to sign
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:157High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Currency:** USDC on Base (`0x83…913`)
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/api-reference.md - note
frontmatter-keyunknown frontmatter key "env" - note
frontmatter-keyunknown frontmatter key "credentials"
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: references/api-reference.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (elfa-api) differs from the folder (claude-ai-trading-skill)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 69 steps
- 100Failures and branches. 10 branches, has a failure section
- 100Execution cost. Instruction body is 3203 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +3Description length 970: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 69 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.