SKILLEMALL.ai
GitHub ↗ RU Sign in

BC warren-nft

Deploy NFT collections permanently on MegaETH mainnet. Images are stored on-chain via SSTORE2, then published through WarrenContainer and WarrenLaunchedNFT.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files · 1 script body ≈ 1 783 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Deploy NFT collections permanently on MegaETH mainnet.

As a process C 57/100 · Has gaps — weak spots: when it triggers, consistency, running it twice

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
B
81/100
safety, quality, tests
Safety 60%
85
Quality 40%
75
Run on models
none yet
Process rating
C
57/100
Has gaps
Progress reporting w 2
0
When it triggers w 12
20
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.

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

✓ No critical or high findings

Medium and low: 11
  • medium Risky intent intent-wallet-secrets SKILL.md:74
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    | `PRIVATE_KEY` | **Yes** | — | Wallet private key for signing transactions |
  • low Secrets in code secret-high-entropy-token deploy-nft.js:24
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const GENESIS_KEY_ADDRESS = process.env.GENESIS_KEY_ADDRESS || '0x0d…a88';
    quoted
  • low Secrets in code secret-high-entropy-token deploy-nft.js:25
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const RABBIT_AGENT_ADDRESS = process.env.RABBIT_AGENT_ADDRESS || '0x3f…1f2';
    quoted
  • low Secrets in code secret-high-entropy-token deploy-nft.js:26
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const CONTAINER_ADDRESS = process.env.CONTAINER_ADDRESS || '0x65…964';
    quoted
  • low Secrets in code secret-high-entropy-token deploy-nft.js:27
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const RENDERER_ADDRESS = process.env.RENDERER_ADDRESS || '0xdC…6BB';
    quoted
  • low Risky intent intent-wallet-secrets deploy-nft.js:509
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)
    --private-key <key>       Wallet private key (or set PRIVATE_KEY env)
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:55
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    Default `RABBIT_AGENT_ADDRESS`: `0x3f…1f2` (override via env).
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:64
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Genesis Key NFT (0xRabbitNeo) | `0x0d…a88` |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:65
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | 0xRa…ent Key NFT | `0x3f…1f2` |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:66
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | WarrenContainer | `0x65…964` |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:67
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | WarrenContainerRenderer | `0xdC…6BB` |
    table

Files scanned: 6. 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 57/100

  • 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
  • 40Consistency. Frontmatter name (warren-nft) differs from the folder (warren-nft-mainnet)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 26 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 1783 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
  • low The response is described with custom markup (9 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 156: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 26 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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