managing-environment-configurations

Implement environment and configuration management with comprehensive guidance and automation. Use when you need to work with environment configuration. Trigger with phrases like "manage environments", "configure environments", or "sync configurations".

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/devops/environment-config-manager/skills/managing-environment-configurations/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-structured with concrete tool names and a useful error-handling table, but it lacks executable examples, integrated validation feedback loops, and links to the bundled scripts/assets.

Suggestions

Add at least one copy-paste-ready command or code snippet for the core operations (e.g. a `sops --encrypt` invocation or a ConfigMap generation command).

Weave an explicit validate->fix->retry checkpoint into the workflow (e.g. after step 7: run the validation script, and if it fails, fix missing vars and re-run before promoting).

Link the bundled scripts from the relevant steps (e.g. "run scripts/validate_config.py" at the validation step, "scripts/encrypt_secrets.py" at the encryption step) so the existing bundle is discoverable.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) without explaining concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Steps name specific tools and conventions (sops, sealed-secrets, APP_DATABASE_HOST, .env.production), but there are no executable commands or code blocks, so it is not copy-paste ready per the anchor 3 bar.	2 / 3
Workflow Clarity	The nine steps are clearly sequenced and include a validation step and an approval gate, but no explicit validate->fix->retry feedback loop is integrated into the workflow for these batch/destructive config operations.	2 / 3
Progressive Disclosure	Sections are well-organized and the body is largely self-contained, but the provided bundle directories (scripts/, assets/) are never referenced or linked from the body, so navigation to bundle material is missing.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description answers both what and when with explicit triggers and a clear niche, but its action statement is padded with vague fluff ("comprehensive guidance and automation") and its trigger terms lack breadth.

Suggestions

Replace "comprehensive guidance and automation" with 2-3 concrete actions (e.g. "externalize values into .env files, encrypt secrets with SOPS, and generate Kubernetes ConfigMaps").

Broaden trigger phrases to include common user terms such as "environment variables", ".env files", "secrets", or "ConfigMaps" in addition to the existing environment/configuration variants.

Dimension	Reasoning	Score
Specificity	It names the domain ("environment and configuration management") and an action ("Implement"), but "comprehensive guidance and automation" is vague fluff rather than a list of concrete actions, so it stops short of the multi-action anchor 3.	2 / 3
Completeness	It explicitly states what ("Implement environment and configuration management...") and when ("Use when you need to work with environment configuration") with explicit trigger phrases, satisfying both halves of the anchor 3.	3 / 3
Trigger Term Quality	The explicit triggers "manage environments", "configure environments", and "sync configurations" are natural, but they are narrow variants of one root and omit common variations users would say (e.g. environment variables, .env files, secrets, ConfigMaps).	2 / 3
Distinctiveness Conflict Risk	The environment/configuration-management niche with distinct triggers ("manage environments", "sync configurations") is clearly scoped and unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/environment-config-manager/skills/managing-environment-configurations/SKILL.md
Commit: 4c47e33

Reviewed: about 15 hours ago

Table of Contents

Discovery 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.