linux-commands-guide
Linux Commands Guide - Auto-activating skill for DevOps Basics. Triggers on: linux commands guide, linux commands guide Part of the DevOps Basics skill category.
33
0%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/linux-commands-guide/SKILL.mdQuality
Discovery
0%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 essentially a title and category label with no substantive content. It fails on all dimensions: it lists no concrete actions, provides no natural trigger terms, lacks both 'what' and 'when' guidance, and is too generic to be distinguishable from other DevOps or Linux-related skills.
Suggestions
Add specific concrete actions the skill covers, e.g., 'Explains common Linux commands for file management, process control, permissions, networking, and package management.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about bash commands, terminal usage, shell scripting, chmod, grep, awk, sed, file permissions, or Linux system administration.'
Remove the duplicate trigger term 'linux commands guide' and replace with varied natural phrases users would actually say, such as 'command line', 'terminal', 'bash', 'shell', 'Linux help'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It says 'Linux Commands Guide' but never specifies what it actually does—no mention of specific commands, tasks, or capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the title. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'linux commands guide' repeated twice. These are not natural phrases users would say; users would more likely say things like 'how do I list files', 'bash commands', 'terminal', 'shell scripting', 'chmod', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Linux Commands Guide' could overlap with any skill related to Linux, DevOps, shell scripting, system administration, or command-line tools. There are no distinct triggers to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of auto-generated boilerplate that describes what a Linux commands guide would do without providing any actual Linux commands, examples, explanations, or actionable guidance. It fails on every dimension of the rubric.
Suggestions
Replace the boilerplate with actual Linux command references organized by category (file management, process management, networking, etc.) with concrete executable examples.
Add specific, copy-paste-ready command examples with common flags and use cases, e.g., `find /var/log -name '*.log' -mtime +30 -delete`.
Include a workflow for common multi-step tasks (e.g., diagnosing disk space issues, debugging network connectivity) with validation checkpoints.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actionable content that teaches Linux commands directly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual Linux commands, examples, or useful information. Every token is wasted on boilerplate. | 1 / 3 |
Actionability | There is zero concrete guidance—no commands, no code, no examples, no specific instructions. The content only describes what it claims to do without actually doing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no sequences, validation checkpoints, or any operational content. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate headings. No references to external files, no organized content hierarchy, and no actual content to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.