managing-environment-configurations
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-environment-configurationsImplement 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no environment-config-specific content. It provides abstract project management steps that could apply to any task, without any concrete commands, code examples, or specific guidance for managing environment configurations. The content fails to teach Claude anything it doesn't already know about general software development practices.
Suggestions
Add concrete code examples showing how to read/write environment config files (e.g., .env parsing, YAML config loading, environment variable management)
Include specific CLI commands or scripts for common operations like syncing configs between environments, validating config schemas, or diffing configurations
Replace generic steps with environment-config-specific workflows (e.g., 'Load .env file -> Validate required keys exist -> Merge with defaults -> Export to target format')
Remove or populate the empty 'Overview' and 'Examples' sections with actual content demonstrating real usage patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that Claude already knows. Phrases like 'Understanding of the system architecture and dependencies' and 'Review plan with team or stakeholders if needed' add no actionable value. The entire content reads like a generic project management template rather than a specific skill. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. Every instruction is abstract ('Execute implementation', 'Verify changes work as expected') with no specific guidance on HOW to manage environment configurations. No actual config file formats, CLI commands, or code snippets provided. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (assess, design, implement, validate, deploy), but they are entirely generic and lack specific validation checkpoints. No concrete validation commands or feedback loops - just vague instructions like 'Run comprehensive tests' without specifying what tests. | 2 / 3 |
Progressive Disclosure | References external files (templates, docs, examples) which is good structure, but all paths use placeholder `{baseDir}` with no indication these files exist or what they contain. The 'Overview' and 'Examples' sections at the end are empty placeholders that add nothing. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
67%The description has good structural completeness with explicit 'Use when' and 'Trigger with' clauses, but suffers from vague capability language ('comprehensive guidance and automation') that doesn't tell Claude what specific actions this skill enables. The trigger terms are reasonable but miss common natural language variations users would actually say.
Suggestions
Replace 'comprehensive guidance and automation' with specific concrete actions like 'create .env files, validate configuration schemas, sync environment variables across deployments'
Expand trigger terms to include natural variations: '.env files', 'environment variables', 'config files', 'secrets management', 'dotenv', 'settings'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (environment and configuration management) and mentions 'guidance and automation' but lacks specific concrete actions. What does 'comprehensive guidance' actually mean? No specific actions like 'create .env files', 'validate configs', or 'sync secrets' are listed. | 2 / 3 |
Completeness | Explicitly answers both what ('Implement environment and configuration management with comprehensive guidance and automation') and when ('Use when you need to work with environment configuration. Trigger with phrases like...'). Has clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant triggers ('manage environments', 'configure environments', 'sync configurations') but misses common natural variations users would say like '.env files', 'environment variables', 'config files', 'secrets', 'dotenv', or 'settings'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Environment configuration' is somewhat specific but could overlap with deployment skills, DevOps skills, or general project setup skills. The term 'configuration management' is broad and could conflict with infrastructure-as-code or settings management skills. | 2 / 3 |
Total | 9 / 12 Passed |
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.