Agent skill · writing content · jeremylongshore
persona-core-workflow-b
Interpret Persona verification resources without collapsing provider evidence into an automatic business decision. Use when mapping checks to review outcomes. Trigger with: "evaluate Persona verification", "map KYC result", "handle Persona checks".
Why this skill is useful
Provides specific API commands and workflows for handling Persona verification types 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 Verification Evidence and Decision Boundary Overview Separate Persona verification lifecycle evidence from the application’s approve, reject, or review decision. Government ID, phone, selfie, document, and database verification types can evolve; the integration must tolerate unfamiliar types and values. Prerequisites Inquiry ID with authorized access Versioned business decision policy and manual-review owner PII-minimized mapping for needed verification attributes Instructions Step 1: Read authoritative resources Fetch the inquiry and related verification resources under the pinned API version. Record IDs, types, statuses, checks, and timestamps without copying unnecessary PII. Step 2: Validate completeness Determine which verification types the template and policy require. Missing evidence is unknown or incomplete, not a silent pass. Step 3: Normalize conservatively Map known provider states to internal evidence states and preserve unknown types or values for review. Never fabricate check enums. Step 4: Apply the policy boundary Evaluate provider evidence through the versioned internal policy. Record the policy version and reasons independently of Persona’s status. Step 5: Handle later changes Accept verified webhook updates and reconcile the resource before changing the decision. Guard terminal decisions against stale or out-of-order events. Step 6: Produce an auditable receipt Retain resource IDs, redacted evidence facts, event IDs, policy version, decision, reviewer, and appeal or retry route. Authentication Use a service bearer key limited to the correct Persona environment. Authorization to retrieve a verification does not authorize broad storage or display of its PII. 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-b