CC Engine miner Wallet
Secure operating guidance for the Engine miner Taproot wallet plugin on OpenClaw. Use for registration signing, safe claim handling, and refusal of unsafe wallet actions.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
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
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Risky intent
intent-wallet-secretsskill-card.md:21Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetMitigation: Show the recovery phrase only during explicit wallet creation after warning and confirmation, then direct the user to store it offline and never paste it back into chat. <br>
-
medium Risky intent
intent-wallet-secretsSKILL.md:24Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- remind the user that the mnemonic or seed phrase is sensitive and must be stored safely offline
-
medium Risky intent
intent-wallet-secretsSKILL.md:25Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- if the user asks the agent to create the wallet, warn that the recovery phrase will be shown once in chat and must be backed up immediately
-
medium Risky intent
intent-wallet-secretsSKILL.md:46Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- wallet creation can be done through `engine_miner_wallet_create`, but only after warning the user that the recovery phrase will be shown once in chat
-
medium Risky intent
intent-wallet-secretsSKILL.md:79Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- only reveal the recovery phrase during explicit wallet-creation flow after warning the user that it will appear in chat once
-
medium Risky intent
intent-wallet-secretsSKILL.md:80Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- never ask the user to paste the mnemonic or seed phrase into chat after wallet creation
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (Engine miner Wallet) differs from the folder (engine-miner-wallet)
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 6 branches
- 100Steps. 78 steps
- 100Execution cost. Instruction body is 1721 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 170: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.