SKILLEMALL.ai

BB clawmegle-staking

Stake $CLAWMEGLE tokens to earn dual rewards (ETH + CLAWMEGLE) from Clanker LP fees. Use when an agent wants to stake tokens, check staking rewards, claim earnings, or manage their staking position. Supports both Bankr API and direct wallet transactions.

modbender/skill-library-mcp Agent Skills author: modbender MIT 18 files · 13 scripts body ≈ 1 345 tokens Open the sourcegithub.com analyzed 2 d ago

Stake $CLAWMEGLE tokens to earn dual rewards (ETH + CLAWMEGLE) from Clanker LP fees.

As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
80
Quality 40%
85
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope 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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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

    ✓ No critical or high findings

    Medium and low: 16
    • medium Broad scope meta-agent-memory-dump HEARTBEAT.md
      Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
      HEARTBEAT.md
    • low Secrets in code secret-high-entropy-token HEARTBEAT.md:9
      High-entropy token-like string (may be an id, hash or a credential)
      ETH_PENDING=$(cast call 0x56…Cf4 "pendingRewards(address)(uint256,uint256)" $WALLET --rpc-url https://mainnet.base.org | head -1)
    • low Secrets in code secret-high-entropy-token HEARTBEAT.md:10
      High-entropy token-like string (may be an id, hash or a credential)
      CLAWMEGLE_PENDING=$(cast call 0x56…Cf4 "pendingRewards(address)(uint256,uint256)" $WALLET --rpc-url https://mainnet.base.org | tail -1)
    • low Secrets in code secret-high-entropy-token HEARTBEAT.md:25
      High-entropy token-like string (may be an id, hash or a credential)
      STAKED=$(cast call 0x56…Cf4 "getStakedAmount(address)(uint256)" $WALLET --rpc-url https://mainnet.base.org)
    • low Secrets in code secret-high-entropy-token README.md:11
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - **Staking Contract:** `0x56…Cf4` (Base)
      quoted
    • low Secrets in code secret-high-entropy-token README.md:12
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      - **CLAWMEGLE Token:** `0x94…07c` (Base)
      quoted
    • low Secrets in code secret-high-entropy-token references/bankr-format.md:19
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      scripts/bankr.sh "Submit this transaction on Base: {\"to\": \"0x94…07c\", \"data\": \"0x09…000<STAK…_0x>0000000000000000000000
      quoted
    • low Secrets in code secret-high-entropy-token references/contract.md:7
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | ClawmegleClientRewards | `0x56…Cf4` | Base |
      table
    • low Secrets in code secret-high-entropy-token references/contract.md:8
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | $CLAWMEGLE Token | `0x94…07c` | Base |
      table
    • low Secrets in code secret-high-entropy-token scripts/bankr-stake.sh:15
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      TOKEN="0x94…07c"
      quoted
    • low Secrets in code secret-high-entropy-token scripts/deposit-rewards.sh:13
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      STAKING_CONTRACT="0x56…Cf4"
      quoted
    • low Secrets in code secret-high-entropy-token scripts/deposit-rewards.sh:14
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      CLAWMEGLE_TOKEN="0x94…07c"
      quoted
    • low Secrets in code secret-high-entropy-token scripts/stake-bankr.sh:17
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      TOKEN="0x94…07c"
      quoted
    • low Secrets in code secret-high-entropy-token scripts/stake.sh:17
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      TOKEN="0x94…07c"
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:137
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | **Contract** | `0x56…Cf4` (deployment pending) |
      table
    • low Secrets in code secret-high-entropy-token SKILL.md:138
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | **Token** | `0x94…07c` |
      table

    Files scanned: 18. 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 67/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 4 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 26 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1345 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 12 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
    • -32 of 13 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 254: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 26 items
    • +4Has examples (12 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)

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