Skip to content
TakoAPI
Back to skills

key-expiry-tracker

by tradmangh

Communication
—Not yet rated
Your rating

Brief

Track **only expiry dates** (metadata) for API keys/client secrets/certificates and alert before they expire.

Description

What This Skill Does

Tracks expiry dates for API keys, client secrets, certificates, and tokens using a local JSON file. Alerts at 14-day and 7-day thresholds before expiry. Stores no credential values, only labels and timestamps.

Because it tracks only expiry metadata and never reads actual credential values, you get expiry visibility without any secrets leaving your local machine.

When to Use It

  • Catching an Azure AD client secret before it expires and breaks an integration
  • Getting weekly reminders about SSL certificates nearing their expiry date
  • Keeping a central inventory of API key expiry dates across multiple projects
  • Tracking OAuth token lifespans for several third-party services at once
  • Setting up automated Sunday checks to surface credentials expiring that week

Example Workflow

INPUT

User asks: check which credentials are expiring soon

AGENT
  1. 1

    Read ~/.openclaw/workspace/.credentials.json

  2. 2

    Compare each credential's expires timestamp against the current date

  3. 3

    Classify entries as expired, critical (7 days or less), or warning (14 days or less)

  4. 4

    Return a grouped summary with credential name, type, provider, and days remaining

OUTPUT

A report listing 2 credentials in warning state and 1 already expired, with names, providers, and exact expiry dates

Installation

clawhub install tradmangh/key-expiry-tracker

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links