bash-linux

Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

Quality

63%

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 ./skills/bash-linux/SKILL.md

Quality

Content

57%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 — every entry is a concrete, executable command or complete script template. Its main weaknesses are substantial redundancy with knowledge Claude already has in the basic command tables, missing validation around destructive process-killing commands, and a monolithic single-file layout with no reference splitting.

Suggestions

Cut or collapse sections that restate basics Claude already knows (Operator Syntax, Essential Commands, Environment Variables) and keep only non-obvious patterns like the lsof/kill pipeline, trap-based cleanup, and the hardening script template.

Add validation before destructive commands, e.g. checking the process identity with "ps -p <PID> -o command=" or listing listeners with "lsof -i :3000" before kill -9.

Split the reference tables (e.g. PowerShell comparison, full command catalog) into separate reference files linked from a concise overview in SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Sections 1, 2, and 5 tabulate basics Claude already knows ("ls -la", "cat file.txt", "echo $PATH", "npm install && npm run dev"), so a large fraction of the body restates existing knowledge even though the tables themselves are terse, matching anchor 2 rather than 3.	2 / 5
Actionability	Everything is concrete and executable: "kill -9 $(lsof -t -i :3000)", "sed -i 's/old/new/g' file.txt", a complete runnable script template with set -euo pipefail, and a working "while IFS= read -r line" loop — copy-paste ready and covering common cases, matching anchor 5.	5 / 5
Workflow Clarity	As a reference cheat-sheet it has no multi-step sequence to validate, but it presents destructive operations ("kill -9 <PID>", "kill -9 $(lsof -t -i :3000)", "rm -f /tmp/tempfile") with no pre-checks or verification steps, which caps workflow clarity at 3 per the rubric's destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in one file; the numbered sections and tables give real structure, but content that would fit separate reference files (e.g. the PowerShell comparison table, full command tables) is inline with no references, matching anchor 3.	3 / 5
	Total	13 / 20 Passed

Description

70%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 is concise, in third person, and covers both what the skill does and when to use it, with solid natural keywords. Its weaknesses are topic-noun phrasing instead of concrete actions and an over-broad when-clause that dilutes distinctiveness.

Suggestions

Convert the topic list into concrete actions, e.g. "Chains commands, manages processes and ports, processes text with grep/sed/awk, and writes safe scripts with error handling and traps."

Tighten the when-clause to concrete triggers, e.g. "Use when writing shell scripts, chaining or piping commands, managing processes/ports, or debugging terminal commands on macOS or Linux."

Add common synonyms such as "shell", "command line", or "CLI" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Critical commands, piping, error handling, scripting" names several concrete topic areas, but these are noun-phrase topics rather than explicit actions (no verbs like 'extract', 'kill processes', or 'write scripts'), matching anchor 3 rather than 4.	3 / 5
Completeness	Explicitly answers both what ("Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting.") and when ("Use when working on macOS or Linux systems"), but the when-clause is broad and lacks concrete trigger phrases, matching anchor 4.	4 / 5
Trigger Term Quality	Includes natural terms users would say — "Bash", "Linux", "terminal", "commands", "piping", "macOS" — but misses common synonyms like "shell", "command line", or "CLI", so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Bash/Linux terminal niche is mostly distinct with clear topical triggers, but "working on macOS or Linux systems" would fire for nearly any task on those platforms, creating minor overlap risk with other skills.	4 / 5
	Total	15 / 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: sickn33/agentic-awesome-skills
Path: skills/bash-linux/SKILL.md
Commit: 7b534bc

Reviewed: 5 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.