Agent skill · software engineering · jeremylongshore
persona-core-workflow-a
Operate the account-linked Persona inquiry and session lifecycle from creation through safe resume. Use when implementing a customer verification journey. Trigger with: "create Persona inquiry", "resume Persona inquiry", "link Persona account".
Why this skill is useful
Adds a complete KYC verification flow with executable backend and frontend code specific to the Persona API, which the AI wouldn't generate on its own.
What it needs
Requires npm installed locally. Requires persona account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Account-Linked Persona Inquiry and Session Lifecycle Overview Model the inquiry as a durable server-side workflow. Link the customer reference during supported account auto-creation, issue sessions only when a client needs one, and never assume resuming is harmless or unlimited. Prerequisites Approved inquiry template and account-linkage policy Durable mapping from internal subject to Persona account and inquiry IDs Session-token delivery and expiration controls Instructions Step 1: Resolve the subject Look up the internal subject and existing Persona account or active inquiry. Prevent concurrent duplicate creates with a subject-scoped operation lock. Step 2: Create the inquiry POST with one template selector, meta.auto-create-account-reference-id when needed, and a durable idempotency key. Optionally request an initial inquiry session. Step 3: Deliver the session safely Read meta['session-token'], bind it to the intended subject and client, redact it from logs, and apply an application-side expiration and single-delivery policy. Step 4: Observe lifecycle events Use verified webhooks as the primary signal and GET reconciliation as a recovery path. Persist Persona event IDs and creation times. Step 5: Resume only on demand For an eligible pending inquiry, call /inquiries/:id/resume and read meta.session-token. Avoid eager resume because an inquiry has a default maximum of 25 sessions. Step 6: Close the domain decision Map observed inquiry and verification evidence into a separately reviewed business decision. Keep retry, manual review, and terminal states explicit. Authentication Server-side lifecycle calls use the environment bearer key and dated API version. Inquiry session tokens are short-lived client capabilities and must not be treated as API keys or logged. 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-core-workflow-a--8c6b1c