bash-linux

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

1.08x

Quality

73%

Does it follow best practices?

Impact

78%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/bash-linux/SKILL.md

The canonical home for this skill is bash-linux in sickn33/agentic-awesome-skills

Quality

Content

76%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 a tight, actionable command reference with concrete executable examples and clean section organization. Its main weakness is workflow clarity: destructive and batch commands appear without validation checkpoints, and there is no multi-step workflow guidance.

Suggestions

Add a brief validation/check step next to destructive commands, e.g. confirm the PID before 'kill -9' or back up the file before 'sed -i', to lift workflow clarity above the destructive-ops cap.

Remove the redundancy between the script template's 'set -euo pipefail' comment and the standalone error-handling 'Set options' block, or cross-reference one from the other.

Consider whether the 'Differences from PowerShell' section earns its tokens for a Bash skill, or move it to a reference file to tighten the core body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference tables and executable code with minimal prose, assuming Claude's bash competence, but has minor redundancy (e.g. section 10's set options repeat the script template's 'set -euo pipefail' and the PowerShell-comparison section is tangential padding), fitting anchor 4 rather than 5.	4 / 5
Actionability	Commands are concrete and copy-paste ready across tables and code blocks (e.g. 'kill -9 $(lsof -t -i :3000)', the full script template, the trap-for-cleanup example), covering common cases with executable examples, matching anchor 5.	5 / 5
Workflow Clarity	This is a command catalog rather than a sequenced workflow, and it includes destructive/batch commands (kill -9, sed -i, rm) with no validation or verification guidance; per the destructive-operations cap this holds at anchor 3 even though the script template shows set -euo pipefail.	3 / 5
Progressive Disclosure	Content is well-organized into 10 clearly headed sections with no buried or nested references, and no bundle files exist; it is over 50 lines so the simple-skill 5 exception does not auto-apply, but the clean section structure fits anchor 4 over 3.	4 / 5
	Total	16 / 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 clearly identifies its niche and includes an explicit 'Use when' trigger with natural keywords, but the 'when' clause is broad and the action list is topic-level rather than concrete. It sits comfortably above midpoint but lacks the precision of the top anchors.

Suggestions

Replace topic categories with concrete actions, e.g. 'Chain commands, pipe output, handle errors, write shell scripts' instead of 'Critical commands, piping, error handling, scripting'.

Tighten the 'when' clause to the actual trigger, e.g. 'Use when running or writing Bash/shell commands on macOS or Linux' rather than the broad 'working on macOS or Linux systems'.

Add common synonyms ('shell', 'command line', 'CLI') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Bash/Linux terminal patterns') and several capability areas ('piping, error handling, scripting'), but these are abstract topic categories rather than concrete actions like 'extract text' or 'fill forms', matching anchor 3 more than 2 because multiple specific areas are enumerated.	3 / 5
Completeness	Has both a clear 'what' (terminal patterns, commands, piping, error handling, scripting) and an explicit 'Use when working on macOS or Linux systems' trigger, but the 'when' is broad and not tied specifically to terminal/shell tasks, matching anchor 4 not 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Bash', 'Linux', 'terminal', 'commands', 'macOS') with good coverage, but misses common synonyms like 'shell', 'command line', or 'CLI', fitting anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'Bash/Linux terminal patterns' framing is a fairly distinct niche with clear triggers, with only minor overlap risk against closely related shell or OS-administration skills, fitting anchor 4.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/bash-linux/SKILL.md
Commit: 57c135b

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