package-json-manager
Package Json Manager - Auto-activating skill for DevOps Basics. Triggers on: package json manager, package json manager Part of the DevOps Basics skill category.
33
0%
Does it follow best practices?
Impact
93%
0.97xAverage 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/package-json-manager/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 with no substantive content. It fails to describe any concrete actions, lacks natural trigger terms users would say, and provides no guidance on when Claude should select this skill. It would be nearly useless for skill selection among multiple available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Reads, creates, and modifies package.json files, manages npm dependencies, updates version numbers, and configures scripts.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about package.json, npm dependencies, adding/removing packages, updating versions, or managing Node.js project configuration.'
Include common file extensions and tool names as trigger terms such as 'package.json', 'npm', 'yarn', 'dependencies', 'devDependencies', '.json' to improve matching accuracy.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is an 'Auto-activating skill for DevOps Basics' without describing what it actually does with package.json files (e.g., add dependencies, update versions, manage scripts). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no description of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'package json manager' repeated twice. It misses natural user phrases like 'package.json', 'npm dependencies', 'add dependency', 'update version', 'node modules', or 'scripts'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any DevOps or Node.js-related skill. 'Package Json Manager' as a name hints at a niche, but the description provides no distinguishing details about its specific capabilities. | 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. It contains only generic boilerplate text that could apply to any skill topic, with no specific guidance, commands, code examples, or workflows related to package.json management. It provides zero value to Claude beyond what it already knows.
Suggestions
Add concrete, executable examples of common package.json operations (e.g., adding dependencies, configuring scripts, setting version fields) with actual JSON snippets and npm/yarn commands.
Define a clear workflow for common tasks like initializing a package.json, managing dependencies, or configuring build scripts, with validation steps (e.g., `npm install --dry-run`, `npm audit`).
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe meta-information about the skill rather than teaching actionable content.
Include specific best practices for package.json management such as version pinning strategies, script conventions, engine constraints, and peer dependency handling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific information about package.json management, and pads with vague descriptions like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No commands, no code examples, no specific instructions for any package.json task. The entire content describes rather than instructs, offering only vague promises of capability. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to supporting files, and no bundle files exist. The structure is just a series of empty boilerplate sections with no substantive information at any level. | 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.