AC stakingverse-lukso
Stake LYX tokens on Stakingverse (LUKSO liquid staking). Use when the user wants to stake LYX, unstake LYX, claim rewards, or check sLYX balance on Stakingverse. Supports deposit, withdrawal requests, and oracle-claim pattern.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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-tokenREADME.md:68High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Address:** `0x9F…F04`
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/balance.js:5High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const STAKINGVERSE_VAULT = '0x9F…F04';
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/claim.js:6High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const STAKINGVERSE_VAULT = '0x9F…F04';
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/stake.js:7High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const STAKINGVERSE_VAULT = '0x9F…F04';
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/unstake-request.js:6High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const STAKINGVERSE_VAULT = '0x9F…F04';
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:23High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)export STAKINGVERSE_VAULT="0x9F…F04"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:64High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Vault | `0x9F…F04` | Staking/unstaking logic |
table
Files scanned: 7. 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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1964 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 226: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (10 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.