Name: os-scripting
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

os-scripting

Operating system and shell scripting troubleshooting workflow for Linux, macOS, and Windows. Covers bash scripting, system administration, debugging, and automation.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/os-scripting/SKILL.md

The canonical home for this skill is os-scripting in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with comprehensive executable examples, but it is a long monolithic inlined document with no progressive disclosure via reference files, and its destructive/batch workflow steps lack inline validation feedback loops.

Suggestions

Add per-phase validation checkpoints (e.g., verify ShellCheck passes before moving from Phase 2 to Phase 4; confirm service restart succeeded before scheduling automation) to satisfy the destructive/batch feedback-loop cap.

Move the large reusable artifacts — the full bash script template, the bats test examples, and the command catalogs — into reference files under references/ and link to them one level deep to improve progressive disclosure.

Trim the repetitive 'Copy-Paste Prompts' blocks (one generic prompt pattern would cover all phases) to reduce token bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with abundant actionable code, but the repetitive per-phase 'Copy-Paste Prompts' blocks and generic numbered 'Actions' lists add bulk that could be tightened without losing value.	3 / 5
Actionability	Fully executable, copy-paste-ready code and commands throughout — diagnostic commands, a complete bash script template, ShellCheck usage, bats tests, cron/systemd examples, and per-scenario troubleshooting command sets covering the common cases.	5 / 5
Workflow Clarity	Seven phases are clearly sequenced and a final Quality Gates checklist exists, but destructive/batch operations (service restarts, disk finds, cron scheduling) lack per-step validate-then-proceed feedback loops, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Section and phase headers give decent structure, but with no bundle files in references/scripts/assets the entire ~420-line catalog is inlined monolithically with no one-level-deep external references to split out the script template, command catalogs, or test examples.	3 / 5
	Total	14 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the workflow covers but lacks an explicit 'Use when...' trigger clause, capping completeness. Trigger terms are strong, though the named actions are category-level rather than concrete.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when debugging a failing bash script, troubleshooting a hung service, or automating a sysadmin task').

Replace generic category words ('system administration', 'automation') with concrete actions ('restart services', 'schedule cron jobs', 'parse logs') to lift specificity.

Narrow the niche or add a distinguishing qualifier to reduce overlap with the related cloud-devops and development bundles.

Dimension	Reasoning	Score
Specificity	Names the domain (OS/shell scripting troubleshooting) plus several actions ('bash scripting, system administration, debugging, and automation'), but these are high-level categories rather than concrete specific actions like 'extract text' or 'fill forms'.	3 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('bash scripting', 'debugging', 'system administration', 'automation', plus 'Linux, macOS, Windows'), giving good keyword coverage with only a few common variations missing.	4 / 5
Distinctiveness Conflict Risk	The OS/shell scripting troubleshooting niche is somewhat specific but broad, with real overlap risk against the related bundles it lists (development, cloud-devops, security-audit, database).	3 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/os-scripting/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.