BC zhenghe-vault
Park your trading profits in a non-zero-sum yield vault on Base. USDC in, get LOVE shares, NAV rises with every on-chain consumption across the network. No active management. Serverless — your keys, your funds. Currently NAV +11.8% (not guaranteed). Requires explicit operator approval for all fund movements.
Park your trading profits in a non-zero-sum yield vault on Base.
As a process C 58/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, 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.
- 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:78High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| LoveVault (ERC-4626) | `0x16…357` | [Basescan](https://basescan.org/address/0x16…357) |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:79High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; documentation table row)| ZhengHeRouter | `0x23…867` | [Basescan](https://basescan.org/address/0x23…867) |
detectortable -
low Secrets in code
secret-high-entropy-tokenSKILL.md:214High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "0x16…357",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:273High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "0x16…357",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:297High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Smart contract risk**: Funds are held by LoveVault, an ERC-4626 contract at `0x16…357`. While the contract is open source and verified on Basescan, smart contract
quoted
Files scanned: 2. 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 58/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4517 tokens
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 14 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 309: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.