rotate-credential

Rotate credentials across the Anton repository with preconditions, verification, and rollback.

3|Updated May 13, 2025
One-click install
npx skills add https://github.com/wcygan/anton --skill rotate-credential
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rotate-credential
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/rotate-credential
Command: npx skills add https://github.com/wcygan/anton --skill rotate-credential

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Credential rotation across the Anton repository to minimize exposure and ensure continuity.

Core Features & Use Cases

  • End-to-end rotation rituals for age key, SOPS keys, Flux deploy key, 1Password token, and Cloudflare tunnel token.
  • Enforces preconditions, verification, and rollback steps with backups and provenance.
  • Supports auditable rollback and safe sequencing to minimize downtime.

Quick Start

Begin by performing Ritual 1 to rotate the age key, then sequentially perform Rituals 2 through 4 with verification after each step.

Frequently Asked Questions about rotate-credential

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rotate SOPS keys and age keys in a GitOps repository?

To rotate SOPS keys and age keys, this Skill executes end-to-end rotation rituals that update Flux secrets, verify preconditions, and enforce backups with provenance to minimize credential exposure risks.

What is the safest way to rotate a Cloudflare tunnel token and 1Password token together?

Rotating a Cloudflare tunnel token and 1Password token safely requires enforcing one-rotation-at-a-time discipline, verifying backups, and updating Flux secrets sequentially to minimize downtime and ensure continuity.

Can I rotate a Flux deploy key without causing downtime in my continuous deployment pipeline?

You can rotate a Flux deploy key without downtime by following safe sequencing steps that verify preconditions before rotation and update Flux secrets accordingly, ensuring auditable rollback if verification fails.

Does this credential rotation process support rollback if the new age key fails verification?

The credential rotation process supports auditable rollback by enforcing provenance and backups before each step, allowing you to safely revert the age key or SOPS keys if post-rotation verification fails.

Why do I need to rotate credentials across my infrastructure repository sequentially?

You need to rotate credentials sequentially to enforce one-rotation-at-a-time discipline, which prevents overlapping failures, maintains auditable backups, and ensures safe verification after each key or token update.