bash-linux

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

Quality

67%

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

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 skill is a dense, highly actionable Bash command reference with concrete executable examples throughout. It is weaker on conciseness (restating well-known commands), workflow structure (no sequenced process with validation), and progressive disclosure (single monolithic file).

Suggestions

Trim or move content Claude already knows; keep only non-obvious patterns, gotchas, and project-specific conventions to earn more token budget.

Add a short multi-step workflow example with explicit validation checkpoints (e.g., script -> shellcheck -> run -> verify) for cases involving destructive or batch operations.

Split the large reference tables (operators, file operations, text processing, PowerShell comparison) into separate reference files and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is well-formatted as terse tables and code, but it largely restates standard Bash commands and concepts Claude already knows, so it is mostly efficient without adding much unique knowledge.	3 / 5
Actionability	Concrete, copy-paste-ready commands fill every table, and the script template and common-pattern blocks are fully executable, covering the common cases comprehensively.	5 / 5
Workflow Clarity	This is a reference cheat sheet rather than a multi-step workflow, so sections are organized but lack an explicit sequence with validation checkpoints; safety patterns like `set -e` and traps exist but are not woven into a workflow.	3 / 5
Progressive Disclosure	Content is organized into numbered sections, but everything is inlined in a single ~200-line file with no external references or deeper-material pointers, and several large reference tables could live in separate files.	3 / 5
	Total	14 / 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 and covers both what the skill does and when to use it, with natural trigger terms. Its main weakness is that the listed capabilities are abstract categories rather than concrete actions.

Suggestions

Replace abstract categories ("Critical commands, piping, error handling, scripting") with concrete actions, e.g. "Chain commands with && and ||, pipe output between processes, handle errors with set -e and traps, write shell scripts."

Broaden trigger terms to include natural synonyms users say, such as "shell", "command line", or "CLI".

Make the 'when' clause more specific, e.g. "Use when writing or debugging Bash scripts, chaining shell commands, or working on macOS/Linux terminals."

Dimension	Reasoning	Score
Specificity	Names the domain ("Bash/Linux terminal patterns") and several capability categories ("Critical commands, piping, error handling, scripting"), but these are abstract areas rather than concrete actions, matching the anchor that names the domain with non-comprehensive specifics.	3 / 5
Completeness	Both 'what' (terminal patterns, commands, piping, error handling, scripting) and 'when' ("Use when working on macOS or Linux systems") are present, but the 'when' clause is generic and could be more specific.	4 / 5
Trigger Term Quality	"Bash", "Linux", "terminal", "macOS" are natural terms users say, and "Use when working on macOS or Linux systems" is an explicit trigger; a few common synonyms (shell, command line, CLI) are missing.	4 / 5
Distinctiveness Conflict Risk	Bash/Linux terminal is a clear niche with distinct triggers and minimal conflict risk, though minor overlap is possible with a generic shell or command-line skill.	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/antigravity-awesome-skills
Path: skills/bash-linux/SKILL.md
Commit: 1f67c44

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