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 just a title with auto-generated boilerplate metadata. It provides no concrete actions, no natural trigger terms, no 'Use when' guidance, and no distinguishing characteristics. It would be nearly impossible for Claude to correctly select this skill from a pool of similar skills.
Suggestions
Add specific concrete actions the skill covers, e.g., 'Explains common Linux commands for file management, process control, networking, and permissions (ls, grep, chmod, ps, etc.)'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Linux terminal commands, bash scripting, shell syntax, file permissions, or command-line utilities.'
Remove the duplicate trigger term 'linux commands guide' and replace with varied natural keywords users would actually say, such as 'bash', 'terminal', 'shell', 'command line', 'CLI', 'Ubuntu commands'.
| 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 terms users would say; users would more likely say things like 'bash', 'terminal', 'shell commands', 'chmod', 'grep', 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 actual content. It contains only generic boilerplate describing what a Linux commands guide skill would do, without providing any actual Linux commands, examples, workflows, or actionable guidance. It fails on every dimension because there is literally no instructional content present.
Suggestions
Add actual Linux command examples organized by category (file management, process management, networking, etc.) with concrete, executable commands and expected outputs.
Include a workflow for common multi-step tasks (e.g., diagnosing a service issue: check status → read logs → restart → verify) with explicit validation checkpoints.
Replace all boilerplate meta-descriptions ('Provides step-by-step guidance', 'Follows industry best practices') with the actual guidance and practices themselves.
If the topic is broad, create a concise overview in SKILL.md with references to separate files for subtopics (e.g., FILE_MANAGEMENT.md, NETWORKING.md, PROCESS_MANAGEMENT.md).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no actual Linux commands, and pads the file with generic meta-descriptions ('Provides step-by-step guidance', 'Follows industry best practices') that add zero value. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no commands, no code, no examples, no specific instructions. The entire content describes what the skill supposedly does 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 references to external files, no structured navigation, and no content organization beyond generic boilerplate headings. There are no bundle files to support the skill, and the body itself contains no substantive content to organize. | 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
13d35b8
- 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.