AC venus-protocol-ops
Analyze Venus Protocol lending/borrowing positions on BNB Chain with risk-first guidance. Use when users ask about Venus markets, collateral/borrow decisions, health factor, liquidation risk, APY/utilization comparison, isolated pools, or "can I borrow X safely" style what-if checks.
As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
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-tokenreferences/flux-bnb-addresses.json:6High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"lendingResolver": "0x48…569",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/flux-bnb-addresses.json:7High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"lendingFactory": "0x54…D03",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/flux-bnb-addresses.json:9High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"symbol": "fU", "address": "0x00…69c"},quoted -
low Secrets in code
secret-high-entropy-tokenreferences/flux-bnb-addresses.json:10High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"symbol": "fUSDC", "address": "0xfE…Df9"},quoted -
low Secrets in code
secret-high-entropy-tokenreferences/flux-bnb-addresses.json:11High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"symbol": "fUSDT", "address": "0xA5…6A2"},quoted
Files scanned: 30. 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 60/100
- 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
- 40Consistency. Frontmatter name (venus-protocol-ops) differs from the folder (venus-agent-skills)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 50 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1153 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +4No input/output examples
- -31 of 12 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 284: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (6 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.