Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/klaviyo-common-errors
Diagnose and fix common Klaviyo API errors and exceptions.
Passed 22 of 25 test cases with the skill, and 12 of 25 without it.
and 9 more in the full report
11 fixed11 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our API requests keep failing with 401 Unauthorized errors even after setting the private key environment variable. What bash command inspects the first 3 characters of the key variable without outputting the full key?
| Checked | Without skill | With skill |
|---|---|---|
| Provides the command echo $KLAVIYO_PRIVATE_KEY | head -c 3 | Missed | Passed |
The instructions your model reads when the skill loads.
Quick reference for the most common Klaviyo API errors with real error payloads,
root causes, and solutions. Because Klaviyo returns JSON:API errors (a status
code plus a structured errors[] array), this skill walks you from a raw
exception to a targeted fix: extract the status code, match it against the
catalog, apply the documented remedy.
The full per-status-code catalog and the SDK-level failure table live in
references/ to keep this workflow scannable — drill in once you know which
status code you are chasing.
klaviyo-api SDK installed (npm install klaviyo-api — note: not @klaviyo/sdk)pk_*) exported as KLAVIYO_PRIVATE_KEYRead the stack trace and Grep for the status code and error codeExtract the status code and error detail from the caught exception. Read the
log line or wrap the call so the structured payload is visible:
try {
await profilesApi.createProfile(payload);
} catch (error: any) {
console.error('Status:', error.status);
console.error('Errors:', JSON.stringify(error.body?.errors, null, 2));
// error.body.errors[] has: { id, code, title, detail, source }
}
If you only have raw logs, Grep for the status code (grep -E "40[0-9]|429|50[0-9]")
and the code field to isolate the failing request.
test cases passed, vs 12 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.