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
Quality
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 functional content. It fails on all dimensions by providing only a skill name and category without describing any capabilities, use cases, or natural trigger terms. The repeated trigger term 'package json manager' suggests auto-generated content that wasn't properly completed.
Suggestions
Add specific actions the skill performs, e.g., 'Manages package.json files: add/remove dependencies, update versions, validate structure, run npm scripts'
Include a 'Use when...' clause with natural trigger terms like 'package.json', 'npm install', 'add dependency', 'node packages', 'update npm package'
Remove the redundant trigger term and replace with varied, user-natural phrases that would indicate need for this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Package Json Manager' is just a name, not a description of capabilities. There's no indication of what actions this skill performs (e.g., add dependencies, update versions, validate structure). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states it's 'auto-activating' and part of 'DevOps Basics' without any functional description or explicit use-case triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'package json manager' repeated twice, which is not a natural phrase users would say. Missing obvious terms like 'package.json', 'npm', 'dependencies', 'node modules', 'add package', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'DevOps Basics' is extremely broad and could conflict with many other skills. Without specific capabilities listed, there's no clear niche established. | 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 essentially a placeholder template with no actual instructional content. It describes what a package.json manager skill would do but provides zero actionable guidance, code examples, or specific instructions. The entire content is meta-description about the skill rather than the skill itself.
Suggestions
Add concrete code examples for common package.json operations (adding dependencies, updating versions, running scripts)
Include specific commands like 'npm install', 'npm update', or 'npm run' with actual usage patterns
Provide a quick reference for package.json structure and common fields (scripts, dependencies, devDependencies)
Replace the generic 'Capabilities' section with actual step-by-step workflows for tasks like dependency management or script configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about package.json management. 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 abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable instructions. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any actual procedural guidance for package.json management tasks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual content. There are no references to detailed materials, examples, or related documentation that would provide real value. | 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
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.