FD monero-pool-comparison
(no description)
Compare and choose the best Monero mining pool for your needs.
As a process D 44/100 · Unfinished process — 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.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
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.
- Add a description to the frontmatter: without it the skill never triggers.
- 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 · 8
-
high Dangerous commands
cmd-cryptominerskill-card.md:37Installs or runs a cryptocurrency miner on the user's machine- [XMRig pool documentation](https://xmrig.com/docs/miner/pool)
-
high Dangerous commands
cmd-cryptominerskill-card.md:48Installs or runs a cryptocurrency miner on the user's machine**Other Properties Related to Output:** [May include XMRig pool configuration snippets, pool-selection criteria, and safety guidance.]
-
high Dangerous commands
cmd-cryptominerSKILL.md:68Installs or runs a cryptocurrency miner on the user's machineTo switch, update your XMRig config:
-
high Dangerous commands
cmd-cryptominerSKILL.md:78Installs or runs a cryptocurrency miner on the user's machineRestart XMRig to connect to the new pool.
-
high Dangerous commands
cmd-cryptominerSKILL.md:83Installs or runs a cryptocurrency miner on the user's machine- **XMRig API**: Enable `"api": {"port": 42000}` in config to monitor locally -
high Dangerous commands
cmd-cryptominerSKILL.md:105Installs or runs a cryptocurrency miner on the user's machine- XMRig documentation: https://xmrig.com/docs/miner/pool
Medium and low: 2
-
medium Dangerous commands
cmd-cryptominerSKILL.md:72Installs or runs a cryptocurrency miner on the user's machine (quoted — discussed, not commanded)"url": "pool…333",
quoted -
medium Obfuscation
obf-base64-blobSKILL.md:113Long base64-looking blob48Gb…Bbu
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 44/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 949 tokens
- 100Running it twice. No mutating operations
- low 10 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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.