CtrlK
BlogDocsLog inGet started
Tessl Logo

bash-linux

Bash/Linux terminal patterns and critical commands.

27

Quality

18%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/bash-linux/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

This skill is essentially an empty table of contents with links to sub-skills but no substantive content of its own. It provides no actionable guidance, no code examples, no workflow, and an orphaned empty section header. Without the bundle files to verify the sub-skills exist and contain quality content, the SKILL.md alone fails to teach Claude anything useful about Bash/Linux patterns.

Suggestions

Add at least a brief quick-reference section with the most essential Bash patterns inline (e.g., common operators, pipe syntax, variable expansion) so the skill is useful even without loading sub-skills.

Remove the empty '## 1. Operator Syntax' heading or populate it with actual content.

Add 1-sentence descriptions next to each sub-skill link so Claude can determine which to consult without loading all of them (e.g., 'Chaining Commands — `&&`, `||`, `;`, pipes, and subshells').

Include at least one concrete, executable code example in the main SKILL.md to make it minimally actionable on its own.

DimensionReasoningScore

Conciseness

The content is very short, which is good for token efficiency, but the '## 1. Operator Syntax' heading is empty with no content, and the '🧠 Knowledge Modules (Fractal Skills)' framing adds unnecessary decoration. The actual content is just a list of links.

2 / 3

Actionability

The SKILL.md body contains zero actionable content—no commands, no code, no concrete guidance. It is entirely a table of contents pointing to sub-skills, with no inline examples or executable instructions whatsoever.

1 / 3

Workflow Clarity

There is no workflow, no sequencing, and no validation steps. The file is purely a list of links with no indication of how or when to use each sub-skill, nor any process for combining them.

1 / 3

Progressive Disclosure

The file does attempt progressive disclosure by linking to sub-skills, and references are one level deep with clear file paths. However, there are no descriptions of what each sub-skill covers, no bundle files were provided to verify the references exist, and the empty 'Operator Syntax' section suggests incomplete organization.

2 / 3

Total

6

/

12

Passed

Description

14%

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 vague and generic to be effective for skill selection. It fails to specify concrete actions, lacks a 'Use when...' clause, and is broad enough to conflict with many other potential skills. It reads more like a topic label than a functional skill description.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about shell scripting, terminal commands, bash syntax, or Linux command-line operations.'

List specific concrete actions the skill covers, e.g., 'Write bash scripts, debug shell commands, explain Linux utilities, construct pipelines and redirections, manage file permissions.'

Include additional natural trigger terms like 'shell', 'CLI', 'command line', 'scripting', '.sh files' to improve keyword coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description uses vague language like 'patterns and critical commands' without listing any concrete actions. It does not specify what the skill actually does (e.g., execute commands, write scripts, debug errors).

1 / 3

Completeness

The description weakly addresses 'what' (patterns and commands) and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

'Bash', 'Linux', and 'terminal' are relevant keywords users might naturally use, but the description misses common variations like 'shell', 'command line', 'CLI', 'scripting', or 'sh'.

2 / 3

Distinctiveness Conflict Risk

The description is extremely broad — 'bash/Linux terminal patterns and critical commands' could overlap with virtually any skill involving shell scripting, DevOps, system administration, or general coding assistance.

1 / 3

Total

5

/

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.

Validation10 / 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
Dokhacgiakhoa/antigravity-ide
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.