BC goldrush-foundational-api
GoldRush Foundational API — REST API for historical and near-real-time blockchain data across 100+ chains. Use this skill whenever the user needs wallet token balances, transaction history, NFT holdings, token prices, token approvals, cross-chain activity, block data, portfolio value tracking, or any on-chain data query via REST. This is the default skill for blockchain data lookups, portfolio dashboards, tax tools, compliance checks, block explorers, and any application that fetches historical or current chain data. If the user needs real-time streaming or WebSocket push data, use goldrush-streaming-api instead. If the user needs pay-per-request access without an API key, use goldrush-x402 instead.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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 · 10
✓ No critical or high findings
Medium and low: 10
-
low Secrets in code
secret-high-entropy-tokenreferences/endpoints-balances.md:152High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Operation ID: `getE…ess`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/endpoints-balances.md:588High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Operation ID: `getT…ess`
quoted -
low Risky intent
intent-wallet-secretsreferences/endpoints-balances.md:669Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (detector / deny-list definition)- **Hierarchical Deterministic (HD) Wallet** refers to a wallet that generates all of its keys and addresses from a single source (e.g. a seed phrase). These keys and addresses can be organized into a
detector -
low Secrets in code
secret-high-entropy-tokenreferences/integration-guide.md:135High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- ✅ Valid: `0xd8…045`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/integration-guide.md:137High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- ❌ Invalid: `d8dA…045` (missing 0x)
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/workflows.md:17High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Get ERC20 transfers → `getE…ess` (primary, 0.05 per item)
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/workflows.md:26High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Get token holders → `getT…ess` (specialized, 0.02 per item)
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/workflows.md:97High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Example: Valid: `0xd8…045`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:58High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Get ERC20 transfer history | `getE…ess` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:68High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Get token holders | `getT…ess` |
table
Files scanned: 9. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1306 tokens
- 100Running it twice. No mutating operations
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 708: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.