BA api3-feed-manager
Discover, activate, fund, and maintain Api3 data feeds permissionlessly for downstream agent projects. Use when an agent needs a decentralized data feed pricing a blockchain based asset on a supported chain, needs to ensure feed runway for a build or deployment, or must maintain an already-enabled feed over time. Default to discovery, readiness checks, and dry-run planning first, and only use signer-backed execution when the user explicitly asks for it.
As a process A 86/100 · Runs to the end — weak spots: 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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokenreferences/part1-research.md:116High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- the package exposes **`comp…ess`**
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/part1-research.md:117High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- it also exposes **`comp…ess`**
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/api3-feed-manager.js:16High-entropy token-like string (may be an id, hash or a credential)Api3…ory,
-
low Secrets in code
secret-high-entropy-tokenscripts/api3-feed-manager.js:18High-entropy token-like string (may be an id, hash or a credential)comp…ess,
-
low Secrets in code
secret-high-entropy-tokenscripts/api3-feed-manager.js:924High-entropy token-like string (may be an id, hash or a credential)const communalProxy = chainState?.communalProxy || comp…ess(chainId, dapiName);
-
low Secrets in code
secret-high-entropy-tokenscripts/api3-feed-manager.js:1008High-entropy token-like string (may be an id, hash or a credential)const communalProxy = chainState?.communalProxy || comp…ess(chainId, dapiName);
-
low Secrets in code
secret-high-entropy-tokenscripts/api3-feed-manager.js:1459High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)from: '0x00…EaD',
quoted
Files scanned: 11. 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 86/100
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 125 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2268 tokens
- 100Running it twice. Mutating operations check current state
- low 10 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 457: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 125 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.