bash-linux

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 with concrete executable commands and a complete script template, but it is a monolithic reference that re-lists many basic commands Claude already knows and lacks validation checkpoints around its destructive operations.

Suggestions

Trim basic commands Claude already knows (ls, cat, head, tail, grep basics) and retain the higher-value patterns (set -euo pipefail, trap cleanup, read-line-by-line, port-kill one-liners) to improve token efficiency.

Add a brief validation/safety note near destructive commands (kill -9, sed -i, rm -f) such as confirming the PID or backing up before sed -i, to introduce a feedback checkpoint.

Consider splitting the large reference tables into a separate reference file linked from a concise overview in SKILL.md to apply progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a lean, table-driven reference with no concept-explaining prose, but much of it catalogs basic commands Claude already knows (ls -la, cat, head, grep -r, ps aux, export VAR), so it could be tightened to focus on less-common patterns rather than reaching the every-token-earns-its-place anchor at 3.	2 / 3
Actionability	It provides concrete, executable, copy-paste-ready commands in every section plus a complete runnable script template with set -euo pipefail, log functions, and a main routine, matching the fully-executable anchor.	3 / 3
Workflow Clarity	This is a reference cheat-sheet rather than a sequenced workflow, and it presents destructive operations (kill -9, sed -i, rm -f in trap) without validation checkpoints or feedback loops, capping it at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Sections are clearly numbered and organized, but the ~200-line file is monolithic with all reference tables inline and no external bundle files or one-level-deep references, fitting the well-structured-but-content-should-be-separate anchor rather than the clear-overview-with-signaled-references anchor at 3.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 covers what and when with an explicit trigger and relevant domain keywords, but its trigger clause is overly broad and its action list is categorical rather than concrete, leaving it generic enough to risk overlap with other macOS/Linux skills.

Suggestions

Tighten the trigger to task-specific phrasing, e.g. 'Use when writing or debugging Bash shell scripts, piping commands, or performing terminal tasks on macOS/Linux.'

Replace categorical action terms ('Critical commands, piping, error handling, scripting') with concrete verbs users would request, e.g. 'Chain commands, pipe output, handle errors with set -e, and write shell scripts.'

Narrow the 'when' clause so it does not fire for non-terminal macOS/Linux work, reducing conflict with unrelated skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Bash/Linux terminal patterns') and lists action categories ('Critical commands, piping, error handling, scripting'), but these are categories rather than concrete actions like 'extract text', so it falls short of the multiple-specific-actions anchor at 3.	2 / 3
Completeness	It states what the skill does ('Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting.') and provides an explicit 'Use when working on macOS or Linux systems.' trigger, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural terms 'Bash', 'Linux', and 'macOS' appear, but the 'Use when working on macOS or Linux systems' trigger is broad and omits common task-specific variations users would say (e.g., 'shell scripting', 'terminal commands'), matching the some-relevant-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	The 'Bash/Linux terminal patterns' niche is somewhat distinct, but the 'Use when working on macOS or Linux systems' trigger is broad enough to overlap with many other skills that operate on those systems, fitting the somewhat-specific-but-could-overlap anchor rather than the clear-niche anchor at 3.	2 / 3
	Total	9 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 615669b

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