AD scripting-utils
Universal scripting utilities supporting 8+ languages (Bash, PowerShell, Python, Perl/Raku, JavaScript, Tcl), IRC bot frameworks (pbot, Limnoria), system management (systemd, Ubuntu/CentOS), and WebSearch integration. Provides syntax validation, code generation, best-practice linting, and cross-platform compatibility checks. Use when (1) Writing or validating scripts in any supported language, (2) Needing IRC bot command syntax, (3) Managing systemd services across Ubuntu/CentOS, (4) Validating JSON/API responses from web searches, (5) Converting between shell dialects, or (6) Batch-processing script validation.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-background-processscripts/system_manager.py:54Starts a background / autostarted process (string literal in code, not executed)ubuntu="systemctl enable {service}",code literal -
low Dangerous commands
cmd-background-processscripts/system_manager.py:55Starts a background / autostarted process (string literal in code, not executed)centos="systemctl enable {service}",code literal
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
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
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 755 tokens
- 100Running it twice. No mutating operations
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
- -239 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 619: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (5 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.