Agent skill · operations · jeremylongshore
lokalise-incident-runbook
Execute Lokalise incident response procedures with triage, mitigation,
Why this skill is useful
Adds executable scripts for rapid diagnostics and incident response procedures specific to Lokalise outages that aren't publicly documented.
What it needs
Requires curl, jq installed locally. Requires lokalise account access. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lokalise Incident Runbook Overview Rapid-response procedures for Lokalise-related incidents in production. Covers quick diagnostics (API health, token validity, rate limit status), triage for five common failure modes (missing translations, stale translations, API outage, file upload failures, OTA failures), fallback to cached translations, and communication templates for stakeholder notification. Designed to be executed under pressure — each section is self-contained. Prerequisites curl and jq available on the responder's machine Production Lokalise API token accessible (from secret manager or break-glass procedure) LOKALISEPROJECTID known (check your deployment config or Lokalise dashboard) Access to application logs (Datadog, CloudWatch, GCP Logging, or equivalent) Incident communication channel (Slack, PagerDuty, or equivalent) Instructions Step 1: Quick Diagnostics (Run First) Execute these three checks immediately to narrow the problem scope. Copy-paste into your terminal: Step 2: Triage Decision Tree Based on the diagnostics above, follow the appropriate path: Symptom Diagnostics Result Go To --------- ------------------- ------- Users see English instead of their language API healthy, token valid Triage A: Missing Translations Users see outdated translations API healthy, token valid Triage B: Stale Translations All translations fail to load API returns 5xx Triage C: API Outage CI upload fails API returns 4xx on upload Triage D: File Upload Failures App works but new keys show raw key names API healthy, keys exist in Lokalise Triage A: Missing Translations Triage A: Missing Translations in Production Likely causes: New keys deployed before translations were uploaded, download step skipped in CI, locale file not included in build. Triage B: Stale Translations Likely causes: Cache not invalidated, OTA bundle not refreshed, CI downloaded from wrong branch or old snapshot. Triage C: API Outage When Lokalise API returns 5xx or is unreachable. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lokalise-incident-runbook--7d5347