From lokalise-pack
Diagnose and fix Lokalise common errors and exceptions. Use when encountering Lokalise errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "lokalise error", "fix lokalise", "lokalise not working", "debug lokalise", "lokalise 401", "lokalise 429".
How this skill is triggered — by the user, by Claude, or both
Slash command
/lokalise-pack:lokalise-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
Quick reference for the most common Lokalise API errors and their solutions.
Quick reference for the most common Lokalise API errors and their solutions.
For full implementation details, load: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Error | Solution |
|---|---|
| 401 Unauthorized - Invalid API Token | See implementation guide |
| 403 Forbidden - Insufficient Permissions | See implementation guide |
| 404 Not Found - Resource Missing | See implementation guide |
| 429 Too Many Requests - Rate Limited | See implementation guide |
| 400 Bad Request - Invalid Parameters | See implementation guide |
| 400 Key Limit Exceeded | See implementation guide |
| 413 Payload Too Large | See implementation guide |
| Upload Process Failed | See implementation guide |
For comprehensive debugging, see lokalise-debug-bundle.
See debugging implementation details for output format specifications.
Basic usage: Apply lokalise common errors to a standard project setup with default configuration options.
Advanced scenario: Customize lokalise common errors for production environments with multiple constraints and team-specific requirements.
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.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin lokalise-pack