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.
35
3%
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
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 extremely weak across all dimensions. It is essentially just a name and category label with no concrete actions, no natural trigger terms, and no explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other DevOps-related skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, validates, and updates package.json files, manages npm dependencies, configures scripts and metadata.'
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 configuring Node.js project metadata.'
Remove the duplicate trigger term 'package json manager' and replace with varied natural language terms users would actually say, such as 'package.json', 'npm', 'node dependencies', 'add package', 'update dependency'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is a 'Package Json Manager' and an 'auto-activating skill for DevOps Basics' without describing what it actually does (e.g., create, edit, validate, update dependencies in package.json files). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the name itself. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'package json manager' repeated twice. It misses natural user phrases like 'package.json', 'npm dependencies', 'add dependency', 'update packages', 'node modules', 'scripts', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'package json' does narrow the domain somewhat compared to a fully generic description, but without specific actions or triggers it could overlap with general Node.js, npm, or DevOps skills. | 2 / 3 |
Total | 5 / 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 managing package.json files. It contains only generic boilerplate descriptions of what the skill could do without providing any concrete guidance, commands, code examples, or workflows. It fails on every dimension because there is effectively no instructional content present.
Suggestions
Add concrete, executable examples of common package.json operations (e.g., adding dependencies, setting scripts, managing version fields) with actual code/commands like `npm init`, `npm install --save`, or direct JSON manipulation patterns.
Define a clear workflow for common tasks such as creating a new package.json, updating dependencies, resolving version conflicts, or auditing for vulnerabilities, with explicit validation steps (e.g., `npm ls` to verify dependency tree).
Replace all generic boilerplate sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') with actual actionable content covering specific package.json fields (scripts, dependencies, engines, exports) and best practices.
Add concrete examples showing proper semver ranges, common script patterns, and package.json configurations for different project types (library vs application).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains nothing Claude doesn't already know and provides zero actual guidance on managing package.json files. Every section is generic boilerplate that could apply to any skill. | 1 / 3 |
Actionability | There are no concrete commands, code examples, or specific instructions. The skill describes what it could do ('provides step-by-step guidance') without actually providing any guidance. No executable content whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or any actionable sequence. | 1 / 3 |
Progressive Disclosure | The content is a flat list of generic sections with no references to detailed materials, no links to related files, and no meaningful structure. The sections contain no real content to organize. | 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.