api-key-manager
Api Key Manager - Auto-activating skill for Security Fundamentals. Triggers on: api key manager, api key manager Part of the Security Fundamentals skill category.
32
0%
Does it follow best practices?
Impact
92%
1.08xAverage 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/api-key-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 substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It fails across all dimensions of the rubric.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates, rotates, stores, and validates API keys and secrets. Manages environment variables and credential files.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions API keys, secret keys, credentials, .env files, key rotation, or managing access tokens.'
Include common user-facing synonyms and file types to improve trigger coverage, such as 'API secrets', 'access tokens', 'credential management', 'environment variables', '.env'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names the skill ('Api Key Manager') and mentions it's part of 'Security Fundamentals' but never describes what it actually does—no verbs like 'rotates', 'generates', 'stores', 'validates', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description only states the skill name and category without explaining functionality or trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api key manager' repeated twice. There are no natural user phrases like 'api key', 'secret key', 'rotate keys', 'manage credentials', 'API secrets', '.env file', etc. that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any security-related skill. 'Security Fundamentals' is a broad category label, and without specific actions or triggers, there's no way to distinguish this from other security or credential management skills. | 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 shell with no actionable content whatsoever. It consists entirely of auto-generated boilerplate that describes a skill's existence rather than providing any actual guidance on API key management. There is no technical substance—no code, no commands, no security patterns, no concrete instructions of any kind.
Suggestions
Add concrete, executable code examples for common API key management tasks (e.g., generating keys, storing them securely using environment variables or secret managers, rotating keys, revoking compromised keys).
Define a clear workflow with validation steps, such as: 1) Check for hardcoded keys in codebase, 2) Move keys to secure storage, 3) Validate access still works, 4) Remove old keys from version history.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actionable content: specific patterns for key storage, rotation schedules, and detection of leaked keys.
Include concrete security guidance such as specific .gitignore patterns, environment variable usage examples, and integration with secret management tools (e.g., AWS Secrets Manager, HashiCorp Vault).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about API key management, and pads with generic phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' without any substance. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific commands, no actual instructions on how to manage API keys. The entire skill describes what it could do rather than instructing Claude on what to do. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill merely lists vague capabilities without any process for accomplishing API key management tasks. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external resources, and the content itself is a flat, monolithic block of generic text with no meaningful structure or 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
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.