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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill package-json-managerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is critically deficient across all dimensions. It provides no information about what the skill actually does with package.json files, contains no natural trigger terms users would use, and lacks any explicit guidance on when Claude should select this skill. The description reads like auto-generated boilerplate rather than a functional skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Manages package.json files: add/remove dependencies, update versions, configure scripts, modify project metadata.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions package.json, npm dependencies, node packages, adding libraries, or managing project scripts.'
Add file type and technology keywords users would naturally say: 'package.json', 'npm', 'yarn', 'dependencies', 'devDependencies', 'node_modules', 'scripts'.
| 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 this skill actually does with package.json files. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's auto-activating and part of DevOps Basics, with no functional information or explicit usage 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', 'scripts', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'DevOps Basics' could overlap with many skills. Without specific actions or clear triggers, this could conflict with any npm, Node.js, or JavaScript project management skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content about package.json management. It contains only generic boilerplate text that could apply to any skill, with no executable code, specific commands, or actionable guidance. The skill fails to teach Claude anything about managing package.json files.
Suggestions
Add concrete code examples showing common package.json operations (adding dependencies, updating versions, running scripts)
Include specific npm/yarn commands with expected outputs (e.g., `npm init`, `npm install --save`, `npm version patch`)
Provide a workflow for common tasks like updating dependencies safely with validation steps
Replace generic capability descriptions with actual package.json structure examples and field explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about package.json management. Phrases like 'automated assistance' and '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 manage a package.json file. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only lists vague capabilities without any sequence of actions or validation checkpoints. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, and no clear organization of content for different use cases. | 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.