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
Quality
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 placeholder with no substantive content. It fails on all dimensions by providing only a title and category label without describing any capabilities, use cases, or natural trigger terms. The repeated trigger term suggests auto-generated content that was not properly customized.
Suggestions
Add specific actions the skill performs (e.g., 'Explains Linux command syntax, provides examples of common commands like grep, awk, sed, find, and troubleshoots shell scripts').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about terminal commands, bash scripting, shell syntax, or needs help with specific Linux utilities').
Remove the redundant trigger term and replace with varied, natural keywords users would actually type (e.g., 'command line', 'terminal', 'bash', 'shell', specific command names).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Linux Commands Guide' is a title, not a description of capabilities. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's a guide and mentions a category, with no explicit trigger guidance or capability explanation. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'linux commands guide' repeated twice, which is not how users naturally speak. Missing natural terms like 'bash', 'terminal', 'shell', 'command line', specific commands, etc. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Linux Commands Guide' could overlap with any skill involving Linux, shell scripting, system administration, or DevOps. No clear niche or distinct triggers are established. | 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 content is entirely meta-description with no actual instructional value. It describes what a Linux commands guide would do without providing any actual Linux commands, examples, or guidance. The content is a template placeholder that fails to teach Claude anything actionable about Linux commands.
Suggestions
Replace the abstract capability descriptions with actual Linux command examples (e.g., file operations, process management, networking commands) with executable syntax
Add concrete code blocks showing common command patterns like `ls -la`, `grep -r 'pattern' /path`, `chmod 755 file.sh` with brief explanations of flags
Structure content into logical sections (file management, process control, networking, permissions) with quick-reference examples in each
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actionable command references and usage patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no actual Linux commands, no code examples, no specific instructions. The entire content describes what the skill does rather than providing executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, and no validation checkpoints. The content only lists abstract capabilities without any process guidance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual content. There are no references to detailed materials, examples, or command references. | 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
994edc4
- 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.