dotenv-manager
Dotenv Manager - Auto-activating skill for DevOps Basics. Triggers on: dotenv manager, dotenv manager Part of the DevOps Basics skill category.
34
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 a placeholder with no functional content. It fails on every dimension: it names no concrete actions, includes no natural trigger terms beyond the skill's own name repeated, provides no guidance on when to use it, and is indistinguishable from any other DevOps-related skill.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, edits, validates, and parses .env files for managing environment variables in projects.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions .env files, environment variables, dotenv, secrets management, or configuration files.'
Remove the duplicate trigger term 'dotenv manager' and replace with varied natural language terms users would actually say, such as 'env file', 'environment config', '.env', 'environment variables'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Dotenv Manager' is a name, not a description of capabilities. There is no mention of what the skill actually does (e.g., create, edit, parse, validate .env files). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states the skill name and category, with no functional description or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'dotenv manager' repeated twice. It misses natural user terms like '.env', 'environment variables', 'env file', 'secrets', 'configuration', or 'dotenv'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's unclear what this skill does, making it impossible to distinguish from other DevOps or configuration-related skills. 'DevOps Basics' category label adds no distinctiveness. | 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 substantive content. It contains only generic boilerplate descriptions that could apply to any skill topic, with no actual instructions, code, commands, or domain-specific knowledge about dotenv file management. It provides zero value to Claude beyond what the skill name alone conveys.
Suggestions
Add concrete, executable examples showing how to create, read, and manage .env files (e.g., creating .env templates, using python-dotenv or dotenv-cli, parsing env vars).
Include a clear workflow for common dotenv tasks such as setting up .env files, adding them to .gitignore, managing .env.example templates, and validating required variables are present.
Add specific security guidance: never commit .env files, how to handle secrets rotation, and validation steps to ensure sensitive values aren't leaked.
Replace all boilerplate sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') with actual actionable content—code snippets, commands, and configuration examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about dotenv management. Every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There are no concrete commands, code examples, configuration snippets, or specific instructions. The skill describes what it could do ('provides step-by-step guidance') without actually providing any guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined. There is no sequence of actions, no validation checkpoints, and no actual procedure for managing dotenv files. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 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
c8a915c
- 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.