key-rotation-manager
Key Rotation Manager - Auto-activating skill for Security Advanced. Triggers on: key rotation manager, key rotation manager Part of the Security Advanced skill category.
35
3%
Does it follow best practices?
Impact
92%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/key-rotation-manager/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 across all dimensions. It is essentially a title and category label with no substantive content—no concrete actions, no natural trigger terms beyond the skill name repeated, and no guidance on when to use it. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Rotates API keys, database credentials, and encryption keys; schedules automatic rotation intervals; updates dependent services with new credentials.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about rotating keys, renewing credentials, expiring secrets, updating API keys, or managing key lifecycle.'
Include common keyword variations users might say, such as 'rotate secrets', 'key expiration', 'credential rotation', 'renew API key', 'secret management', '.env key update'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Key Rotation Manager') and states it's part of 'Security Advanced' but never describes what it actually does—no mention of rotating keys, generating new keys, updating configurations, or any specific capability. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'key rotation manager' repeated twice. There are no natural user keywords like 'rotate keys', 'API key expiration', 'secret rotation', 'credential renewal', 'rotate credentials', etc. that users would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'key rotation' is somewhat specific to a security domain niche, which provides some distinctiveness. However, the lack of concrete actions and the vague 'Security Advanced' category label could cause overlap with other security-related 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 shell with no actual content. It repeatedly references 'key rotation manager' without ever defining what key rotation involves, providing any concrete steps, code, or configurations. It reads as auto-generated boilerplate that would provide zero value to Claude when performing key rotation tasks.
Suggestions
Add concrete, executable code examples for key rotation workflows (e.g., rotating AWS KMS keys, database credential rotation, TLS certificate rotation) with specific CLI commands or API calls.
Define a clear multi-step workflow with validation checkpoints: generate new key → update dependent services → verify functionality → revoke old key → confirm revocation.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than providing actionable guidance.
Add specific examples for at least one key rotation scenario (e.g., AWS secrets rotation with code) and reference separate files for additional scenarios like database credentials or API keys.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or code. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no specific steps, no configuration examples. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Key rotation is inherently a multi-step process involving generating new keys, updating references, validating, and revoking old keys, yet none of this is addressed. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain no useful information. There are no references to detailed files, no examples, and no structured navigation to deeper content. The sections are just boilerplate. | 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
87f14eb
- 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.