BC Linux Production Shell Scripts
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or…
As a process C 55/100 · Has gaps — weak spots: result and completion, failures and branches, consistency
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 · 4
-
high Dangerous commands
cmd-persistenceSKILL.md:344Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "$schedule_time $scheduled_task") | crontab -
Medium and low: 3
-
low Risky intent
intent-offensive-securitySKILL.md:13Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Provide production-ready shell script templates for common Linux system administration tasks including backups, monitoring, user management, log analysis, and automation. These scripts serve as buildi
detector -
low Dangerous commands
cmd-cron-mentionSKILL.md:344Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "$schedule_time $scheduled_task") | crontab -
-
low Dangerous commands
cmd-cron-mentionSKILL.md:492Mentions editing / listing crontab (documentation table row)| `crontab -e` | Edit cron jobs |
table
Files scanned: 1. 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)
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 40Consistency. Frontmatter name (Linux Production Shell Scripts) differs from the folder (linux-shell-scripting)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 15 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3012 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +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
- +5Description quotes 6 example trigger phrases
- +3Description length 266: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.