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
Quality
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 only provides the skill name, a duplicate trigger term, and a category label without explaining what the skill does or when it should be used. Claude would have no meaningful basis for selecting this skill appropriately.
Suggestions
Add specific actions the skill performs (e.g., 'Parse, validate, and modify JSON configuration files. Create new config files from templates, merge configurations, and update nested values.')
Add a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions JSON configs, .json files, configuration settings, package.json, tsconfig, or needs to edit/create config files.')
Include file extensions and common config file names as trigger terms (e.g., '.json', 'package.json', 'config.json', 'settings.json', 'tsconfig.json')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Json Config Manager' and category metadata. There is no explanation of what the skill actually does (e.g., parse, validate, edit, merge JSON configs). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' field just repeats the skill name without meaningful context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'json config manager' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms like 'JSON', 'config file', 'configuration', 'settings.json', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'DevOps Basics' category and 'config manager' could overlap with YAML configs, environment variables, or any configuration-related skill. | 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 an empty template with no substantive content. It describes what a JSON config manager skill would theoretically do but provides absolutely no actual guidance, code, examples, or techniques for managing JSON configurations. The entire content could be replaced with a single sentence and lose nothing of value.
Suggestions
Add concrete, executable code examples for common JSON config operations (reading, writing, merging, validating JSON files)
Include specific tools and commands (e.g., jq for CLI manipulation, Python json module patterns, schema validation with jsonschema)
Provide a clear workflow for common tasks like environment-specific config management, secrets handling, and config validation in CI/CD pipelines
Remove all generic boilerplate text and replace with actionable technical content that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about JSON config management. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific techniques for managing JSON configs. The skill describes what it claims to do rather than actually instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no processes, and no validation checkpoints. The content only describes trigger conditions, not how to actually perform JSON config management tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples to follow, and no organization of actual technical content because there is none 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
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.