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 that repeats the skill name without describing any capabilities, use cases, or trigger conditions. It provides no actionable information for Claude to determine when to select this skill over others. It scores at the lowest level across all dimensions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Reads, writes, validates, and merges JSON configuration files for applications and infrastructure tools.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about editing JSON configs, managing settings files, .json files, environment configuration, or config validation.'
Include distinguishing details that separate this from general JSON or DevOps skills, such as specific tools or config formats supported (e.g., package.json, tsconfig.json, Docker configs).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Json Config Manager' but never describes any concrete actions like reading, writing, validating, or merging JSON config files. It's essentially just a name repeated with no capability details. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explicit trigger guidance or 'Use when...' clause, and the 'what' is entirely absent beyond the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'json config manager' repeated twice. It lacks natural user keywords like 'JSON', 'config file', 'configuration', 'settings', '.json', 'parse', 'edit config', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any skill involving JSON, configuration files, or DevOps tooling. There are no distinct triggers or scoping details to differentiate it. | 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 instructional content. It consists entirely of boilerplate meta-descriptions about what the skill supposedly does without providing any concrete guidance, code, commands, or workflows for JSON config management. It would provide zero value to Claude beyond what it already knows.
Suggestions
Replace the boilerplate with actual executable examples of JSON config management tasks (e.g., reading/writing JSON configs with jq, Python, or Node.js; merging configs; validating schemas).
Add a concrete workflow with steps for common operations like environment-specific config management, secret handling, and config validation with explicit validation checkpoints.
Include specific code snippets for tools like jq, jsonschema, or config templating approaches (e.g., envsubst, Jsonnet) that are copy-paste ready.
Remove all meta-sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content organized by task type (e.g., '## Merge configs', '## Validate schema', '## Environment overrides').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'json config manager' excessively, and provides zero substantive information about what JSON config management actually entails. | 1 / 3 |
Actionability | There are no concrete code examples, commands, configuration snippets, or executable guidance whatsoever. The content only describes vague capabilities ('provides step-by-step guidance') without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any indication of how to actually perform JSON config management tasks. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed files, and no navigation structure. The sections that exist (Purpose, When to Use, Capabilities, Example Triggers) are all meta-descriptions with no substance. | 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.