SKILLEMALL.ai

CD Linux

Operate Linux systems avoiding permission traps, silent failures, and common admin mistakes.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 995 tokens Open the sourcegithub.com analyzed 2 d ago

Operate Linux systems avoiding permission traps, silent failures, and common admin mistakes.

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedurePersonal productivityInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
67/100
safety, quality, tests
Safety 60%
72
Quality 40%
60
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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.

Dangerous commands
If you install

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.

For the author

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

  1. 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.
  2. 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 · 7

  • high Dangerous commands cmd-persistence SKILL.md:63
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    - @reboot runs on daemon restart too, not just system reboot
Medium and low: 6
  • medium Dangerous commands cmd-privilege SKILL.md:11
    Privilege escalation / world-writable permissions
    - Setuid on scripts is ignored for security — only works on binaries
  • low Dangerous commands cmd-privilege SKILL.md:10
    Privilege escalation / world-writable permissions (quoted — discussed, not commanded)
    - `chmod 777` fixes nothing, breaks everything — find the actual owner/group issue
    quoted
  • low Dangerous commands cmd-background-process SKILL.md:18
    Starts a background / autostarted process (quoted — discussed, not commanded)
    - `nohup` doesn't work if process already running — use `disown` instead
    quoted
  • low Dangerous commands cmd-background-process SKILL.md:19
    Starts a background / autostarted process (negated — the text forbids it)
    - Background job with `&` still dies on terminal close without `disown` or `nohup`
    negated
  • low Dangerous commands cmd-background-process SKILL.md:52
    Starts a background / autostarted process (quoted — discussed, not commanded)
    - `systemctl enable` doesn't start service — also need `start`
    quoted
  • low Dangerous commands cmd-cron-mention SKILL.md:62
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    - Crontab lost if edited incorrectly — `crontab -l > backup` before editing
    quoted

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 46/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 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
  • 85Steps. 50 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 995 tokens
  • 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 92: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 50 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.