Agent skill · data analytics · jeremylongshore
lokalise-common-errors
Diagnose and fix Lokalise common errors and exceptions.
Why this skill is useful
Provides specific diagnostic curl commands and error handling patterns for the Lokalise API that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires lokalise account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Common Errors Overview 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. Prerequisites curl available for diagnostic commands @lokalise/node-api SDK installed for the error wrapper API token stored in LOKALISEAPITOKEN environment variable jq installed for parsing JSON responses (optional but recommended) Instructions 1. Understand the Error Response Format All Lokalise API errors return this structure: 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. 2. Diagnose by Status Code 401 Unauthorized — Invalid or Missing API Token Causes: Token is incorrect, expired, or revoked X-Api-Token header missing from request Token copied with leading/trailing whitespace Fix: 400 Bad Request — Validation Errors Common 400 causes: Invalid projectid format (must be {number}.{alphanumeric}) Missing required fields in POST/PUT body Invalid language ISO code Key name exceeding 256 characters Invalid platform value (must be ios, android, web, or other) Fix: 404 Not Found — Resource Does Not Exist Causes: Project ID is wrong or project was deleted Key, translation, or webhook ID does not exist Token lacks access to the specified project (appears as 404, not 403) Fix: 429 Too Many Requests — Rate Limited The response includes a Retry-After header indicating seconds to wait. Fix: See lokalise-rate-limits skill for full implementation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-common-errors