json-config-manager
Json Config Manager - Auto-activating skill for DevOps Basics. Triggers on: json config manager, json config manager Part of the DevOps Basics skill category.
33
0%
Does it follow best practices?
Impact
95%
1.00xAverage 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/json-config-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 on all dimensions: it names no concrete actions, includes no natural trigger terms, provides no 'Use when...' guidance, and is too generic to be distinguished from other skills. It would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Reads, validates, creates, and updates JSON configuration files. Supports merging configs, adding/removing keys, and formatting JSON.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to edit .json config files, manage JSON settings, parse configuration, or work with package.json, tsconfig.json, or similar config files.'
Remove the duplicate trigger term ('json config manager' is listed twice) and replace with varied natural phrases users would actually say, such as 'JSON config', 'configuration file', '.json', 'settings file', 'edit config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Json Config Manager' is a name, not a description of capabilities. There are no verbs describing what the skill actually does (e.g., parse, validate, merge, update JSON config 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 the description only states the skill name and category without explaining functionality or trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'json config manager' repeated twice. These are not natural phrases a user would say — users would more likely say 'edit JSON config', 'update configuration file', 'parse JSON', '.json file', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from any other skill that might deal with JSON, configuration files, or DevOps tasks. 'Config Manager' could overlap with YAML config, TOML config, environment variable management, or general file editing skills. | 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 substantive content. It contains only generic boilerplate descriptions that could apply to any topic, with no actual guidance on JSON config management. It fails on every dimension because it provides nothing actionable, concrete, or useful.
Suggestions
Add concrete, executable code examples showing how to read, write, validate, and merge JSON config files (e.g., using jq, Python's json module, or Node.js)
Define a clear workflow for common JSON config tasks such as: loading config → validating schema → merging overrides → writing output, with explicit validation steps
Replace the generic 'Capabilities' and 'Example Triggers' sections with actual technical content like JSON schema validation examples, environment-specific config patterns, and common pitfalls
Include specific tool recommendations and commands (e.g., jq filters, jsonschema validation, diff tools for config comparison) instead of vague references to 'best practices'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about JSON config management, and pads with vague capability descriptions and trigger phrases. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of JSON config structures, no specific tools or libraries mentioned. Every section describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful 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
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.