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

78%

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

65%

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

A highly actionable catalog of ready-to-use bash scripts with good internal organization, but it is a long monolithic file that teaches some basics Claude already knows and lacks validation checkpoints for its destructive batch operations. Splitting templates into reference files and trimming the Quick Reference would lift the weaker dimensions.

Suggestions

Move the template catalog into separate per-domain reference files (e.g. references/backup-scripts.md, references/monitoring-scripts.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add explicit validation/feedback steps to destructive and batch scripts — e.g. verify tar/rsync exit codes, confirm mysqldump succeeded before gzip, and test in non-production before rotation deletes oldest backups.

Trim the Quick Reference table entries that restate bash fundamentals Claude already knows (shebang, $(date), $((expression)), ${var:-default}); keep only skill-specific conventions.

Dimension	Reasoning	Score
Conciseness	The body is a ~500-line catalog of complete scripts that is mostly lean per-item, but the overall volume is high and the Quick Reference explains basics Claude already knows (shebang, $(date), $((expression)), ${var:-default}).	2 / 3
Actionability	Every section provides fully executable, copy-paste-ready bash scripts with concrete commands (tar, rsync, mysqldump, openssl, find, etc.) rather than pseudocode or abstract direction.	3 / 3
Workflow Clarity	Content is organized into numbered phases, but it is a collection of independent scripts rather than a sequenced process, and destructive/batch operations (backup rotation, db dump, cleanup) lack explicit validation or feedback checkpoints.	2 / 3
Progressive Disclosure	Internal sectioning (phases, Quick Reference) is reasonable, but everything lives in one monolithic ~500-line file with no bundle files or one-level-deep references to split out the large template catalog.	2 / 3
	Total	9 / 12 Passed

Description

92%

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: concrete capabilities, natural trigger terms, third-person voice, and explicit 'Use when' guidance covering both what and when. Its only weakness is that a couple of triggers are broad enough to risk overlap with adjacent sysadmin/automation skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "create bash scripts", "backup files", "manage users", "monitor system resources" — and states it "provides ready-to-use shell script templates", listing specific concrete actions rather than vague language.	3 / 3
Completeness	It explicitly answers what ("provides ready-to-use shell script templates for system administration") and when ("This skill should be used when the user asks to ..."), with an explicit 'Use when'-style trigger clause.	3 / 3
Trigger Term Quality	The quoted triggers ("create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", "write production shell scripts") are natural phrases a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The shell-scripting/sysadmin niche is clear, but broad triggers like "automate Linux tasks" and "monitor system resources" could overlap with other automation or monitoring skills, so it is not maximally distinctive.	2 / 3
	Total	11 / 12 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: af7d491

Reviewed: about 9 hours 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.