Agent skill · software engineering · jeremylongshore
persona-prod-checklist
Validate a Persona integration for production with evidence across identity flow, privacy, security, reliability, and rollback. Use when preparing a go-live. Trigger with: "launch Persona", "Persona production checklist", "approve Persona go-live".
Why this skill is useful
Adds specific implementation patterns and error handling for the Persona identity verification API that the AI wouldn't reliably generate on its own.
What it needs
Requires persona account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Persona Production Readiness Gate Overview A production key and passing happy path are not enough. The gate must prove environment isolation, template governance, API-version compatibility, authentic replay-safe webhooks, quota behavior, privacy controls, manual review, rollback, and accountable approval. Prerequisites Immutable release SHA and production architecture Named security, privacy, compliance, product, and operations approvers Sandbox evidence matching the intended production configuration Instructions Step 1: Freeze release inputs Record code SHA, API version, templates and versions, endpoint IDs, domains, environment, feature flags, and migration plan. Step 2: Verify access and privacy Prove least-privilege keys, secret rotation, PII minimization, retention, access logging, customer rights, redaction governance, and incident response. Step 3: Exercise identity paths Run synthetic pass, fail, retry, abandon, resume, unknown-verification, duplicate-customer, and manual-review scenarios. Step 4: Prove event reliability Verify raw-body HMAC, rotation candidates, duplicate delivery, out-of-order delivery, queue recovery, dead-letter replay, and GET reconciliation. Step 5: Test limits and failures Exercise 429 handling, product-quota exhaustion, provider timeout, ambiguous POST, dependency outage, and degraded manual path. Step 6: Approve release and rollback Require named approvals, deploy a narrow cohort, watch defined indicators, and demonstrate rollback without losing authoritative events or decisions. Authentication Production readiness requires production credentials to remain in the production secret boundary. Tests should prove bindings and permissions without exporting their values. Tool Discipline Use Read and Grep to inspect application configuration, provider documentation, fixtures, schemas, tests, and redacted operational evidence before proposing a change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/persona-prod-checklist