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.

66

Quality

81%

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

The canonical home for this skill is bash-linux in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, highly actionable bash reference that is token-efficient and well-organized as a self-contained single file. The main gap is the absence of validation/safety guidance around destructive commands, which limits workflow clarity.

Suggestions

Add brief safety caveats or validation steps for destructive commands such as `sed -i` (e.g., test without `-i` first or back up the file) and `kill -9` (prefer `kill` / verify the PID first).

Consider a short 'safe scripting' workflow with a feedback loop (run, check exit status, fix, re-run) to lift workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

The body is lean — tables and executable code with minimal prose, a one-line intro, and no explaining of concepts Claude already knows; every token earns its place, matching the 'lean and efficient' top anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands across all sections plus a complete `#!/bin/bash` script template with `set -euo pipefail`, satisfying the 'fully executable code/commands' top anchor.

3 / 3

Workflow Clarity

Content is well-organized into numbered sections and offers a script template, but there are no validation checkpoints or feedback loops, and destructive commands like `sed -i` and `kill -9` appear without safety caveats, capping it at 2 per the feedback-loops note.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is a self-contained single file with ten well-organized numbered sections and no nested references; per the simple-skill note, well-organized sections with no external-reference need score 3.

3 / 3

Total

11

/

12

Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, platform-scoped description that answers both what and when with an explicit Use-when clause. It is somewhat held back by category-level capability wording and missing common trigger synonyms like 'shell' or 'command line'.

Suggestions

Replace category-level wording ('Critical commands, piping, error handling, scripting') with concrete actions, e.g. 'Chain commands with pipes and operators, search and replace text, manage processes, write robust scripts with error handling'.

Add common natural trigger terms users say, such as 'shell', 'command line', 'CLI', or 'Unix'.

DimensionReasoningScore

Specificity

Names the domain ('Bash/Linux terminal patterns') and four capability areas ('Critical commands, piping, error handling, scripting'), but these are topical categories rather than concrete verb+object actions, so it falls short of the comprehensive-specific-actions anchor at 3.

2 / 3

Completeness

Explicitly answers both what ('Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting.') and when ('Use when working on macOS or Linux systems.') with an explicit Use-when clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Includes natural terms ('Bash/Linux terminal', 'macOS or Linux systems') but omits common variations users would say such as 'shell', 'command line', 'CLI', or 'Unix', matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Bash on macOS/Linux) with distinct platform-specific triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
vudovn/ag-kit
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.