dotenv-manager
Dotenv Manager - Auto-activating skill for DevOps Basics. Triggers on: dotenv manager, dotenv manager Part of the DevOps Basics skill category.
36
3%
Does it follow best practices?
Impact
98%
0.98xAverage 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/dotenv-manager/SKILL.mdQuality
Discovery
7%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 extremely weak—it is essentially a label with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. The only slight positive is that 'dotenv' is a somewhat distinctive term.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates, reads, updates, and validates .env files for managing environment variables and application secrets.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions .env files, environment variables, env vars, dotenv, secrets management, or application configuration.'
Remove the duplicate trigger term ('dotenv manager' is listed twice) and expand with common variations like '.env', 'environment variables', 'env config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Dotenv Manager') and its category ('DevOps Basics') without describing what it actually does—no mention of creating, reading, editing, or managing .env files. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no explanation of capabilities and no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'dotenv manager' repeated twice. There are no natural user keywords like '.env', 'environment variables', 'secrets', 'config files', or 'env vars' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'dotenv' is somewhat niche and points to a specific domain (.env file management), which provides some distinctiveness. However, the lack of concrete actions means it could overlap with general DevOps or configuration management skills. | 2 / 3 |
Total | 5 / 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 an empty template with no substantive content about dotenv management. It contains only generic boilerplate descriptions of what the skill claims to do without any actual instructions, code examples, commands, or technical guidance. It provides zero value to Claude beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable examples for common dotenv tasks: creating .env files, parsing them, managing environment-specific variants (.env.development, .env.production), and using tools like `dotenv` CLI or `python-dotenv`.
Include a clear workflow for dotenv management, e.g.: 1) Create .env.example with placeholder values, 2) Copy to .env and fill in real values, 3) Add .env to .gitignore, 4) Validate required variables are set before app startup.
Add security guidance: never commit .env files with secrets, use .env.example for documentation, integrate with secret managers for production, and validate that .gitignore properly excludes sensitive files.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching Claude how to perform dotenv management tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about dotenv management, and wastes tokens on generic meta-descriptions like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Actionability | There is zero actionable content—no commands, no code, no concrete steps for managing .env files. The skill describes what it could do rather than instructing Claude on how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints—just vague claims about providing 'step-by-step guidance' without any actual guidance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to reference either, but the skill body itself lacks any useful structure. | 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
13d35b8
- 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.