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.
36
Quality
7%
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
7%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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It provides no concrete actions, no meaningful trigger terms (just duplicates the skill name), and no guidance on when Claude should select this skill. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes package.json scripts for redundancy, parallelizes independent tasks, reduces build times, and consolidates script commands.'
Replace the duplicate trigger term with natural user phrases like 'optimize npm scripts', 'speed up npm run', 'package.json scripts', 'npm build performance', 'script consolidation'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to improve npm script performance, reduce build times, or clean up package.json scripts.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Npm Scripts Optimizer') without describing any concrete actions. There are no verbs or specific capabilities listed - no indication of what optimization means or what actions it performs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('npm scripts optimizer, npm scripts optimizer'). No natural user language like 'optimize package.json', 'speed up npm', 'script performance', or 'npm run' variations are included. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'npm scripts' provides some specificity to the Node.js/npm ecosystem, but 'optimizer' is vague and could overlap with performance, build, or general DevOps skills. The lack of specific actions makes it unclear what distinguishes this from other npm-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no substantive content about npm scripts optimization. It describes capabilities in abstract marketing language but provides zero actionable guidance, code examples, or specific techniques. The skill would be completely useless for actually helping with npm scripts optimization tasks.
Suggestions
Add concrete npm script examples showing before/after optimization (e.g., parallelizing scripts with npm-run-all, using pre/post hooks efficiently)
Include specific commands and package.json configurations that can be copy-pasted
Define a clear workflow: analyze current scripts -> identify optimization opportunities -> implement changes -> validate improvements
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about npm scripts optimization. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually optimize npm scripts - no examples, no commands, no configurations. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there's no actual content to disclose. References to related skills exist but no links to detailed documentation or examples are provided. | 2 / 3 |
Total | 5 / 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.