CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bash-linux

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

70

1.08x
Quality

68%

Does it follow best practices?

Impact

78%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bash-linux/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

56%Weight 40%Scale 1-5

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

The body is a well-organized, actionable command cheat sheet, but it overwhelmingly restates basic Bash knowledge Claude already has, offers little non-obvious value (no gotchas like macOS sed -i differences or kill -9 caveats), and is a monolithic single file with a meaningless circular 'When to Use' section.

Suggestions

Cut the tables of commands Claude already knows and keep only the non-obvious material: platform differences (e.g., sed -i requires an argument on macOS), kill -9 caveats, quoting pitfalls, and trap/set behavior.

Replace the circular 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') with concrete guidance on when each pattern applies.

Split the reference into a lean SKILL.md overview plus a references/ file (e.g., command tables) to reduce inline bulk and support progressive disclosure.

DimensionReasoningScore

Conciseness

Although formatted as terse tables, nearly the entire body documents commands and concepts Claude already knows (ls, head, tail, ps aux, grep, sed, awk, env, curl, set -euo pipefail), so most of the ~200 lines add no new knowledge — noticeably below the mostly-efficient anchor, though not 'heavily padded' prose.

2 / 5

Actionability

Commands are concrete and mostly copy-paste ready ('find . -name "*.js" -type f', 'kill -9 $(lsof -t -i :3000)', a complete script template), with only minor placeholders (URL, <PID>) leaving small gaps.

4 / 5

Workflow Clarity

As a single-purpose command reference with well-organized numbered sections, organization is unambiguous, but there is no validation guidance around destructive commands (kill -9, sed -i, rm) and the trailing 'When to Use' section is circular filler ('applicable to execute the workflow or actions described in the overview') that provides no sequencing value.

4 / 5

Progressive Disclosure

No bundle files exist and no external references are signaled; all ~200 lines are inlined monolithically in SKILL.md, beyond the under-50-line simple-skill exception. Section structure is present, but content that could be split out (e.g., the PowerShell comparison) is inlined.

3 / 5

Total

13

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 is concise, uses third person, and includes an explicit 'Use when...' clause with good natural keywords, but it lists topic areas rather than concrete capabilities and its trigger ('working on macOS or Linux systems') is over-broad, creating conflict risk.

Suggestions

Narrow the trigger clause to concrete situations, e.g. 'Use when writing shell scripts, chaining terminal commands, or handling errors in Bash' instead of any work on macOS/Linux.

State capabilities as actions (e.g. 'Chain commands safely, manage processes, process text streams, write error-resilient scripts') rather than topic labels like 'Critical commands, piping'.

Add common synonyms such as 'shell', 'shell scripting', and 'command line' to the trigger terms to improve natural-language matching.

DimensionReasoningScore

Specificity

Names the domain ('Bash/Linux terminal patterns') and lists several topic areas ('Critical commands, piping, error handling, scripting'), but these are topic labels rather than concrete actions, matching the anchor for naming a domain with limited concrete actions rather than the anchor requiring several specific actions.

3 / 5

Completeness

Both 'what' (terminal patterns, commands, piping, error handling, scripting) and an explicit 'when' ('Use when working on macOS or Linux systems') are present, but the 'when' is broad and could be more concrete about the triggering tasks, matching the anchor-4 example structure.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('Bash', 'Linux', 'terminal', 'commands', 'piping', 'error handling', 'scripting', 'macOS') that users would actually say, but misses common variations like 'shell', 'shell script', and 'command line'.

4 / 5

Distinctiveness Conflict Risk

The 'what' carves a clear Bash/Linux niche, but 'Use when working on macOS or Linux systems' is broad enough to fire for virtually any work on those platforms, creating real overlap risk with many other skills.

3 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/bash-linux/SKILL.md

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.