bash-linux
Bash/Linux terminal patterns and critical commands.
43
30%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/bash-linux/SKILL.mdQuality
Discovery
22%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 is too brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail to distinguish it from other command-line or scripting-related skills. The description would benefit significantly from listing specific capabilities and adding clear 'Use when...' guidance.
Suggestions
Add a 'Use when...' clause specifying triggers like 'shell scripts', 'command line', 'terminal commands', 'bash scripting', or 'Linux administration'
Replace 'patterns and critical commands' with specific concrete actions such as 'Write shell scripts, debug command pipelines, explain Linux commands, manage file permissions'
Include common user terms and file extensions like '.sh', 'CLI', 'shell', 'chmod', 'grep', 'awk' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('patterns and critical commands') without listing any concrete actions. It doesn't specify what actions Claude can perform, just mentions abstract concepts. | 1 / 3 |
Completeness | Only weakly addresses 'what' (patterns and commands) and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger guidance is provided. | 1 / 3 |
Trigger Term Quality | Contains 'Bash' and 'Linux terminal' which are relevant keywords users might say, but misses common variations like 'shell', 'command line', 'CLI', 'scripts', or specific command names. | 2 / 3 |
Distinctiveness Conflict Risk | While 'Bash/Linux terminal' provides some specificity, 'patterns and critical commands' is vague enough to potentially overlap with shell scripting, DevOps, or general coding skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill file is essentially an empty index page - it's concise but provides no standalone value. The main SKILL.md should contain at least a quick-start section with the most common patterns, with sub-skills reserved for detailed reference. Currently, a user must click through multiple files to get any actionable information.
Suggestions
Add a 'Quick Reference' section with the 3-5 most essential bash patterns (e.g., command chaining operators, basic file loops) directly in the main file
Provide brief one-line descriptions for each sub-skill link so readers know what they'll find without clicking through
Include at least one executable code example in the main skill file demonstrating a common pattern
Consider adding a 'When to use which sub-skill' guide or decision tree for navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean - just a brief description and organized links to sub-skills. No unnecessary explanation or padding. | 3 / 3 |
Actionability | The main skill file contains no concrete code, commands, or executable guidance - it's purely a table of contents with no actionable content itself. | 1 / 3 |
Workflow Clarity | No workflow is presented; the file is just a list of links with no sequencing, validation steps, or process guidance for how to use these patterns together. | 1 / 3 |
Progressive Disclosure | Good use of sub-skills for organization, but the main file provides no quick-start content or overview of what each sub-skill covers - it's just bare links without context or signaling. | 2 / 3 |
Total | 7 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.