FC block-storage
Manage block storage volumes and LVM. Configure cloud block storage and local disks. Use when managing disk storage.
Manage block storage volumes and LVM.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
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.
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.
- 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 · 5
-
high Dangerous commands
cmd-destructive-fs-scopedSKILL.md:71Destructive command on a partition / current directory (normal in admin docs; verify the target)wipefs -a /dev/sdb1
-
high Dangerous commands
cmd-destructive-fs-scopedSKILL.md:78Destructive command on a partition / current directory (normal in admin docs; verify the target)mkfs.ext4 /dev/sdb1
-
high Dangerous commands
cmd-destructive-fs-scopedSKILL.md:84Destructive command on a partition / current directory (normal in admin docs; verify the target)mkfs.xfs /dev/sdb1
-
high Dangerous commands
cmd-destructive-fs-scopedSKILL.md:149Destructive command on a partition / current directory (normal in admin docs; verify the target)mkfs.ext4 /dev/data_vg/app_lv
-
high Dangerous commands
cmd-destructive-fs-scopedSKILL.md:266Destructive command on a partition / current directory (normal in admin docs; verify the target)mkfs.ext4 /dev/nvme1n1
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "license_source"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2871 tokens
- low 11 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 116: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 17 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.