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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill npm-scripts-optimizerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped and essentially just restates the skill name without providing any useful information. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. Claude would have no basis to distinguish when to use this skill versus other DevOps or npm-related skills.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes and optimizes npm scripts in package.json, identifies redundant dependencies, parallelizes build tasks, and reduces script execution time.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user mentions slow npm scripts, package.json optimization, build performance, or wants to improve npm run commands.'
Remove the duplicate trigger term and add variations users would naturally say: 'npm run slow', 'package.json scripts', 'optimize build scripts', 'npm performance'.
| 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 the 'when' clause is just the skill name repeated. There is no explicit guidance on when Claude should select this skill or what problems it solves. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('npm scripts optimizer, npm scripts optimizer'). This is redundant and misses natural variations users would say like 'optimize package.json', 'speed up npm', 'npm run scripts', or 'package scripts'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'npm scripts' provides some specificity to the Node.js/npm ecosystem, but 'optimizer' is vague and could overlap with performance optimization, build optimization, or other npm-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what an npm scripts optimizer skill would do without providing any actual guidance, code examples, or specific techniques for optimizing npm scripts. The entire content could be replaced with concrete examples of script optimization patterns.
Suggestions
Add concrete npm script optimization examples (e.g., parallelizing scripts with `npm-run-all`, using `pre` and `post` hooks efficiently, caching strategies)
Include executable code showing before/after script configurations in package.json
Provide specific commands and tools (e.g., `npm-run-all --parallel`, `concurrently`, script naming conventions)
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual optimization techniques
| 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 mentions 'step-by-step guidance' but provides none. There are no sequences, validation steps, or any actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed materials, no clear sections with actionable content, just marketing-style descriptions. | 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.