What problem does it solve? Writing credential-shaped test fixtures often triggers secret-scanning failures during code review, and inventing fake tokens by hand risks either failing admission checks or accidentally resembling real secrets. This Skill provides a deterministic process for choosing exact, catalog-approved synthetic access, refresh, ID, API-key, and bearer token values that pass review secret admission. ## Core Features & Use Cases - Catalog-driven token selection: Queries the installed review helper's synthetic-tokens commands to list, filter, and retrieve approved token values by role (access, refresh, id, api-key, bearer) and lifecycle state (active, expired, consumed). - Stable fixture authoring: Records selected token IDs with each fixture so later work reuses the same values instead of reselecting after a catalog update, and provides placeholder-only templates for OAuth sessions, lifecycle transitions, and independent credentials. - Historical exemption handling: Inspects helper-owned legacy exemption envelopes for values already proven in master history, without registering pull-request-only values as legacy. - Use Case: When adding a test that models an expired access token and an active refresh token, run the helper's list command, filter by role and state, retrieve the exact values by ID, and insert them verbatim into the fixture. ## Quick Start Ask the assistant to use synthetic-token-fixtures to choose review-safe synthetic token values for a new credential-shaped test fixture.
