Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lokalise-common-errors
Diagnose and fix Lokalise common errors and exceptions.
Passed 17 of 22 test cases with the skill, and 9 of 22 without it.
and 9 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our Node SDK error handling wrapper, when an operation throws a 401 Unauthorized status, we want to output an actionable error message directing developers to where they can regenerate their token. What specific URL should be included in the error message?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the URL https://app.lokalise.com/profile#apitokens in the error message | Missed | Passed |
The instructions your model reads when the skill loads.
Every Lokalise API error returns a JSON body with a consistent structure. This skill covers the error response format, diagnosis of each HTTP status code (401, 400, 404, 429, 413, 500, 503), diagnostic curl commands for rapid troubleshooting, and a reusable error handling wrapper for the Node SDK.
curl available for diagnostic commands@lokalise/node-api SDK installed for the error wrapperLOKALISE_API_TOKEN environment variablejq installed for parsing JSON responses (optional but recommended)All Lokalise API errors return this structure:
{
"error": {
"message": "Human-readable error description",
"code": 401
}
}
The code field mirrors the HTTP status code. The message field provides specifics. When using the Node SDK, errors are thrown as exceptions with error.code, error.message, and error.headers properties.
{"error": {"message": "Invalid `X-Api-Token` header", "code": 401}}
Causes:
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.