system-environment-setup
Configure development and production environments for consistent and reproducible setups. Use when setting up new projects, Docker environments, or development tooling. Handles Docker Compose, .env configuration, dev containers, and infrastructure as code.
87
82%
Does it follow best practices?
Impact
96%
1.31xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
100%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 is a strong skill description that clearly articulates specific capabilities (Docker Compose, .env configuration, dev containers, IaC), provides explicit trigger guidance with a 'Use when...' clause, and uses natural keywords developers would actually say. The description is well-scoped to environment configuration, making it distinct from other development-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure development and production environments', 'setting up new projects', 'Docker environments', 'development tooling', 'Docker Compose', '.env configuration', 'dev containers', 'infrastructure as code'. | 3 / 3 |
Completeness | Clearly answers both what ('Configure development and production environments', 'Handles Docker Compose, .env configuration, dev containers, and infrastructure as code') AND when ('Use when setting up new projects, Docker environments, or development tooling'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Docker', 'Docker Compose', '.env', 'dev containers', 'infrastructure as code', 'development environments', 'production environments', 'new projects', 'development tooling'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on environment configuration with distinct triggers like 'Docker Compose', '.env', 'dev containers', 'infrastructure as code' that are unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable configuration examples for environment setup with excellent code quality. However, it's overly long for a SKILL.md overview, lacking validation checkpoints for multi-service orchestration, and includes placeholder sections that waste tokens. The content would benefit from splitting detailed configs into reference files and adding explicit verification steps.
Suggestions
Add validation checkpoints after docker-compose up (e.g., 'Verify: docker-compose ps should show all services as healthy') and include troubleshooting for common failures
Move the detailed Terraform configuration to a separate TERRAFORM.md reference file, keeping only a brief overview and link in the main skill
Remove the empty placeholder Examples section and Metadata boilerplate, or populate them with actual useful content
Add a verification step for environment variable loading (e.g., 'Run npm run env:check to validate all required variables are set')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial configuration examples but includes some unnecessary verbosity. The Terraform section is extensive for what could be a reference link, and the metadata/examples sections at the end are placeholder boilerplate that adds no value. | 2 / 3 |
Actionability | Excellent executable examples throughout - complete docker-compose.yml, working TypeScript code for env loading, full Makefile with real commands, and Terraform configurations. All code is copy-paste ready with realistic values. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but lacks explicit validation checkpoints. No verification steps after docker-compose up, no health check validation, and no feedback loops for when services fail to start or configurations are invalid. | 2 / 3 |
Progressive Disclosure | References section links to external docs appropriately, but the skill itself is monolithic. The Terraform section and detailed configurations could be split into separate reference files. The 'Related Skills' section suggests structure exists but content is all inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.