bash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
57
66%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bash-linux/SKILL.mdQuality
Discovery
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 establishes a clear domain (Bash/Linux terminal) and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are broad categories rather than specific actions, and the trigger condition ('working on macOS or Linux systems') is overly broad—nearly any development task could match. The description would benefit from more specific actions and narrower trigger conditions.
Suggestions
Replace broad categories with specific concrete actions, e.g., 'Write and debug shell scripts, chain commands with pipes, parse command output, handle exit codes and error streams, manage file permissions'.
Add more natural trigger terms users would say: 'shell', 'command line', 'CLI', 'zsh', '.sh files', 'bash script', 'terminal commands'.
Narrow the 'Use when' clause to avoid over-triggering, e.g., 'Use when the user asks about shell scripting, terminal commands, bash syntax, piping, or command-line utilities' rather than the overly broad 'working on macOS or Linux systems'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bash/Linux terminal) and mentions some action categories ('piping, error handling, scripting, critical commands'), but these are broad categories rather than specific concrete actions like 'write shell scripts, chain commands with pipes, handle exit codes'. | 2 / 3 |
Completeness | Answers both 'what' (Bash/Linux terminal patterns, critical commands, piping, error handling, scripting) and 'when' explicitly ('Use when working on macOS or Linux systems'), though the 'when' clause is somewhat broad. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Bash', 'Linux', 'terminal', 'piping', 'scripting', and 'macOS', but misses common user terms like 'shell', 'command line', 'CLI', 'sh', 'zsh', '.sh files', or 'bash script'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'Bash/Linux terminal' is a recognizable niche, the broad scope ('critical commands, piping, error handling, scripting') and the wide trigger ('working on macOS or Linux systems') could overlap with many development-related skills since most coding tasks on these systems involve the terminal. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill with excellent actionability—nearly every item is a concrete, executable command or snippet. Its main weaknesses are moderate verbosity (PowerShell comparison, boilerplate sections, some obvious content) and the lack of workflow-oriented guidance with validation steps for potentially destructive operations. The flat structure works reasonably well for a cheat sheet but could be tighter.
Suggestions
Remove the PowerShell comparison section (section 9) and the trailing boilerplate ('When to Use', 'Limitations') to improve conciseness—Claude can infer cross-platform differences.
Add a brief validation/verification pattern for destructive operations (e.g., 'before kill -9, confirm the PID with ps aux | grep; before rm -rf, echo the glob first') to improve workflow safety.
Consider splitting the script template and common patterns into a separate PATTERNS.md reference file to improve progressive disclosure for this longer document.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables, but includes some unnecessary sections like the PowerShell comparison (section 9) and the trailing boilerplate ('When to Use', 'Limitations') that add little value. The 'Remember' callout at the end restates obvious points. Some table entries cover things Claude already knows well. | 2 / 3 |
Actionability | Nearly every entry provides concrete, copy-paste ready commands and code snippets. The script template is fully executable, the common patterns section has complete working examples, and the tables provide specific command syntax rather than vague descriptions. | 3 / 3 |
Workflow Clarity | This is primarily a reference/cheat-sheet skill rather than a multi-step workflow skill. The script template shows good practices (set -euo pipefail, trap cleanup), but there's no explicit workflow sequencing with validation checkpoints for operations like batch file processing or destructive commands (e.g., kill -9 is shown without any verification step). | 2 / 3 |
Progressive Disclosure | The content is well-organized with numbered sections and clear headers, making it easy to navigate. However, it's a fairly long monolithic document (~180 lines) that could benefit from splitting advanced topics (scripting patterns, text processing) into separate reference files. No bundle files exist to offload detail. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
45bad85
- Reviewed
Table of Contents
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.