bash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
73
66%
Does it follow best practices?
Impact
78%
1.08xAverage score across 3 eval scenarios
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 covers the basics with a clear 'Use when' clause and identifies the domain, but it lacks specific concrete actions and uses broad category terms rather than detailed capabilities. The trigger scope ('working on macOS or Linux systems') is overly wide and could cause conflicts with many other skills that also operate in those environments.
Suggestions
Narrow the 'Use when' clause to more specific triggers, e.g., 'Use when writing bash scripts, chaining shell commands, debugging terminal errors, or working with shell syntax'.
Add more natural trigger terms users would say, such as 'shell', 'command line', 'CLI', 'zsh', '.sh files', 'terminal commands'.
Replace broad category words like 'critical commands' with specific actions, e.g., 'write shell scripts, chain commands with pipes, parse command output, handle exit codes and signals'.
| 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, commands, piping, error handling, scripting) and 'when' ('Use when working on macOS or Linux systems') with an explicit trigger clause. | 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 | The scope is fairly broad — 'working on macOS or Linux systems' could overlap with many other skills (e.g., a Python scripting skill, a system administration skill, or a deployment skill). The trigger is too wide to clearly carve out a distinct niche. | 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 bash reference/cheat-sheet with good structure and fully executable examples. Its main weaknesses are including content Claude already knows (basic commands, PowerShell comparisons) and lacking validation/safety guidance for destructive operations like `kill -9` and `sed -i`. The table-based format is efficient but the breadth of coverage dilutes the 'essential patterns' focus.
Suggestions
Remove or significantly trim sections covering commands Claude already knows well (basic file operations, basic process management) to improve conciseness.
Add safety warnings or validation steps for destructive operations like `sed -i` (suggest backup first) and `kill -9` (suggest trying `kill` without -9 first).
Consider removing the PowerShell comparison section as it's tangential to the skill's stated purpose of Bash/Linux patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with table-based formatting, but includes some content Claude already knows well (basic bash commands like ls, cat, grep). The PowerShell comparison section and the final 'Remember' note add marginal value. Some tables could be trimmed. | 2 / 3 |
Actionability | All examples are concrete, executable commands and code snippets. The script template is copy-paste ready, common patterns include complete working code blocks, and every table entry has a real command. | 3 / 3 |
Workflow Clarity | This is a reference/cheat-sheet skill rather than a multi-step workflow, so sequencing is less critical. However, the script template and error handling sections show good patterns. The content lacks any validation checkpoints or feedback loops for potentially destructive operations (e.g., kill -9, sed -i replacements). | 2 / 3 |
Progressive Disclosure | Content is well-organized with numbered sections and tables, but it's a monolithic file with no references to external resources for deeper topics. Some sections (like the full script template or network commands) could be split out, though the overall length is manageable. | 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
43280f9
- 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.