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 is an extremely weak description that essentially only provides a skill name and category label. It lacks any concrete actions, meaningful trigger terms, or explicit guidance on when to use the skill. It would be nearly impossible for Claude to reliably select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes package.json scripts for redundancy, optimizes build pipelines, consolidates duplicate npm commands, and suggests parallel execution strategies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about optimizing npm scripts, improving package.json run commands, speeding up npm builds, or consolidating npm run tasks.'
Remove the duplicate trigger term ('npm scripts optimizer' is listed twice) and replace with varied natural keywords users would actually say, such as 'package.json scripts', 'npm run optimization', 'slow npm builds', 'script consolidation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Npm Scripts Optimizer') and mentions a category ('DevOps Basics') without describing what it actually does—no mention of optimizing, refactoring, analyzing, or any specific operations on npm scripts. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('npm scripts optimizer, npm scripts optimizer'). There are no natural user keywords like 'package.json', 'npm run', 'build scripts', 'script performance', or other terms a user would naturally use. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'DevOps Basics' is extremely broad, and without specific actions or triggers, it could easily conflict with any npm-related or DevOps-related skill. | 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 placeholder with no actionable content. It repeatedly names the topic ('npm scripts optimizer') without ever providing any concrete guidance, code examples, commands, or workflows. It fails on every dimension because it contains no real instructional content—only generic boilerplate that could apply to any topic.
Suggestions
Add concrete, executable examples of npm script optimization (e.g., using `npm-run-all` for parallel execution, lifecycle hooks, pre/post scripts, cross-env usage) with copy-paste ready package.json snippets.
Define a clear workflow: 1) Audit existing scripts, 2) Identify redundancies, 3) Apply specific optimization patterns, 4) Validate with `npm run` dry runs.
Remove all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') and replace with specific, actionable instructions that Claude doesn't already know.
Include a before/after example showing an unoptimized package.json scripts section transformed into an optimized one, with explanation of each change.
| 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 domain-specific information. Every section is padded with generic phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' without any substance. | 1 / 3 |
Actionability | There is no concrete, executable guidance whatsoever—no code, no commands, no specific examples, no configuration snippets. The skill describes what it could do in abstract terms but never actually instructs Claude on how to optimize npm scripts. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There is no sequence of actions, no validation checkpoints, and no error handling. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | There are no references to external files, no bundle files, and the content is a monolithic block of generic placeholder text with no meaningful structure or navigation to deeper resources. | 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.