Agent skill · software engineering · jeremylongshore
persona-install-auth
Configure sandbox and production Persona API keys, dated API-version headers, and a least-privilege client boundary. Use when bootstrapping or rotating Persona credentials. Trigger with: "set up Persona auth", "rotate Persona API key", "configure Persona environment".
Why this skill is useful
Adds specific API configuration steps and error handling for Persona's identity verification API that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires withpersona account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Persona Environment and Least-Privilege API Key Setup Overview Establish an explicit environment boundary before any identity workflow. Persona API keys are environment-specific, may carry different configured API versions, and must reach https://api.withpersona.com/api/v1; a credential check must not create or mutate an inquiry. Prerequisites Persona Dashboard access authorized for the target environment A named service owner, secret store, and rotation window The approved dated Persona API version; current documentation shows 2025-12-08 Instructions Step 1: Inventory the boundary Record sandbox or production, owning service, inquiry template, API-key permissions, configured API version, and secret-store location. Never infer environment from an untrusted request. Step 2: Create and store the key Create the narrowest key supported by the Dashboard. Put the value in the deployment secret store, expose it only as PERSONAAPIKEY, and retain only the key name and final four characters in receipts. Step 3: Pin request metadata Set the base URL to https://api.withpersona.com/api/v1. Send Authorization: Bearer ..., Persona-Version: 2025-12-08 or the reviewed target version, Accept: application/json, and Content-Type: application/json for bodies. Step 4: Run a read-only probe List one inquiry or call another approved read endpoint. Capture status, response request identifier, rate-limit headers, environment, and API version without storing response PII. Step 5: Prove separation and rotation Confirm sandbox and production secrets cannot be swapped by configuration fallback. Exercise dual-secret rollout, old-key revocation, and rollback in sandbox before production. Authentication Persona REST authentication uses an environment-scoped API key as a bearer token. The Persona-Version request header overrides the version configured on that key for the request, so pin it deliberately and test each key independently. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/persona-install-auth