bash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill bash-linuxOverall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description has a solid structure with an explicit 'Use when' clause, which is good for completeness. However, it relies on category-level terms rather than specific concrete actions, and the trigger scope is quite broad ('macOS or Linux systems' covers nearly any non-Windows task). The description would benefit from more specific action verbs and narrower trigger conditions.
Suggestions
Add more specific concrete actions like 'write shell scripts, chain commands with pipes, parse text with grep/sed/awk, handle exit codes'
Include additional natural trigger terms users would say: 'shell', 'command line', 'CLI', 'zsh', 'terminal commands'
Narrow the 'Use when' clause to be more specific, e.g., 'Use when writing shell scripts, chaining terminal commands, or troubleshooting command-line errors'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bash/Linux terminal) and mentions some actions (commands, piping, error handling, scripting), but these are categories rather than concrete specific actions like 'parse log files' or 'chain grep and awk commands'. | 2 / 3 |
Completeness | Clearly 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 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Bash', 'Linux', 'terminal', 'macOS' that users might say, but misses common variations like 'shell', 'command line', 'CLI', 'zsh', or specific command names users might reference. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to shell/terminal work, but could overlap with skills for specific tools (git, docker), system administration, or general scripting skills. The broad 'macOS or Linux systems' trigger could fire for many unrelated tasks. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
88%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality reference skill that efficiently covers essential Bash patterns. It excels at conciseness through effective use of tables and avoids explaining concepts Claude already knows. The main weakness is the lack of validation guidance for potentially destructive operations (kill, sed -i), though this is minor for a reference document.
Suggestions
Consider adding a brief note about testing sed commands without -i flag first (e.g., `sed 's/old/new/g' file.txt` to preview before `sed -i`)
For the 'Kill port' command, consider noting to verify the PID before killing with `lsof -i :3000` first
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, minimal prose, no explanations of concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Fully executable commands and code throughout. The script template is copy-paste ready, all examples are concrete with real syntax, and common patterns include complete, working code snippets. | 3 / 3 |
Workflow Clarity | This is primarily a reference skill rather than a multi-step workflow, but the script template section provides good structure. However, there's no explicit validation workflow for potentially destructive operations like `kill -9` or `sed -i` replacements. | 2 / 3 |
Progressive Disclosure | Well-organized with clear numbered sections and tables for quick scanning. For a reference-style skill under reasonable length, the structure is appropriate with logical groupings and no need for external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.