From persona-pack
Optimizes Persona identity verification costs via template selection, caching, and duplicate avoidance. Use for KYC API integrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/persona-pack:persona-cost-tuningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Choose appropriate verification types, cache results, avoid duplicate inquiries.
Choose appropriate verification types, cache results, avoid duplicate inquiries.
persona-install-auth setupimport os, requests
HEADERS = {
"Authorization": f"Bearer {os.environ['PERSONA_API_KEY']}",
"Persona-Version": "2023-01-05",
}
BASE = "https://withpersona.com/api/v1"
# Optimize Persona verification costs with template selection and caching
resp = requests.get(f"{BASE}/inquiries?page[size]=10", headers=HEADERS)
resp.raise_for_status()
inquiries = resp.json()["data"]
for inq in inquiries:
print(f" {inq['id']}: {inq['attributes']['status']}")
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Invalid API key | Check PERSONA_API_KEY |
| 429 Rate Limited | Too many requests | Implement backoff |
| 404 Not Found | Wrong resource ID | Verify ID format |
See related Persona skills for more workflows.
npx claudepluginhub fleet-to-force/claude-code-plugins-plus --plugin persona-pack5plugins reuse this skill
First indexed Jul 10, 2026
Optimizes Persona identity verification costs by selecting appropriate templates, caching results, and avoiding duplicate inquiries.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.