CD unified-dev-monitor
Unified Dev Wallet Monitor for BSC and Solana - Monitor only, manual buy only, no private keys
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 14
✓ No critical or high findings
Medium and low: 14
-
medium Secrets in code
secret-labelled-tokenbilling-final.js:9Labelled 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-tokenbilling.js:10Labelled 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-tokenSKILL.md:9Labelled token / key literal (vendor format unknown — verify it is not a live credential)api_key: sk_f…4b5
-
low Secrets in code
secret-password-literalbilling-final.js:9Hard-coded password / key literal (may be an example)const API_KEY = 'sk_f…4b5';
-
low Secrets in code
secret-password-literalbilling.js:10Hard-coded password / key literal (may be an example)const API_KEY = 'sk_f…4b5';
-
low Secrets in code
secret-high-entropy-tokenindex-bsc.js:11High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)WBNB_ADDRESS: '0xbb…95c'
quoted -
low Secrets in code
secret-high-entropy-tokenindex-sol-safe.js:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)WSOL_MINT: 'So11…112'
quoted -
low Secrets in code
secret-high-entropy-tokenREADME.md:41High-entropy token-like string (may be an id, hash or a credential)node index-sol-safe.js monitor 7xKX…AsU SOL 3600
-
low Secrets in code
secret-high-entropy-tokenREADME.md:52High-entropy token-like string (may be an id, hash or a credential)- **Router Address**: 0x10…24E
-
low Secrets in code
secret-password-literalSKILL.md:9Hard-coded password / key literal (may be an example)api_key: sk_f…4b5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:127High-entropy token-like string (may be an id, hash or a credential)- **Router Address**: 0x10…24E
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:270High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)WSOL_MINT: 'So11…112'
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:279High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)PANKCAKESWAP_ROUTER: '0x10…24E',
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:280High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)WBNB_ADDRESS: '0xbb…95c',
quoted
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "payment"
Process rating: all ten parameters 48/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (unified-dev-monitor) differs from the folder (sol-bsc-dev-monitor)
- 100Tools and files. No external tools needed
- 100Steps. 98 steps
- 100Execution cost. Instruction body is 2335 tokens
- 100Progress reporting. Reports progress
- low 23 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)
- +3Description length 94: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -255 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 57 headings
- +3Step-by-step instructions: 98 items
- +4Has examples (22 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.