API keys designed for safe rotation and clear ownership.
What it does
Designs a platform's API-key lifecycle so consumers get scoped credentials, safe storage, manageable rotation, and clear ownership.
When to use it
Use for provider-side API-key design, prefixes, rotation, scoping, or employee-offboarding revocation; not for consuming another vendor's API or designing an OAuth authorization server.
How to use it
Give it an API-key design problem; it asks a batch of clarifying questions before developing the lifecycle design.
Good to know
- edits its own instructions
Latest review
What you need · 1
Hands off when third-party apps need OAuth, leaving this skill responsible for the boundary decision and key-side design; an installation requirement is unstated.
Access · 1
This skill
persistent memory
Write
Stores decisions in agent memory