npm-scripts-optimizer
Npm Scripts Optimizer - Auto-activating skill for DevOps Basics. Triggers on: npm scripts optimizer, npm scripts optimizer Part of the DevOps Basics skill category.
32
0%
Does it follow best practices?
Impact
88%
0.94xAverage 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/npm-scripts-optimizer/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 that restates the skill name without providing any meaningful information about capabilities, actions, or usage triggers. It fails on all dimensions: no concrete actions are listed, trigger terms are a single repeated phrase, there is no 'when to use' guidance, and it is indistinguishable from other DevOps or npm-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes package.json scripts for redundancy, consolidates build commands, adds parallel execution, and simplifies complex script chains.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to clean up, optimize, or refactor npm scripts in package.json, or mentions slow build scripts, redundant npm commands, or script organization.'
Remove the duplicate trigger term and replace with varied natural keywords users might say, such as 'package.json', 'npm run scripts', 'build optimization', 'script refactoring', 'npm commands'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('npm scripts optimizer') but provides no concrete actions. There is no indication of what the skill actually does—no verbs like 'optimize', 'refactor', 'analyze', or 'consolidate' are present. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just a duplicate of the skill name, not meaningful trigger criteria. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'npm scripts optimizer' repeated twice. This is a narrow, unnatural phrase that users are unlikely to say verbatim. Common variations like 'package.json scripts', 'npm run', 'script optimization', or 'build scripts' are entirely missing. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's unclear what distinguishes this from any other npm-related or DevOps skill. The phrase 'DevOps Basics' is generic and the lack of specific capabilities makes overlap with other skills highly likely. | 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 template with no actual content about npm scripts optimization. It contains only boilerplate section headers and generic descriptions that repeat the skill name without providing any actionable guidance, code examples, or concrete instructions. It fails on every dimension because it teaches Claude nothing it doesn't already know and provides zero executable value.
Suggestions
Add concrete, executable examples of npm script optimizations (e.g., using `npm-run-all` for parallel execution, leveraging `pre`/`post` hooks, replacing shell scripts with cross-platform alternatives)
Include before/after examples showing a bloated package.json scripts section transformed into an optimized one with specific techniques
Provide a clear workflow: 1. Audit existing scripts, 2. Identify redundancies, 3. Apply specific optimization patterns, 4. Validate with `npm run` dry runs
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching the actual skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'npm scripts optimizer' excessively, and provides zero actual technical content about optimizing npm scripts. | 1 / 3 |
Actionability | There are no concrete commands, code examples, or executable guidance whatsoever. The skill describes what it could do ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content contains no sequence of actions, no validation checkpoints, and no actual instructions for optimizing npm scripts. | 1 / 3 |
Progressive Disclosure | While there are section headers, they contain only generic placeholder text. There are no references to detailed materials, no examples, and no meaningful content organization—just a template with no substance. | 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.