linux-shell-scripting

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/linux-shell-scripting/SKILL.md

Quality

Content

61%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 skill is highly actionable with many ready-to-run scripts, but it is a monolithic document that inlines basic-bash padding and omits validation/feedback loops for destructive and batch operations. Splitting categories into reference files and adding verification steps would materially improve it.

Suggestions

Add explicit validation/verification checkpoints (e.g. test backups in a non-production path, verify restored data, confirm a script succeeded before proceeding) for destructive and batch scripts such as backup rotation, data cleanup, and package installation.

Split the ten script categories into one-level-deep reference files (e.g. references/backups.md, references/monitoring.md) and keep SKILL.md as a concise overview that links to them, improving progressive disclosure.

Remove or trim the Quick Reference tables that explain basic bash concepts Claude already knows (shebang, date formatting, default-value syntax) to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-first sections, but the Quick Reference tables explain basic bash concepts Claude already knows (shebang, date formatting, default-value syntax), and Prerequisites/Outputs add mild padding that could be trimmed.	3 / 5
Actionability	Numerous fully executable, copy-paste-ready bash scripts with real commands covering backups, monitoring, user management, encryption, log analysis, networking, and automation across common cases.	5 / 5
Workflow Clarity	Phases are organized but consist of independent scripts rather than a sequenced process, and several destructive/batch operations (rm -r rotation, find -exec rm, apt-get install, mysqldump with hardcoded credentials) lack validation checkpoints or feedback loops, capping this dimension.	3 / 5
Progressive Disclosure	A monolithic ~500-line SKILL.md inlines all ten categories of scripts with no bundle files and no references/navigation to split content into one-level-deep materials, so structure is minimal.	2 / 5
	Total	13 / 20 Passed

Description

88%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.

A strong description that clearly states both the capability set and explicit use-when triggers with natural phrasing. Minor room to improve distinctiveness and add a few more synonyms or extension-based triggers.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", "write production shell scripts") and "ready-to-use shell script templates", giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both what ("provides ready-to-use shell script templates for system administration") and when ("This skill should be used when the user asks to...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural phrases users would say ("create bash scripts", "automate Linux tasks", "backup files", "manage users"), but lacks some synonyms or file-extension variants that would push it to comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The Linux system-administration niche has distinct triggers, though there is minor overlap risk with general coding or DevOps skills covering similar scripting territory.	4 / 5
	Total	18 / 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
skill_md_line_count	SKILL.md is long (505 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/linux-shell-scripting/SKILL.md
Commit: 59c5fc4

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.