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.

78

1.08x
Quality

73%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/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

76%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-structured, highly actionable bash command reference with copy-paste examples and a complete script template. It is weaker on workflow clarity because it offers reference snippets rather than any sequenced, validated workflow.

Suggestions

Add at least one end-to-end worked workflow with an explicit validate/verify checkpoint (e.g. write script -> shellcheck -> run with set -euo pipefail -> verify output) to lift workflow clarity.

Trim the PowerShell comparison section unless it serves a concrete cross-platform trigger, since Claude already knows these differences.

Move the larger reference tables (e.g. full network/text-processing catalogs) into a references/ file and link from SKILL.md to improve progressive disclosure at this length.

DimensionReasoningScore

Conciseness

The body uses compact reference tables and a tight script template with little padding, assuming Claude's competence; minor over-explanation (the PowerShell comparison and the trailing Remember line) could be trimmed.

4 / 5

Actionability

Commands are exact and copy-paste ready throughout (ls -la, kill -9 $(lsof -t -i :3000), grep -r ...), and the script template is complete and executable, covering common cases.

5 / 5

Workflow Clarity

This is a reference/cheat-sheet rather than a sequenced multi-step workflow, so no validation checkpoints or feedback loops are presented; the organization is clear but no explicit workflow sequence exists.

3 / 5

Progressive Disclosure

Content is well-organized into ten numbered sections with clear headers in a single file with no nested references; at over 50 lines it is not eligible for the simple-skill 5, so good structure with minor organization gaps fits.

4 / 5

Total

16

/

20

Passed

Description

71%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, third-person, and includes an explicit Use-when trigger with several concrete capability categories. Its main weakness is the overly broad when-clause, which raises conflict risk with general dev skills.

Suggestions

Tighten the when-clause to concrete triggers, e.g. "Use when writing bash scripts, chaining shell commands, or debugging Linux/macOS terminal tasks" rather than all macOS/Linux work.

Add natural synonyms users say ("shell", "command line", "CLI") to broaden trigger-term coverage.

Consider naming a distinct niche (e.g. scripting vs. ad-hoc commands) to reduce overlap with general coding skills.

DimensionReasoningScore

Specificity

Lists several concrete action categories ("Critical commands, piping, error handling, scripting") naming the domain with specific capabilities, matching the anchor for several specific actions with minor gaps.

4 / 5

Completeness

Both a clear "what" (Bash/Linux terminal patterns and the listed capabilities) and an explicit "when" ("Use when working on macOS or Linux systems") are present, but the when-clause is broad rather than tightly scoped to concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural terms users would say are present ("Bash/Linux", "terminal", "macOS or Linux systems"), but common synonyms like "shell", "command line", or "CLI" are missing, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The skill name and domain ("Bash/Linux terminal patterns") are somewhat specific, but the "Use when working on macOS or Linux systems" trigger is broad enough to overlap with many general development skills.

3 / 5

Total

15

/

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.

Validation15 / 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
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.