BC 31third-safe-rebalancer-simple
One-step Safe rebalancer using on-chain 31Third policies.
One-step Safe rebalancer using on-chain 31Third policies.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:157High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…QYA+ISs0/2l3T9/kj42…aQT/dfNXWX/ZZCQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:361High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-6+gjmF…uh8+uw3mnrvgs+dSPQ…dZG+D4garKg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:378High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…DUr+vOv8…A8A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:448High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…jgR+Mkmf+D189…ihQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:600High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Dl4/xSdo…8U8+Zxkn…TtH+z95HTmg==",
detector
Files scanned: 15. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1272 tokens
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 57: 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: 11 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.