SKILLEMALL.ai
GitHub ↗ RU Sign in

CC agent-credit

Borrow from Aave via credit delegation. Agent self-funds by borrowing against delegator collateral. Supports borrow, repay, health checks. Works on Aave V2/V3.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: @aaronjmars v1.0.0 11 files · 4 scripts body ≈ 3 025 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

ProcedureAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
63/100
safety, quality, tests
Safety 60%
57
Quality 40%
72
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

Risky intent medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.

For the author

Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 22

  • high Dangerous commands cmd-pipe-to-shell SKILL.md:72
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    curl -L https://foundry.paradigm.xyz | bash && foundryup
Medium and low: 21
  • medium Risky intent intent-wallet-secrets SKILL.md:248
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    | `agentPrivateKey`        | Yes      | Agent wallet private key (0x-prefixed)        |
  • low Secrets in code secret-high-entropy-token config.example.json:4
    High-entropy token-like string (may be an id, hash or a credential) (placeholder value)
    "agentPrivateKey": "0xYO…KEY",
    placeholder
  • low Secrets in code secret-high-entropy-token config.example.json:6
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    "poolAddress": "0xA2…1c5",
    fixturequoted
  • low Secrets in code secret-high-entropy-token config.example.json:7
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    "dataProviderAddress": "0x2d…8Ac",
    fixturequoted
  • low Secrets in code secret-high-entropy-token config.example.json:10
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    "address": "0x83…913",
    fixturequoted
  • low Secrets in code secret-high-entropy-token config.example.json:18
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    "address": "0x2A…c22",
    fixturequoted
  • low Secrets in code secret-high-entropy-token contracts.md:10
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Pool (L2Pool)           | `0xA2…1c5`  |
    table
  • low Secrets in code secret-high-entropy-token contracts.md:11
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | PoolAddressesProvider   | `0xe2…64D`  |
    table
  • low Secrets in code secret-high-entropy-token contracts.md:12
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | PoolDataProvider        | `0x2d…8Ac`  |
    table
  • low Secrets in code secret-high-entropy-token contracts.md:13
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | WETHGateway             | `0x8b…f8C`  |
    table
  • low Secrets in code secret-high-entropy-token contracts.md:18
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | USDC  | `0x83…913` | 6        |
    table
  • low Secrets in code secret-high-entropy-token deployments.md:22
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Pool               | `0xA2…1c5` |
    table
  • low Secrets in code secret-high-entropy-token deployments.md:23
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | PoolAddressesProvider | `0xe2…64D` |
    table
  • low Secrets in code secret-high-entropy-token deployments.md:24
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | PoolDataProvider   | `0x2d…8Ac` |
    table
  • low Secrets in code secret-high-entropy-token deployments.md:28
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | USDC  | `0x83…913` | 6 | `0x4e…0AB` | `0x59…C28` |
    table
  • low Secrets in code secret-high-entropy-token deployments.md:29
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | WETH  | `0x42…006` | 18 | `0xD4…bb7` | `0x24…A1E` |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:89
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "poolAddress": "0xA2…1c5",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:90
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "dataProviderAddress": "0x2d…8Ac",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:93
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "address": "0x83…913",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:194
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Base      | `0xA2…1c5` | Very Low  |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:195
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Ethereum  | `0x87…4E2` | High      |
    table

Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 59/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. 7 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 44 steps, 1 vague phrases
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3025 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 159: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (12 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: suspicious
This skill is not deceptive, but it gives an agent live Aave borrowing authority using a plaintext wallet key and has gaps in the advertised financial safety checks.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026