CtrlK
BlogDocsLog inGet started
Tessl Logo

bash-linux

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

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-devops-cloud/skills/bash-linux/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Scale 1-3

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 skill with excellent actionability—nearly every item is a concrete, executable command or snippet. The table-based format is efficient for quick lookup. Main weaknesses are some unnecessary content (PowerShell comparison, boilerplate limitations section, obvious reminders) and the monolithic structure that could benefit from splitting advanced topics into separate files.

Suggestions

Remove or significantly trim the PowerShell comparison section (section 9) as it's tangential to the skill's purpose and consumes tokens

Remove the boilerplate 'When to Use' and 'Limitations' sections at the end, as well as the 'Remember' callout, which state obvious information

DimensionReasoningScore

Conciseness

The content is mostly efficient with good use of tables, but includes some unnecessary sections like the PowerShell comparison (section 9) which adds bulk without clear necessity, and the trailing 'When to Use' and 'Limitations' sections are boilerplate filler. The 'Remember' callout at the end restates obvious Bash knowledge.

2 / 3

Actionability

Nearly every entry provides concrete, copy-paste-ready commands and code snippets. The script template is fully executable with set -euo pipefail, the common patterns section has complete working examples, and the tables map tasks directly to specific commands.

3 / 3

Workflow Clarity

For a reference/cheat-sheet style skill covering single-task patterns, the content is well-organized with clear sections. The script template demonstrates proper error handling with set -euo pipefail and trap cleanup, and the error handling section explicitly covers validation patterns. No multi-step destructive workflows require feedback loops here.

3 / 3

Progressive Disclosure

The content is well-structured with numbered sections and tables, but it's a monolithic file with no references to external files for deeper topics. Some sections (like the full script template or the PowerShell comparison) could be split out. However, for a standalone skill with no bundle files, the organization is reasonable though slightly long.

2 / 3

Total

10

/

12

Passed

Description

67%Scale 1-3

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 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, the trigger terms miss common user vocabulary variations, and the 'when' clause is overly broad ('working on macOS or Linux systems'), which could cause conflicts with many other skills.

Suggestions

Add more specific concrete actions, e.g., 'Write shell scripts, chain commands with pipes, parse output with grep/awk/sed, handle exit codes and signals'.

Expand trigger terms to include common variations like 'shell', 'command line', 'CLI', 'zsh', '.sh files', 'bash script'.

Narrow the 'Use when' clause to reduce conflict risk, e.g., 'Use when the user asks about shell scripting, terminal commands, piping, or Bash syntax' rather than the overly broad 'working on macOS or Linux systems'.

DimensionReasoningScore

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 including 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 distinguish this from other terminal-adjacent skills.

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.