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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill linux-commands-guideOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no functional content. It provides only a title and category membership without describing any capabilities, actions, or usage scenarios. The repeated trigger term and lack of natural keywords make it nearly useless for skill selection.
Suggestions
Add specific actions the skill performs (e.g., 'Explains Linux command syntax, provides examples for file operations, process management, and system administration tasks')
Include a 'Use when...' clause with natural trigger terms like 'bash', 'terminal', 'command line', 'shell', 'chmod', 'grep', 'ls', etc.
Differentiate from other potential DevOps skills by specifying the scope (beginner commands, specific distributions, particular use cases like file management vs networking)
| 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 part of a category, with no functional information or explicit usage triggers. | 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 command-line tools. No distinguishing features are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill content is essentially an empty template with no actual instructional value. It describes what a Linux commands guide skill would do without providing any actual Linux commands, examples, or guidance. The entire content is meta-description rather than actionable instruction.
Suggestions
Replace the abstract 'Capabilities' section with actual Linux command examples organized by category (file operations, process management, networking, etc.)
Add concrete, executable command examples with expected outputs (e.g., `ls -la` with sample output)
Include a quick reference section with the most commonly needed commands in copy-paste ready format
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual instructional content
| 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 actual process. | 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
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.