SKILLEMALL.ai
GitHub ↗ RU Sign in

AB fxusd

Use when the user wants to deploy, unwind, or compare fxUSD-related yield strategies on Base. Covers minting and redeeming fxSAVE, discovering and managing Hydrex single-sided liquidity vaults, and planning Morpho supply or borrow workflows with protocol-specific risk controls. Uses the fxSAVE backend plus public Hydrex and Morpho APIs for planning, and emits Bankr-ready transaction steps for execution.

ClawHub Agent Skills author: Tao Wang v1.0.1 MIT-0 8 files body ≈ 3 393 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting

ProcedureInfrastructuretype 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
A
90/100
safety, quality, tests
Safety 60%
89
Quality 40%
91
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    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 · 11

    ✓ No critical or high findings

    Medium and low: 11
    • low Secrets in code secret-high-entropy-token scripts/fxusd_cli.py:26
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "USDC": Token("USDC", "0x83…913", 6),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_hydrex.py:22
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      DEPOSIT_GUARD = "0x9A…8d8"
      detector
    • low Secrets in code secret-high-entropy-token scripts/fxusd_hydrex.py:23
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      VAULT_DEPLOYER = "0x7d…fEE"
      detector
    • low Secrets in code secret-high-entropy-token scripts/fxusd_hydrex.py:36
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "USDC": Token("USDC", "0x83…913", 6),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_hydrex.py:38
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "BNKR": Token("BNKR", "0x22…F3b", 18),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_hydrex.py:39
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "HYDX": Token("HYDX", "0x00…B30", 18),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_morpho.py:21
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      MORPHO_BLUE_ADDRESS = "0xBB…FCb"
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_morpho.py:35
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "USDC": Token("USDC", "0x83…913", 6),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_morpho.py:37
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "wstETH": Token("wstETH", "0xc1…452", 18),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_morpho.py:38
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "cbBTC": Token("cbBTC", "0xcb…3Bf", 8),
      quoted
    • low Secrets in code secret-high-entropy-token scripts/fxusd_morpho.py:39
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "BNKR": Token("BNKR", "0x22…F3b", 18),
      quoted

    Files scanned: 8. 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 65/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 60Failures and branches. 2 branches
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 154 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3393 tokens
    • 100Running it twice. Mutating operations check current state
    • 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 406: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 154 items
    • +4Has examples (9 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 3 scripts are documented

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

    External checks

    ClawHub: suspicious
    This DeFi skill is coherent and not clearly malicious, but it needs Review because it prepares executable wallet transactions using third-party data and some high-impact flows lack strong execution safeguards.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026