AC bifrost-slpx-stake
Execute liquid staking operations on Bifrost SLPx protocol across Ethereum, Base, Optimism, and Arbitrum. Mint vETH by staking ETH/WETH, redeem vETH back to ETH, and claim after redemption completes. Supports manual signing and agent-side signing via ERC-4626 vault. Use when users want to stake, unstake, mint, redeem, or claim ETH on Bifrost DeFi.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:23High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Ethereum | 1 | `0xc3…4D8` | `0xC0…Cc2` | `https://ethereum.publicnode.com` | `https://1rpc.io/eth` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:24High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base | 8453 | `0xc3…4D8` | `0x42…006` | `https://base.publicnode.com` | `https://1rpc.io/base` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:25High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Optimism | 10 | `0xc3…4D8` | `0x42…006` | `https://optimism.publicnode.com` | `https://1rpc.io/op` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:26High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Arbitrum | 42161 | `0xc3…4D8` | `0x82…ab1` | `https://arbitrum-one.publicnode.com` | `https://1rpc.io/arb` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:38High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `BIFROST_VETH_ADDRESS` | VETH contract address (override) | `0xc3…4D8` |
table
Files scanned: 2. 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 53/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 35 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2805 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (4 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 349: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.