env-secret-detector
Env Secret Detector - Auto-activating skill for Security Fundamentals. Triggers on: env secret detector, env secret detector Part of the Security Fundamentals skill category.
36
3%
Does it follow best practices?
Impact
96%
0.96xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/env-secret-detector/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 reads like an auto-generated stub rather than a useful skill description. It provides no concrete actions, no natural trigger terms users would say, and no explicit guidance on when Claude should select this skill. The repeated trigger term and boilerplate category mention add no value.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Scans code and configuration files for exposed secrets, API keys, tokens, and credentials in .env files and environment variables.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions secrets, API keys, credentials, .env files, leaked tokens, environment variable security, or secret scanning.'
Remove the redundant duplicate trigger term and replace with varied natural language phrases users would actually say when needing this capability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Env Secret Detector' names a concept but never describes what it actually does—no verbs like 'scans', 'detects', 'flags', or 'removes' are present. The language is entirely abstract. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is limited to a redundant trigger phrase. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'env secret detector' repeated twice, which is not a phrase users would naturally say. Missing natural terms like 'secrets', 'API keys', 'credentials', '.env file', 'leaked secrets', 'environment variables', 'sensitive data'. | 1 / 3 |
Distinctiveness Conflict Risk | The name 'Env Secret Detector' is somewhat specific to a niche (detecting secrets in environment files), which provides some distinctiveness. However, the lack of concrete description means it could overlap with broader security scanning 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 placeholder with no substantive content. It contains only generic boilerplate text that repeats the skill name without providing any actual guidance on detecting secrets in environment files. There are no code examples, no regex patterns, no detection strategies, no tool recommendations, and no actionable instructions of any kind.
Suggestions
Add concrete regex patterns or code for detecting common secret formats (API keys, tokens, passwords) in .env files and environment variables.
Provide an executable workflow: e.g., 1) scan files with a specific command/script, 2) classify findings by severity, 3) report or remediate, with validation at each step.
Include specific examples showing input (a sample .env file with secrets) and expected output (detected secrets with line numbers and types).
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that add no actionable information and replace with actual detection logic and best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'env secret detector' excessively, and provides zero domain-specific information. Every section is padded with generic phrasing. | 1 / 3 |
Actionability | There are no concrete steps, no code examples, no commands, no patterns for detecting secrets in environment files. The content is entirely abstract and descriptive, offering no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 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 organization of content across sections. | 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.