SKILLEMALL.ai
GitHub ↗ RU Sign in

DD bsc-dev-monitor

BSC Dev Wallet Monitor - 专为跟投 Dev 的用户设计。 监控指定 BSC 地址的代币转出（发币）行为，第一时间发现新币发布。 支持 Webhook 通知、安全检测、历史记录等功能。

Not recommendedlow grade D
ClawHub Agent Skills author: mybusd v1.0.1 22 files · 1 script body ≈ 927 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

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
D
45/100
safety, quality, tests
Safety 60%
30
Quality 40%
68
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: bsc-dev-monitor (ClawHub)

What is at stake

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

Secrets in code 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 files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

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

✓ No critical or high findings

Medium and low: 30
  • medium Secrets in code secret-labelled-token BILLING-UPDATE-COMPLETE.md:17
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    api_key: sk_f…4b5
  • medium Secrets in code secret-labelled-token BILLING-UPDATE-COMPLETE.md:245
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    - API Key: `sk_f…4b5`
  • medium Secrets in code secret-labelled-token billing.js:6
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    const API_KEY = 'sk_f…4b5';
  • medium Secrets in code secret-labelled-token index-enhanced.js:13
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apiKey: 'JM67…PH1',
  • medium Secrets in code secret-labelled-token index-updated.js:16
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apiKey: 'sk_f…4b5',
  • medium Secrets in code secret-labelled-token index-updated.js:29
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apiKey: 'JM67…PH1',
  • medium Secrets in code secret-labelled-token index.js:17
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apiKey: 'sk_f…4b5',
  • medium Secrets in code secret-labelled-token index.js:30
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apiKey: 'JM67…PH1',
  • medium Secrets in code secret-labelled-token README.md:72
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    apiKey: 'sk_f…4b5',
  • medium Secrets in code secret-labelled-token SKILL.md:12
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    api_key: sk_f…4b5
  • low Secrets in code secret-password-literal auto-deploy.js:15
    Hard-coded password / key literal (may be an example)
    password: 'hefa…633'
  • low Secrets in code secret-password-literal BILLING-UPDATE-COMPLETE.md:17
    Hard-coded password / key literal (may be an example)
    api_key: sk_f…4b5
  • low Secrets in code secret-password-literal billing.js:6
    Hard-coded password / key literal (may be an example)
    const API_KEY = 'sk_f…4b5';
  • low Secrets in code secret-password-literal index-enhanced.js:13
    Hard-coded password / key literal (may be an example)
    apiKey: 'JM67…PH1',
  • low Secrets in code secret-high-entropy-token index-enhanced.js:23
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0x69…933': '0x4f…1a4', // PEPE
    quoted
  • low Secrets in code secret-high-entropy-token index-enhanced.js:24
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0xfb…F7c': '0x74…bEb', // FLOKI
    quoted
  • low Secrets in code secret-high-entropy-token index-enhanced.js:25
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0xd0…dA0': '0x10…24E', // BONK
    quoted
  • low Secrets in code secret-high-entropy-token index-enhanced.js:26
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0xc7…2C1': '0x25…0Cb'  // BABYDOGE
    quoted
  • low Secrets in code secret-password-literal index-updated.js:16
    Hard-coded password / key literal (may be an example)
    apiKey: 'sk_f…4b5',
  • low Secrets in code secret-password-literal index-updated.js:29
    Hard-coded password / key literal (may be an example)
    apiKey: 'JM67…PH1',
  • low Secrets in code secret-high-entropy-token index-updated.js:39
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0x69…933': '0x4f…1a4',
    quoted
  • low Secrets in code secret-high-entropy-token index-updated.js:40
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0xfb…F7c': '0x74…bEb',
    quoted
  • low Secrets in code secret-high-entropy-token index-updated.js:41
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0xd0…dA0': '0x10…24E',
    quoted
  • low Secrets in code secret-high-entropy-token index-updated.js:42
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    '0xc7…2C1': '0x25…0Cb'
    quoted
  • low Secrets in code secret-password-literal index.js:17
    Hard-coded password / key literal (may be an example)
    apiKey: 'sk_f…4b5',
  • low Secrets in code secret-password-literal index.js:30
    Hard-coded password / key literal (may be an example)
    apiKey: 'JM67…PH1',
  • low Secrets in code secret-labelled-token mock-deploy.js:18
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (test fixture / example file)
    api_key: 'sk_f…4b5',
    fixture
  • low Secrets in code secret-password-literal mock-deploy.js:18
    Hard-coded password / key literal (may be an example) (test fixture / example file)
    api_key: 'sk_f…4b5',
    fixture
  • low Secrets in code secret-password-literal README.md:72
    Hard-coded password / key literal (may be an example)
    apiKey: 'sk_f…4b5',
  • low Secrets in code secret-password-literal SKILL.md:12
    Hard-coded password / key literal (may be an example)
    api_key: sk_f…4b5

Files scanned: 22. 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")
  • note frontmatter-key unknown frontmatter key "payment"

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (bsc-dev-monitor) differs from the folder (bsc-dev-monitor-v2)
  • 100Tools and files. No external tools needed
  • 100Steps. 25 steps
  • 100Execution cost. Instruction body is 927 tokens
  • 100Running it twice. No mutating operations

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)
  • +3Description length 103: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (11 code blocks)

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

External checks

ClawHub: suspicious
The wallet monitor is mostly recognizable, but the package exposes payment and platform credentials and includes deployment/publishing actions that are not appropriate for an end-user monitoring skill.
LLM: suspicious (high) · VirusTotal: · 29 May 2026