dotenv-manager
Dotenv Manager - Auto-activating skill for DevOps Basics. Triggers on: dotenv manager, dotenv manager Part of the DevOps Basics skill category.
34
Quality
0%
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
0%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 essentially metadata without substance. It names the skill and its category but provides zero information about what the skill actually does or when it should be selected. Claude would have no basis for choosing this skill over others when a user needs help with environment variables or .env files.
Suggestions
Add specific capabilities using action verbs: 'Creates, edits, and parses .env files. Manages environment variables, validates configuration syntax, and handles secrets.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions .env files, environment variables, dotenv, configuration files, API keys, or secrets management.'
Remove the duplicate trigger term and expand with variations users would naturally say: 'dotenv', '.env', 'env file', 'environment config', 'env vars'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Dotenv Manager') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating, editing, parsing, or managing .env files. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no 'Use when...' clause or explicit trigger guidance). Only metadata about categorization is provided. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'dotenv manager' repeated twice. Missing natural user terms like '.env', 'environment variables', 'env file', 'secrets', 'configuration', or 'API keys' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'DevOps Basics' category is generic, and without specific capabilities or triggers, this could conflict with any configuration, environment, or DevOps-related skill. | 1 / 3 |
Total | 4 / 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 actual content. It contains only meta-descriptions and trigger phrases but provides zero technical guidance on dotenv management - no code examples, no commands, no best practices, and no workflows. The skill fails to teach Claude anything actionable about managing dotenv files.
Suggestions
Add concrete code examples for common dotenv operations (creating, reading, parsing .env files with specific tools like python-dotenv or dotenv-cli)
Include a clear workflow for managing environment variables across development/staging/production environments with validation steps
Provide specific commands and patterns for dotenv best practices (e.g., .env.example templates, gitignore rules, secret management)
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual technical instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-descriptions Claude doesn't need. | 1 / 3 |
Actionability | There is zero executable guidance - no code, no commands, no specific steps for working with dotenv files. The content only describes what the skill claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed materials, no structured sections with actual content, and no navigation to supporting documentation. | 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
994edc4
- 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.