BC sys-updater
Production-safe Ubuntu maintenance orchestrator: runs daily apt security updates, tracks non-security updates across apt/npm/pnpm/brew with quarantine + auto-review, applies only approved updates, rotates logs/state, and generates clear 09:00 MSK Telegram reports (including what was actually installed).
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
low Dangerous commands
cmd-cron-mentiondocs/operations.md:10Mentions editing / listing crontab (documentation of a security skill)crontab -e
security skill -
low Dangerous commands
cmd-cron-mentiondocs/operations.md:18Mentions editing / listing crontab (documentation of a security skill)crontab -e # Delete sys-updater lines
security skill -
low Dangerous commands
cmd-background-processdocs/scheduling.md:63Starts a background / autostarted process (documentation of a security skill)sudo systemctl enable --now sys-…mer
security skill -
low Dangerous commands
cmd-privilegedocs/sudoers.md:29Privilege escalation / world-writable permissions (documentation of a security skill)sudo chmod 440 /etc/sudoers.d/sys-updater
security skill -
low Dangerous commands
cmd-privilegeSKILL.md:141Privilege escalation / world-writable permissions (documentation of a security skill)sudo chmod 440 /etc/sudoers.d/sys-updater
security skill
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Production-safe Ubuntu maintenance orchestrator: runs daily apt se… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 48 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1077 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -49 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 304: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.