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.

Install with Tessl CLI

npx tessl i github:lchenrique/politron-ide --skill bash-linux
What are skills?

83

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Discovery

67%

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 provides adequate coverage with a clear 'Use when' clause and identifies the domain well. However, it relies on category terms (piping, error handling) rather than concrete actions, and the trigger terms could be expanded to include common synonyms like 'shell', 'CLI', or 'command line' that users naturally use.

Suggestions

Replace category terms with specific concrete actions, e.g., 'Write shell scripts, parse log files, chain commands with pipes, handle exit codes'

Expand trigger terms to include common synonyms: 'shell', 'CLI', 'command line', 'zsh', 'sh', 'terminal commands'

DimensionReasoningScore

Specificity

Names the domain (Bash/Linux terminal) and mentions some actions (commands, piping, error handling, scripting), but these are categories rather than concrete specific actions like 'parse log files' or 'write shell scripts'.

2 / 3

Completeness

Clearly answers both what (Bash/Linux terminal patterns, 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 relevant terms like 'Bash', 'Linux', 'terminal', 'macOS' that users might say, but misses common variations like 'shell', 'command line', 'CLI', 'sh', 'zsh', or specific command names.

2 / 3

Distinctiveness Conflict Risk

Reasonably specific to shell/terminal work, but could overlap with skills for scripting languages, DevOps, or system administration. The 'macOS or Linux' trigger helps but is still broad.

2 / 3

Total

9

/

12

Passed

Implementation

87%

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

This is a high-quality reference skill that efficiently covers essential Bash patterns. It excels at conciseness through table-based formatting and provides fully actionable, executable examples. The only minor weakness is the lack of explicit validation steps for potentially destructive commands, though the error handling section partially addresses safety concerns.

DimensionReasoningScore

Conciseness

Extremely lean and efficient. Uses tables for quick reference, minimal prose, no explanations of concepts Claude already knows. Every section delivers actionable content without padding.

3 / 3

Actionability

Fully executable commands and code throughout. The script template is copy-paste ready, all examples are concrete with real syntax, and common patterns include complete, working code snippets.

3 / 3

Workflow Clarity

This is primarily a reference skill rather than a multi-step workflow skill. The script template includes set -euo pipefail for safety, and error handling section covers traps, but there's no explicit validation/verification workflow for potentially destructive operations like kill -9 or sed -i.

2 / 3

Progressive Disclosure

Well-organized with clear numbered sections and tables. For a reference-style skill under reasonable length, the structure is excellent with logical groupings. No external file references needed for this scope.

3 / 3

Total

11

/

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

allowed_tools_field

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

Warning

Total

10

/

11

Passed

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.