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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill key-rotation-managerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It reads like auto-generated boilerplate with no actual content describing what the skill does, what actions it performs, or when it should be triggered. The repeated trigger term and lack of any concrete capabilities make this description nearly useless for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Rotates API keys, manages credential lifecycles, schedules automatic key expiration, and updates key references across configurations.'
Include a 'Use when...' clause with natural trigger terms like 'rotate keys', 'API key expiration', 'credential rotation', 'secret rotation', 'renew API keys'.
Remove the redundant trigger term and boilerplate category text, replacing with meaningful capability descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Key Rotation Manager' is just a name, and 'Auto-activating skill for Security Advanced' provides no information about what the skill actually does. | 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 guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'key rotation manager' repeated twice, which is redundant and unlikely to match natural user language. Users would more likely say 'rotate keys', 'API key rotation', 'credential rotation', or 'secret management'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'key rotation' is somewhat specific to a security domain, which provides some distinctiveness. However, without concrete actions described, it could still conflict with other security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about key rotation management. It contains only generic placeholder text that could apply to any skill topic, with no executable code, specific procedures, or actionable guidance for implementing key rotation in any context.
Suggestions
Add concrete code examples for key rotation (e.g., rotating AWS KMS keys, database credentials, API tokens) with specific commands and scripts
Define a clear workflow with validation steps: inventory current keys → generate new keys → update references → verify functionality → deprecate old keys → delete old keys
Include specific guidance for different key types (symmetric, asymmetric, API keys, certificates) with rotation intervals and compliance requirements
Add references to detailed documentation for specific platforms (AWS, GCP, Azure, HashiCorp Vault) rather than generic claims about 'best practices'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about key rotation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude already understands. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code, no commands, no specific steps for implementing key rotation. The entire skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. No validation checkpoints, no sequence, no process for key rotation operations. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, no links to related materials. The 'Related Skills' section mentions a category but provides no navigation. | 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.