From clari-pack
Diagnoses and fixes Clari API errors like auth failures, empty exports, job timeouts, and UI data mismatches. Supplies curl commands to test keys, list forecasts, and verify data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/clari-pack:clari-common-errorsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Diagnostic guide for the most common Clari API issues: authentication failures, empty exports, job timeouts, and data discrepancies.
Diagnostic guide for the most common Clari API issues: authentication failures, empty exports, job timeouts, and data discrepancies.
{"error": "Unauthorized", "message": "Invalid API key"}
Fix: Regenerate token at Clari > User Settings > API Token. Tokens may expire or be revoked by admins.
{"error": "Forbidden", "message": "API access not enabled for this user"}
Fix: Contact your Clari admin to enable API access. Requires enterprise plan.
{"error": "Not Found", "message": "Forecast 'wrong_name' not found"}
Fix: List available forecasts first:
curl -s -H "apikey: ${CLARI_API_KEY}" \
https://api.clari.com/v4/export/forecast/list | jq '.forecasts[].forecastName'
The API returns {"entries": []} with no error.
Causes:
Fix: Verify in Clari UI that the forecast has submissions for the requested period.
Export job never reaches COMPLETED status.
Causes:
Fix: Increase polling timeout. Break large exports into per-period batches.
Forecast numbers from API do not match what is shown in Clari UI.
Causes:
Fix: Use includeHistorical: true to get all submission versions. Match the exact time period label from the UI.
{"error": "invalid_client"}
Fix: The Copilot API uses OAuth2, not API key auth. Register your app at https://api-doc.copilot.clari.com and use client credentials flow.
HTTP 429 Too Many Requests
Fix: Implement exponential backoff. See clari-rate-limits for patterns.
# Test API key
curl -s -o /dev/null -w "%{http_code}" \
-H "apikey: ${CLARI_API_KEY}" \
https://api.clari.com/v4/export/forecast/list
# List all forecasts
curl -s -H "apikey: ${CLARI_API_KEY}" \
https://api.clari.com/v4/export/forecast/list | jq .
# Check running jobs
curl -s -H "apikey: ${CLARI_API_KEY}" \
https://api.clari.com/v4/export/jobs | jq '.jobs[] | {jobId, status, createdAt}'
For comprehensive diagnostics, see clari-debug-bundle.
5plugins reuse this skill
First indexed Jul 10, 2026
npx claudepluginhub ia23a-lachnita/claude-code-plugins-plus-fix-skills --plugin clari-packDiagnose and fix Clari API errors including auth failures, export issues, and data mismatches. Use when Clari API calls fail, exports return empty data, or forecast numbers do not match the UI. Trigger with phrases like "clari error", "clari not working", "clari api failure", "fix clari", "debug clari".
Diagnose and fix common Klaviyo API errors and exceptions. Use when encountering Klaviyo 4xx/5xx errors, debugging failed requests, or troubleshooting SDK integration issues. Trigger with phrases like "klaviyo error", "fix klaviyo", "klaviyo not working", "debug klaviyo", "klaviyo 400", "klaviyo 429".
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.