BB agentic-lending-evk
Plan and execute the current EVK-first agentic lending workflow for Api3-backed markets. Use when a user wants an agent to resolve the oracle route for selected collateral and borrow assets, discover or fund the required Api3 feeds, including browser-assisted Api3 Market funding when needed, prepare the Euler oracle path, assemble and deploy the EVK lending market, and then prove real borrowability with a post-deploy canary borrow against the intended collateral path. This variant can reach real onchain writes, including feed funding, market deployment, approvals, swaps, and borrow canaries when explicitly allowed. Default to plan, simulation, or preview mode first, and only use live signer-backed execution when the user explicitly asks for it. Do not use for Morpho, unsupported recipes, or unsupported oracle/deployment routes.
As a process B 79/100 · Nearly there — weak spots: running it twice, progress reporting
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 · 30
✓ No critical or high findings
Medium and low: 30
-
low Secrets in code
secret-high-entropy-tokendata/part2/contract-artifacts/Api3PartialAggregatorV2V3Interface.json:2High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"contractName": "Api3…ace",
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/evk-addresses.api3-supported-overlap.json:14High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"evc": "0x0C…383",
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/evk-addresses.api3-supported-overlap.json:15High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"eVaultFactory": "0x29…C8e"
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/evk-addresses.api3-supported-overlap.json:18High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"edgeFactory": "0xA9…9Bd",
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/evk-addresses.api3-supported-overlap.json:19High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"evkFactoryPerspective": "0xB3…182",
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/evk-addresses.api3-supported-overlap.json:20High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"escrowedCollateralPerspective": "0x4e…DdE"
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/feed-status.json:7High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"supp…ace": true,
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/feed-status.json:19High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"supp…ace": true,
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/feed-status.json:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"supp…ace": true,
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/feed-status.json:43High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"supp…ace": true,
quoted -
low Secrets in code
secret-high-entropy-tokendata/part2/feed-status.json:57High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"supp…ace": true,
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/api_reference.md:122High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){ "symbol": "USDC", "address": "0xaf…831" }quoted -
low Secrets in code
secret-high-entropy-tokenreferences/arbitrum-eusdc1-isolated-example.json:4High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"accountAddress": "0x00…EaD",
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/arbitrum-eusdc1-isolated-example.json:20High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"address": "0xaf…831",
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/arbitrum-eusdc1-isolated-example.json:27High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"address": "0x9d…5Fe"
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/arbitrum-eusdc1-isolated-example.json:31High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"address": "0x0a…899"
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/arbitrum-eusdc1-isolated-example.json:36High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"address": "0x78…dFF"
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/current_capabilities.md:27High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `Api3…ace` deployment can be executable
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/example-request.json:15High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"address": "0xaf…831"
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/live-request-template.json:15High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0xaf…831"
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/api3-feed-manager.js:16High-entropy token-like string (may be an id, hash or a credential)Api3…ory,
-
low Secrets in code
secret-high-entropy-tokenscripts/lib/api3-feed-manager.js:18High-entropy token-like string (may be an id, hash or a credential)comp…ess,
-
low Secrets in code
secret-high-entropy-tokenscripts/lib/api3-feed-manager.js:931High-entropy token-like string (may be an id, hash or a credential)const communalProxy = chainState?.communalProxy || comp…ess(chainId, dapiName);
-
low Secrets in code
secret-high-entropy-tokenscripts/lib/api3-feed-manager.js:1015High-entropy token-like string (may be an id, hash or a credential)const communalProxy = chainState?.communalProxy || comp…ess(chainId, dapiName);
-
low Secrets in code
secret-high-entropy-tokenscripts/lib/api3-feed-manager.js:1466High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)from: '0x00…EaD',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/part2-planner.js:22High-entropy token-like string (may be an id, hash or a credential)Api3…ce: path.join(CONTRACT_ARTIFACT_DIR, 'Api3PartialAggregatorV2V3Interface.json'),
-
low Secrets in code
secret-high-entropy-tokenscripts/lib/part2-planner.js:171High-entropy token-like string (may be an id, hash or a credential)supp…ce: classification !== 'unsupported',
-
low Secrets in code
secret-high-entropy-tokenscripts/lib/part2-planner.js:1991High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'Api3…ace remains the preferred compatibility layer for Api3-backed legs.',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/part2-planner.js:2003High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'Api3 via Api3…ace is the default route when a direct compatible feed is sufficient.',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib/part2-planner.js:2121High-entropy token-like string (may be an id, hash or a credential)supp…ce: true,
Files scanned: 35. 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 79/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 55 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 144 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 10 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3405 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
- 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
- +3Description length 839: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 12 headings
- +3Step-by-step instructions: 144 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.