BC helius-openapi-skill
Operate Helius Wallet API reads through UXC with a curated OpenAPI schema, API-key auth, and read-first guardrails.
As a process C 61/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenreferences/usage-patterns.md:43High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)addresses:='["HXsK…664"]'
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/usage-patterns.md:47High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'{"addresses":["HXsK…664"]}'quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:86High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `helius-openapi-cli post:/v1/wallet/batch-identity addresses:='["HXsK…664"]'`
quoted
Files scanned: 6. 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")
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1082 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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 115: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: clean
The skill appears to provide purpose-aligned blockchain wallet research through Helius, with a privacy disclosure gap but no evidence of hidden, destructive, or privilege-seeking behavior.
LLM: benign (medium) · VirusTotal: · 29 May 2026