CtrlK

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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill json-config-manager

What are skills?

Overall
score

17%

Review — 0%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely lacking across all dimensions. It provides only boilerplate metadata (skill name, category, redundant trigger) without any explanation of capabilities, concrete actions, or usage guidance. Claude would have no meaningful information to determine when to select this skill over others.

Suggestions

Add specific actions the skill performs, e.g., 'Reads, validates, edits, and merges JSON configuration files. Handles nested structures, environment-specific configs, and schema validation.'

Include a 'Use when...' clause with natural trigger terms: 'Use when working with JSON config files, .json settings, package.json, tsconfig.json, or when the user needs to modify configuration values.'

Remove the redundant trigger term repetition and replace with varied, user-natural phrases that distinguish this from other config-related skills (YAML, TOML, env files).

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 both 'what does this do' and 'when should Claude use it'. It only provides metadata about the skill category and a redundant trigger phrase, with no functional description or use-case guidance.	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. No clear niche is established.	1 / 3
	Total	4 / 12 Passed

Implementation

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

69%

Warnings & errors only

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: 23 days ago

Table of Contents

Activation Implementation Validation

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.