What problem does it solve?
Managing API keys across multiple projects is error‑prone and insecure when each credential is stored or entered separately, leading to duplication, accidental exposure, and broken environments.
Core Features & Use Cases
- Multi‑format parsing: Reads Access.txt files in colon‑separated, key‑value, or informal layouts.
- Regex extraction: Identifies keys for services such as OpenAI, Anthropic, Render, Reddit, Supabase, and many others.
- Automatic validation: Sends lightweight API calls to confirm each key’s validity before use.
- .env generation: Writes discovered credentials to a project’s .env file and updates .gitignore.
- Missing‑key reporting: Alerts the user to any required credentials that were not found and provides guidance.
Quick Start
Ask the credentials skill to load my API keys from ~/Documents/Access.txt and create a .env file for the project.