Content
11%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder — it repeats its own description three times and provides no actionable content whatsoever. For a security-focused skill about preventing secret exposure, the complete absence of concrete patterns, commands, validation steps, or examples is particularly problematic. It fails to teach Claude anything it could act on.
Suggestions
Add concrete, executable examples showing how to securely load environment variables (e.g., using .env files with dotenv, reading from a secrets manager) without exposing them in logs or terminal output.
Define a clear workflow with validation steps: e.g., 1) check .gitignore includes .env, 2) load secrets via specific pattern, 3) verify no secrets appear in command output, 4) validate git staging doesn't include secret files.
Add specific anti-patterns and guardrails, such as 'Never use echo $SECRET or print(os.environ[...])' and 'Always use subprocess with env parameter rather than shell interpolation'.
Remove the redundant 'When to Use' and 'Instructions' sections that just repeat the overview, and replace them with actual instructional content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with repetitive descriptions — the overview, 'when to use' section, and instructions all say essentially the same thing. Despite being short, it wastes tokens by repeating the description three times without adding any new information. | 2 / 5 |
Actionability | There is zero concrete guidance — no code, no commands, no specific steps, no examples. The entire content is a vague description that tells Claude nothing about how to actually manage environment variables securely. | 1 / 5 |
Workflow Clarity | No steps, no sequence, no validation checkpoints. For a skill involving security-sensitive operations (secrets management), the complete absence of any workflow or safety checks is a critical gap. | 1 / 5 |
Progressive Disclosure | There are section headers providing minimal structure, but no bundle files exist and the only reference is an external GitHub link with no indication of what it contains. There's no meaningful content to organize or disclose progressively. | 2 / 5 |
Total | 6 / 20 Passed |