CC lista-wallet-connect
Connect wallets via WalletConnect v2 and execute EVM signing/contract-call operations on Ethereum and BSC.
Not recommendedcritical or high security findings
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
Secrets in code
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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
-
high Secrets in code
meta-credential-files.envCredential / dotenv files bundled with the skill (1).env
Medium and low: 10
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:33High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7pY+zoMV…h0x/Ptw8…8dg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:49High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…b00+Gxjx…zRc/oZwU…hzA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:113High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:145High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Dsc+j03S…0oA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:417High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NS8+tHW7…WOF+PEzk…X4Q==",
detector -
low Secrets in code
secret-high-entropy-tokenreferences/chains.md:16High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC | 6 | `0xA0…B48` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/chains.md:17High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDT | 6 | `0xdA…ec7` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/chains.md:18High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| WETH | 18 | `0xC0…Cc2` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/chains.md:19High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| DAI | 18 | `0x6B…d0F` |
table -
low Secrets in code
secret-high-entropy-tokenreferences/chains.md:20High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| WBTC | 8 | `0x22…599` |
table
Files scanned: 55. 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 "repository" - note
frontmatter-keyunknown frontmatter key "node"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 60 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2530 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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)
- +3Description length 106: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 26 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
The skill largely does what it says, but it needs review because it can request wallet signatures and transactions while storing sensitive wallet/session artifacts locally with limited safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026