Api key manager

Skill a5c-ai/babysitter/library/specializations/sdk-platform-development/skills/api-key-manager

Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration

Install

npx -y skills add a5c-ai/babysitter --skill api-key-manager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

API key generation, rotation, and management system

SKILL.md

2.2 KB, as published. Nobody here has run it

API Key Manager Skill

Overview

This skill implements comprehensive API key management including secure generation, rotation policies, usage tracking, and quota enforcement.

Capabilities

Generate cryptographically secure API keys
Implement key rotation with grace periods
Track key usage and enforce quotas
Support key scoping and permissions
Configure key prefix patterns for identification
Implement key revocation and blacklisting
Support multiple key types (test, live)
Generate key hashes for secure storage

Target Processes

Authentication and Authorization Patterns
Developer Portal Implementation
Platform API Gateway Design

Integration Points

Key management systems (HashiCorp Vault)
Rate limiting middleware
Usage analytics systems
Developer portal UIs
API gateway key validation

Input Requirements

Key format requirements
Scoping/permission model
Rotation policy
Quota definitions
Storage security requirements

Output Artifacts

Key generation service
Key validation middleware
Rotation management system
Usage tracking integration
Quota enforcement rules
Admin management API

Usage Example

skill:
  name: api-key-manager
  context:
    keyFormat:
      prefix: "sk_"
      testPrefix: "sk_test_"
      livePrefix: "sk_live_"
      length: 32
    rotation:
      enabled: true
      gracePeriod: "7d"
    scopes:
      - read
      - write
      - delete
    quotas:
      default: 1000
      premium: 10000

Best Practices

Use cryptographically secure random generation
Prefix keys to indicate type (test/live)
Store only hashed keys in database
Implement rotation with overlap periods
Track usage per key for analytics
Support immediate revocation