SKILLEMALL.ai
GitHub ↗ RU Sign in

BC streme-launcher

Launch tokens on Streme (streme.fun) - the streaming token platform on Base. Use when deploying SuperTokens with built-in staking rewards, Uniswap V3 liquidity, and optional vesting vaults. Triggers on "launch token on streme", "deploy streme token", "create supertoken", or any Streme token deployment task.

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 1 452 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Launch tokens on Streme (streme.fun) - the streaming token platform on Base. Use when deploying SuperTokens with built-in staking rewards, Uniswap V3…

As a process C 64/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice

IntegrationInfrastructuretype 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
86/100
safety, quality, tests
Safety 60%
80
Quality 40%
96
Run on models
none yet
Process rating
C
64/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
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

    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 Risky intent intent-wallet-secrets scripts/deploy-token.ts:10
      Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
      *   PRIVATE_KEY - Deployer wallet private key
    • low Secrets in code secret-high-entropy-token references/contracts.md:7
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      STRE…V2: '0x87…748',
      quoted
    • low Secrets in code secret-high-entropy-token references/contracts.md:8
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      STREME_SUPER_TOKEN_FACTORY: '0xB9…ce9',
      quoted
    • low Secrets in code secret-high-entropy-token references/contracts.md:9
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      STREME_ALLOCATION_HOOK: '0xC9…c7B',
      quoted
    • low Secrets in code secret-high-entropy-token references/contracts.md:10
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      LP_FACTORY: '0xfF…5C8',
      quoted
    • low Secrets in code secret-high-entropy-token references/contracts.md:13
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      STAK…V2: '0xC7…2c0',
      quoted
    • low Secrets in code secret-high-entropy-token scripts/deploy-token.ts:33
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      DEPLOYER: '0x87…748' as const,
      quoted
    • low Secrets in code secret-high-entropy-token scripts/deploy-token.ts:34
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      TOKEN_FACTORY: '0xB9…ce9' as const,
      quoted
    • low Secrets in code secret-high-entropy-token scripts/deploy-token.ts:35
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      ALLOCATION_HOOK: '0xC9…c7B' as const,
      quoted
    • low Secrets in code secret-high-entropy-token scripts/deploy-token.ts:36
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      LP_FACTORY: '0xfF…5C8' as const,
      quoted
    • low Exfiltration exfil-secret-in-url scripts/upload-image.ts:116
      Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
      ? `https://api.imgbb.com/1/upload?key=…
      placeholder
    • low Secrets in code secret-high-entropy-token SKILL.md:18
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      const DEPLOYER = '0x87…748';
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:46
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | STRE…_V2 | `0x87…748` |
      table
    • low Secrets in code secret-high-entropy-token SKILL.md:47
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | STREME_SUPER_TOKEN_FACTORY | `0xB9…ce9` |
      table
    • low Secrets in code secret-high-entropy-token SKILL.md:48
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | STREME_ALLOCATION_HOOK | `0xC9…c7B` |
      table
    • low Secrets in code secret-high-entropy-token SKILL.md:49
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | LP_FACTORY | `0xfF…5C8` |
      table

    Files scanned: 4. 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 64/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 7 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1452 tokens

    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

    • +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
    • +5Description quotes 3 example trigger phrases
    • +3Description length 308: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 11 items
    • +4Has examples (11 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 2 scripts are documented

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