Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Centralized workflow for storing, testing, and tracking API tokens. Saves tokens to a canonical .env file with expiration dates, runs a permission test battery against each service, and creates calendar reminders before tokens expire. Documents capabilities and renewal instructions in a per-service connections folder.
Keeps all tokens in one predictable location with expiration tracking and automated renewal reminders, so credentials are never re-requested or silently expired mid-project.
When to use it
- Adding a new Jira API token and recording its scope and expiry
- Getting a 7-day warning before a GitHub personal access token expires
- Checking whether a credential already exists before requesting one from a colleague
- Running a quick permissions audit on a newly received API key
- Building a searchable index of all active service credentials in one place
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: 'salva API key pra Figma, expires 2027-03-01'
- 1Git commits the current .env state as a safety checkpoint before making changes
- 2Appends FIGMA_TOKEN=value with an expiration comment to ~/Documents/life/.env
- 3Creates an all-day Google Calendar event on 2027-02-22 with a renewal reminder and the token settings URL
- 4Runs a test script against the Figma API to enumerate what the token can read or write
- 5Creates ~/Documents/life/connections/figma.md with token metadata, scope summary, and code usage examples
Token stored in .env, permissions documented in connections/figma.md, and a renewal reminder scheduled 7 days before expiry
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.