dotenv-manager
Dotenv Manager - Auto-activating skill for DevOps Basics. Triggers on: dotenv manager, dotenv manager Part of the DevOps Basics skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill dotenv-managerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely lacking across all dimensions. It provides no information about what the skill actually does, contains no natural trigger terms users would use, and offers no guidance on when Claude should select it. The description is essentially just a title and category label.
Suggestions
Add specific capabilities: describe what actions the skill performs (e.g., 'Creates, reads, and modifies .env files, manages environment variables, validates dotenv syntax').
Include natural trigger terms users would say: '.env', 'environment variables', 'env file', 'secrets', 'config file', 'environment configuration'.
Add an explicit 'Use when...' clause: 'Use when the user needs to create, edit, or manage .env files, set up environment variables, or configure application secrets.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Dotenv Manager' and category information. It doesn't explain what the skill actually does with dotenv files. | 1 / 3 |
Completeness | Missing both 'what' (no capabilities described) and 'when' (no explicit usage guidance). The 'Triggers on' clause only repeats the skill name rather than describing actual use cases. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'dotenv manager' repeated twice. Missing natural terms users would say like '.env', 'environment variables', 'env file', 'secrets', 'configuration'. | 1 / 3 |
Distinctiveness Conflict Risk | Very generic - 'DevOps Basics' category is broad, and without specific capabilities described, it's unclear how this differs from other environment/configuration management skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content about dotenv management. It describes what a skill should do in abstract terms but provides zero actionable guidance, code examples, or specific instructions for working with .env files, environment variables, or related tooling.
Suggestions
Add concrete code examples showing how to create, read, and manage .env files (e.g., using python-dotenv, direnv, or shell commands)
Include specific commands for common dotenv operations like loading variables, validating .env files, and handling different environments (dev/staging/prod)
Provide a clear workflow for managing environment variables securely, including what to commit vs. gitignore
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about dotenv management. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance on dotenv management. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any actual procedural content for managing dotenv files. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual content. There are no references to detailed materials because there is no substantive content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.