[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792XG58CBXK2FG2MTJXG6CY":3,"skill-same:01M792XG58CBXK2FG2MTJXG6CY":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M792XG58CBXK2FG2MTJXG6CY","lokalise-incident-runbook",null,"Execute Lokalise incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Lokalise-related outages, investigating errors,\nor running post-incident reviews for Lokalise integration failures.\nTrigger with phrases like \"lokalise incident\", \"lokalise outage\",\n\"lokalise down\", \"lokalise on-call\", \"lokalise emergency\", \"translations broken\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lokalise-pack--lokalise-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lokalise-incident-runbook\ndescription: |\n  Execute Lokalise incident response procedures with triage, mitigation, and postmortem.\n  Use when responding to Lokalise-related outages, investigating errors,\n  or running post-incident reviews for Lokalise integration failures.\n  Trigger with phrases like \"lokalise incident\", \"lokalise outage\",\n  \"lokalise down\", \"lokalise on-call\", \"lokalise emergency\", \"translations broken\".\nallowed-tools: Read, Grep, Bash(curl:*), Bash(lokalise2:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, lokalise, incident-response]\n---\n# Lokalise Incident Runbook\n\n## Overview\n\nRapid-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.\n\n## Prerequisites\n\n- `curl` and `jq` available on the responder's machine\n- Production Lokalise API token accessible (from secret manager or break-glass procedure)\n- `LOKALISE_PROJECT_ID` known (check your deployment config or Lokalise dashboard)\n- Access to application logs (Datadog, CloudWatch, GCP Logging, or equivalent)\n- Incident communication channel (Slack, PagerDuty, or equivalent)\n\n## Instructions\n\n### Step 1: Quick Diagnostics (Run First)\n\nExecute these three checks immediately to narrow the problem scope. Copy-paste into your terminal:\n\n```bash\n#!\u002Fbin\u002Fbash\n# incident-diagnostics.sh — Run all three checks in sequence\nset -uo pipefail\n\n: \"${LOKALISE_API_TOKEN:?Set LOKALISE_API_TOKEN before running diagnostics}\"\n: \"${LOKALISE_PROJECT_ID:?Set LOKALISE_PROJECT_ID before running diagnostics}\"\n\necho \"=== 1. Lokalise API Health ===\"\nAPI_STATUS=$(curl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\")\n\ncase \"$API_STATUS\" in\n  200) echo \"API: HEALTHY (200 OK)\" ;;\n  401) echo \"API: AUTH FAILURE (401) — Token invalid or expired. Rotate immediately.\" ;;\n  403) echo \"API: FORBIDDEN (403) — Token lacks permissions for this project.\" ;;\n  404) echo \"API: NOT FOUND (404) — Check LOKALISE_PROJECT_ID value.\" ;;\n  429) echo \"API: RATE LIMITED (429) — Throttled. Wait 10 seconds and retry.\" ;;\n  5*)  echo \"API: LOKALISE OUTAGE (${API_STATUS}) — Check https:\u002F\u002Fstatus.lokalise.com\" ;;\n  000) echo \"API: UNREACHABLE — DNS\u002Fnetwork issue. Check connectivity.\" ;;\n  *)   echo \"API: UNEXPECTED (${API_STATUS}) — Investigate further.\" ;;\nesac\n\necho \"\"\necho \"=== 2. Token Validity ===\"\nTOKEN_CHECK=$(curl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" 2>\u002Fdev\u002Fnull)\n\nif [[ $? -eq 0 ]]; then\n  PROJECT_NAME=$(echo \"$TOKEN_CHECK\" | jq -r '.project.name')\n  TEAM_ID=$(echo \"$TOKEN_CHECK\" | jq -r '.project.team_id')\n  echo \"Token: VALID\"\n  echo \"  Project: ${PROJECT_NAME}\"\n  echo \"  Team ID: ${TEAM_ID}\"\nelse\n  echo \"Token: INVALID or project inaccessible\"\n  echo \"  Action: Get a valid token from your secret manager or Lokalise dashboard\"\nfi\n\necho \"\"\necho \"=== 3. Rate Limit Status ===\"\nRATE_RESPONSE=$(curl -sI \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\u002Fkeys?limit=1\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" 2>\u002Fdev\u002Fnull)\n\nRATE_LIMIT=$(echo \"$RATE_RESPONSE\" | grep -i \"x-ratelimit-limit\" | tr -d '\\r' | awk '{print $2}')\nRATE_REMAINING=$(echo \"$RATE_RESPONSE\" | grep -i \"x-ratelimit-remaining\" | tr -d '\\r' | awk '{print $2}')\n\nif [[ -n \"$RATE_REMAINING\" ]]; then\n  echo \"Rate limit:     ${RATE_LIMIT:-6} req\u002Fsec\"\n  echo \"Remaining:      ${RATE_REMAINING} req\u002Fsec\"\n  if [[ \"${RATE_REMAINING}\" -eq 0 ]]; then\n    echo \"STATUS: EXHAUSTED — Wait 1 second for reset\"\n  else\n    echo \"STATUS: OK\"\n  fi\nelse\n  echo \"Could not determine rate limit status\"\nfi\n```\n\n### Step 2: Triage Decision Tree\n\nBased on the diagnostics above, follow the appropriate path:\n\n| Symptom | Diagnostics Result | Go To |\n|---------|-------------------|-------|\n| Users see English instead of their language | API healthy, token valid | **Triage A: Missing Translations** |\n| Users see outdated translations | API healthy, token valid | **Triage B: Stale Translations** |\n| All translations fail to load | API returns 5xx | **Triage C: API Outage** |\n| CI upload fails | API returns 4xx on upload | **Triage D: File Upload Failures** |\n| App works but new keys show raw key names | API healthy, keys exist in Lokalise | **Triage A: Missing Translations** |\n\n### Triage A: Missing Translations in Production\n\n**Likely causes:** New keys deployed before translations were uploaded, download step skipped in CI, locale file not included in build.\n\n```bash\n# 1. Check if the key exists in Lokalise\nKEY_NAME=\"homepage.welcome_message\"  # Replace with the missing key\ncurl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\u002Fkeys?filter_keys=${KEY_NAME}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  | jq '.keys[] | {key_name: .key_name.web, translations: [.translations[] | {locale: .language_iso, value: .translation}]}'\n\n# 2. Check if the locale file was included in the deployed build\n# (run on the production server or check the build artifact)\nls -la \u002Fapp\u002Flocales\u002F  # Adjust path to your deployed locale directory\ncat \u002Fapp\u002Flocales\u002Fde.json | jq \".$KEY_NAME\" 2>\u002Fdev\u002Fnull || echo \"Key not found in deployed file\"\n\n# 3. Quick fix: Re-download and redeploy\nlokalise2 file download \\\n  --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  --format json \\\n  --original-filenames=true \\\n  --directory-prefix=\"\" \\\n  --export-empty-as=base \\\n  --unzip-to \"src\u002Flocales\u002F\"\n# Then trigger a redeploy\n```\n\n### Triage B: Stale Translations\n\n**Likely causes:** Cache not invalidated, OTA bundle not refreshed, CI downloaded from wrong branch or old snapshot.\n\n```bash\n# 1. Compare Lokalise timestamp with deployed file\nLOKALISE_UPDATED=$(curl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  | jq -r '.project.statistics.datetime')\necho \"Lokalise last updated: $LOKALISE_UPDATED\"\n\n# 2. Check when your deployed translations were built\nstat src\u002Flocales\u002Fen.json  # File modification time\n\n# 3. Force cache invalidation if using OTA\n# For i18next-http-backend or similar:\n# Clear the browser\u002Fapp cache or increment the version query parameter\n\n# 4. Re-download fresh translations\nlokalise2 file download \\\n  --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  --format json \\\n  --original-filenames=true \\\n  --directory-prefix=\"\" \\\n  --unzip-to \"src\u002Flocales\u002F\"\n```\n\n### Triage C: API Outage\n\n**When Lokalise API returns 5xx or is unreachable.**\n\n```bash\n# 1. Confirm on status page\necho \"Check: https:\u002F\u002Fstatus.lokalise.com\"\ncurl -sf \"https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fsummary.json\" 2>\u002Fdev\u002Fnull \\\n  | jq '.status.description' || echo \"Status page unreachable\"\n\n# 2. Enable fallback translations\n# Your app should have a fallback mechanism. If not, deploy one immediately:\n```\n\n```typescript\n\u002F\u002F Emergency fallback implementation\n\u002F\u002F Add to your translation loader\n\nimport bundledTranslations from '.\u002Flocales\u002Fen.json';\n\nasync function loadTranslations(locale: string): Promise\u003CRecord\u003Cstring, string>> {\n  try {\n    \u002F\u002F Try loading from Lokalise\u002FCDN\u002FAPI\n    const response = await fetch(`\u002Fapi\u002Ftranslations\u002F${locale}`, {\n      signal: AbortSignal.timeout(3000),  \u002F\u002F 3-second timeout\n    });\n    if (!response.ok) throw new Error(`HTTP ${response.status}`);\n    return await response.json();\n  } catch (error) {\n    console.error(`Translation fetch failed for ${locale}, using fallback:`, error);\n    \u002F\u002F Fall back to bundled English translations\n    return bundledTranslations;\n  }\n}\n```\n\n```bash\n# 3. If your app crashes without the API, set the env var to enable static fallback:\nexport LOKALISE_FALLBACK_ENABLED=true\n# Then restart the application\n\n# 4. Monitor for recovery\nwatch -n 30 'curl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\"'\n```\n\n### Triage D: File Upload Failures\n\n**When CI fails to upload source strings to Lokalise.**\n\n```bash\n# 1. Validate the source file locally\njq empty src\u002Flocales\u002Fen.json && echo \"Valid JSON\" || echo \"INVALID JSON — fix syntax\"\n\n# 2. Check file size (Lokalise limit: 50MB per file)\ndu -h src\u002Flocales\u002Fen.json\n\n# 3. Test upload with verbose output\nlokalise2 file upload \\\n  --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  --file \"src\u002Flocales\u002Fen.json\" \\\n  --lang-iso \"en\" \\\n  --replace-modified \\\n  --poll \\\n  --poll-timeout 120s 2>&1\n\n# 4. Common fixes:\n# - \"Unsupported file format\": Check file extension matches --format\n# - \"Key name too long\": Lokalise limit is 1024 chars per key\n# - \"Too many keys\": Split into multiple files if > 10,000 keys per upload\n# - 429 error: Wait and retry, or reduce upload frequency\n```\n\n### Step 3: Fallback to Cached Translations\n\nIf the Lokalise API is down and you need the app to keep running, use bundled translations.\n\n```typescript\n\u002F\u002F src\u002Fi18n\u002Ffallback-loader.ts\nimport fs from 'fs';\nimport path from 'path';\n\nconst CACHE_DIR = path.resolve(__dirname, '..\u002Flocales');\nconst FALLBACK_DIR = path.resolve(__dirname, '..\u002Flocales-fallback');\n\n\u002F**\n * Copy current translations to fallback directory.\n * Run this as a post-build step: `cp -r src\u002Flocales\u002F src\u002Flocales-fallback\u002F`\n *\u002F\nexport function loadWithFallback(locale: string): Record\u003Cstring, unknown> {\n  const primaryPath = path.join(CACHE_DIR, `${locale}.json`);\n  const fallbackPath = path.join(FALLBACK_DIR, `${locale}.json`);\n  const defaultPath = path.join(FALLBACK_DIR, 'en.json');\n\n  \u002F\u002F Try primary (freshly downloaded)\n  if (fs.existsSync(primaryPath)) {\n    try {\n      return JSON.parse(fs.readFileSync(primaryPath, 'utf-8'));\n    } catch { \u002F* fall through *\u002F }\n  }\n\n  \u002F\u002F Try locale-specific fallback\n  if (fs.existsSync(fallbackPath)) {\n    console.warn(`Using fallback translations for ${locale}`);\n    return JSON.parse(fs.readFileSync(fallbackPath, 'utf-8'));\n  }\n\n  \u002F\u002F Last resort: English fallback\n  console.error(`No translations available for ${locale}, falling back to English`);\n  return JSON.parse(fs.readFileSync(defaultPath, 'utf-8'));\n}\n```\n\n### Step 4: Communication Templates\n\n**Initial notification (post within 5 minutes of detection):**\n\n```\n[INCIDENT] Translation service degraded\nStatus: Investigating\nImpact: [Users in DE\u002FFR\u002FES\u002FJA locales may see English text | All translations unavailable]\nStart time: YYYY-MM-DD HH:MM UTC\nCause: [Lokalise API outage | Stale translation cache | Missing keys in deployment]\nNext update: 15 minutes\n```\n\n**Mitigation applied:**\n\n```\n[UPDATE] Translation service — Mitigation in progress\nStatus: Mitigating\nAction taken: [Enabled fallback translations | Redeployed with fresh downloads | Reverted to previous build]\nETA for full resolution: [30 minutes | Next deployment cycle | Pending Lokalise recovery]\n```\n\n**Resolved:**\n\n```\n[RESOLVED] Translation service restored\nDuration: X hours Y minutes\nRoot cause: [Brief description]\nImpact: [Number of affected users\u002Frequests]\nFollow-up: Postmortem scheduled for YYYY-MM-DD\n```\n\n### Step 5: Post-Incident Checklist\n\nAfter the incident is resolved:\n\n1. Verify all locales are loading correctly in production\n2. Check for any data loss (keys deleted or overwritten during incident)\n3. Review rate limit consumption during the incident\n4. Document the timeline in your incident tracker\n5. Schedule a postmortem with findings:\n   - What failed and why\n   - How it was detected (monitoring alert or user report?)\n   - Time to detection, time to mitigation, time to resolution\n   - What changes would prevent recurrence\n\n## Output\n\nAfter executing this runbook:\n- Root cause identified and documented\n- Immediate mitigation applied (fallback translations, redeployment, or cache clear)\n- Stakeholders notified via communication templates\n- Post-incident evidence collected for postmortem\n\n## Error Handling\n\n| Issue During Response | Cause | Solution |\n|----------------------|-------|----------|\n| Can't access Lokalise dashboard | Lokalise fully down | Use CLI with API token; check status.lokalise.com on mobile |\n| Token from secret manager fails | Secret manager also experiencing issues | Use break-glass procedure (documented token in secure vault) |\n| Fallback translations not present | Never set up fallback mechanism | Deploy English-only as emergency, then implement fallback |\n| App crashes on missing translations | No null-safe translation access | Hotfix: wrap translation calls in try-catch, return key name |\n| Rate limited during recovery | Too many API calls fixing the issue | Wait 1 second between requests; max 6 req\u002Fsec |\n| Git deploy blocked by CI | CI translation checks failing | Bypass with `[skip-translation-check]` in commit message (if configured) |\n\n## Examples\n\n### One-Line Health Check\n\n```bash\ncurl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  | jq '{name: .project.name, keys: .project.statistics.keys_total, progress: .project.statistics.progress_total}' \\\n  || echo \"UNHEALTHY — API unreachable or auth failed\"\n```\n\n### Application Health Endpoint\n\n```typescript\n\u002F\u002F GET \u002Fhealth\u002Ftranslations\nexport async function translationHealthCheck(): Promise\u003C{\n  status: 'healthy' | 'degraded' | 'unhealthy';\n  details: Record\u003Cstring, unknown>;\n}> {\n  const checks = {\n    api_reachable: false,\n    translations_loaded: false,\n    cache_fresh: false,\n  };\n\n  \u002F\u002F Check 1: Can we reach the Lokalise API?\n  try {\n    const res = await fetch(`https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${process.env.LOKALISE_PROJECT_ID}`, {\n      headers: { 'X-Api-Token': process.env.LOKALISE_API_TOKEN! },\n      signal: AbortSignal.timeout(5000),\n    });\n    checks.api_reachable = res.ok;\n  } catch { \u002F* timeout or network error *\u002F }\n\n  \u002F\u002F Check 2: Are translations loaded in memory?\n  checks.translations_loaded = Object.keys(i18next.store.data).length > 0;\n\n  \u002F\u002F Check 3: Is the cache fresh (less than 1 hour old)?\n  const cacheAge = Date.now() - (globalThis.__translationCacheTimestamp ?? 0);\n  checks.cache_fresh = cacheAge \u003C 3600_000;\n\n  const allHealthy = Object.values(checks).every(Boolean);\n  const anyHealthy = Object.values(checks).some(Boolean);\n\n  return {\n    status: allHealthy ? 'healthy' : anyHealthy ? 'degraded' : 'unhealthy',\n    details: checks,\n  };\n}\n```\n\n## Resources\n\n- [Lokalise Status Page](https:\u002F\u002Fstatus.lokalise.com) — First thing to check during an outage\n- [Lokalise API Rate Limits](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Fapi-rate-limits)\n- [Lokalise API Error Codes](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Ferrors)\n- [Lokalise Support](mailto:support@lokalise.com) — For P1 issues, also try the in-app chat\n- [Lokalise Community Forum](https:\u002F\u002Fcommunity.lokalise.com)\n\n## Next Steps\n\n- After resolving the incident, run `lokalise-prod-checklist` to verify the system is fully healthy\n- Implement the health endpoint from the examples if you do not already have one\n- Set up automated alerting on the health endpoint (Datadog, PagerDuty, or equivalent)\n- Add the fallback translation mechanism to prevent full outage on future API issues\n","# Lokalise Incident Runbook\n\n## Overview\n\nRapid-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.\n\n## Prerequisites\n\n- `curl` and `jq` available on the responder's machine\n- Production Lokalise API token accessible (from secret manager or break-glass procedure)\n- `LOKALISE_PROJECT_ID` known (check your deployment config or Lokalise dashboard)\n- Access to application logs (Datadog, CloudWatch, GCP Logging, or equivalent)\n- Incident communication channel (Slack, PagerDuty, or equivalent)\n\n## Instructions\n\n### Step 1: Quick Diagnostics (Run First)\n\nExecute these three checks immediately to narrow the problem scope. Copy-paste into your terminal:\n\n```bash\n#!\u002Fbin\u002Fbash\n# incident-diagnostics.sh — Run all three checks in sequence\nset -uo pipefail\n\n: \"${LOKALISE_API_TOKEN:?Set LOKALISE_API_TOKEN before running diagnostics}\"\n: \"${LOKALISE_PROJECT_ID:?Set LOKALISE_PROJECT_ID before running diagnostics}\"\n\necho \"=== 1. Lokalise API Health ===\"\nAPI_STATUS=$(curl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\")\n\ncase \"$API_STATUS\" in\n  200) echo \"API: HEALTHY (200 OK)\" ;;\n  401) echo \"API: AUTH FAILURE (401) — Token invalid or expired. Rotate immediately.\" ;;\n  403) echo \"API: FORBIDDEN (403) — Token lacks permissions for this project.\" ;;\n  404) echo \"API: NOT FOUND (404) — Check LOKALISE_PROJECT_ID value.\" ;;\n  429) echo \"API: RATE LIMITED (429) — Throttled. Wait 10 seconds and retry.\" ;;\n  5*)  echo \"API: LOKALISE OUTAGE (${API_STATUS}) — Check https:\u002F\u002Fstatus.lokalise.com\" ;;\n  000) echo \"API: UNREACHABLE — DNS\u002Fnetwork issue. Check connectivity.\" ;;\n  *)   echo \"API: UNEXPECTED (${API_STATUS}) — Investigate further.\" ;;\nesac\n\necho \"\"\necho \"=== 2. Token Validity ===\"\nTOKEN_CHECK=$(curl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" 2>\u002Fdev\u002Fnull)\n\nif [[ $? -eq 0 ]]; then\n  PROJECT_NAME=$(echo \"$TOKEN_CHECK\" | jq -r '.project.name')\n  TEAM_ID=$(echo \"$TOKEN_CHECK\" | jq -r '.project.team_id')\n  echo \"Token: VALID\"\n  echo \"  Project: ${PROJECT_NAME}\"\n  echo \"  Team ID: ${TEAM_ID}\"\nelse\n  echo \"Token: INVALID or project inaccessible\"\n  echo \"  Action: Get a valid token from your secret manager or Lokalise dashboard\"\nfi\n\necho \"\"\necho \"=== 3. Rate Limit Status ===\"\nRATE_RESPONSE=$(curl -sI \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\u002Fkeys?limit=1\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" 2>\u002Fdev\u002Fnull)\n\nRATE_LIMIT=$(echo \"$RATE_RESPONSE\" | grep -i \"x-ratelimit-limit\" | tr -d '\\r' | awk '{print $2}')\nRATE_REMAINING=$(echo \"$RATE_RESPONSE\" | grep -i \"x-ratelimit-remaining\" | tr -d '\\r' | awk '{print $2}')\n\nif [[ -n \"$RATE_REMAINING\" ]]; then\n  echo \"Rate limit:     ${RATE_LIMIT:-6} req\u002Fsec\"\n  echo \"Remaining:      ${RATE_REMAINING} req\u002Fsec\"\n  if [[ \"${RATE_REMAINING}\" -eq 0 ]]; then\n    echo \"STATUS: EXHAUSTED — Wait 1 second for reset\"\n  else\n    echo \"STATUS: OK\"\n  fi\nelse\n  echo \"Could not determine rate limit status\"\nfi\n```\n\n### Step 2: Triage Decision Tree\n\nBased on the diagnostics above, follow the appropriate path:\n\n| Symptom | Diagnostics Result | Go To |\n|---------|-------------------|-------|\n| Users see English instead of their language | API healthy, token valid | **Triage A: Missing Translations** |\n| Users see outdated translations | API healthy, token valid | **Triage B: Stale Translations** |\n| All translations fail to load | API returns 5xx | **Triage C: API Outage** |\n| CI upload fails | API returns 4xx on upload | **Triage D: File Upload Failures** |\n| App works but new keys show raw key names | API healthy, keys exist in Lokalise | **Triage A: Missing Translations** |\n\n### Triage A: Missing Translations in Production\n\n**Likely causes:** New keys deployed before translations were uploaded, download step skipped in CI, locale file not included in build.\n\n```bash\n# 1. Check if the key exists in Lokalise\nKEY_NAME=\"homepage.welcome_message\"  # Replace with the missing key\ncurl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\u002Fkeys?filter_keys=${KEY_NAME}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  | jq '.keys[] | {key_name: .key_name.web, translations: [.translations[] | {locale: .language_iso, value: .translation}]}'\n\n# 2. Check if the locale file was included in the deployed build\n# (run on the production server or check the build artifact)\nls -la \u002Fapp\u002Flocales\u002F  # Adjust path to your deployed locale directory\ncat \u002Fapp\u002Flocales\u002Fde.json | jq \".$KEY_NAME\" 2>\u002Fdev\u002Fnull || echo \"Key not found in deployed file\"\n\n# 3. Quick fix: Re-download and redeploy\nlokalise2 file download \\\n  --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  --format json \\\n  --original-filenames=true \\\n  --directory-prefix=\"\" \\\n  --export-empty-as=base \\\n  --unzip-to \"src\u002Flocales\u002F\"\n# Then trigger a redeploy\n```\n\n### Triage B: Stale Translations\n\n**Likely causes:** Cache not invalidated, OTA bundle not refreshed, CI downloaded from wrong branch or old snapshot.\n\n```bash\n# 1. Compare Lokalise timestamp with deployed file\nLOKALISE_UPDATED=$(curl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  | jq -r '.project.statistics.datetime')\necho \"Lokalise last updated: $LOKALISE_UPDATED\"\n\n# 2. Check when your deployed translations were built\nstat src\u002Flocales\u002Fen.json  # File modification time\n\n# 3. Force cache invalidation if using OTA\n# For i18next-http-backend or similar:\n# Clear the browser\u002Fapp cache or increment the version query parameter\n\n# 4. Re-download fresh translations\nlokalise2 file download \\\n  --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  --format json \\\n  --original-filenames=true \\\n  --directory-prefix=\"\" \\\n  --unzip-to \"src\u002Flocales\u002F\"\n```\n\n### Triage C: API Outage\n\n**When Lokalise API returns 5xx or is unreachable.**\n\n```bash\n# 1. Confirm on status page\necho \"Check: https:\u002F\u002Fstatus.lokalise.com\"\ncurl -sf \"https:\u002F\u002Fstatus.lokalise.com\u002Fapi\u002Fv2\u002Fsummary.json\" 2>\u002Fdev\u002Fnull \\\n  | jq '.status.description' || echo \"Status page unreachable\"\n\n# 2. Enable fallback translations\n# Your app should have a fallback mechanism. If not, deploy one immediately:\n```\n\n```typescript\n\u002F\u002F Emergency fallback implementation\n\u002F\u002F Add to your translation loader\n\nimport bundledTranslations from '.\u002Flocales\u002Fen.json';\n\nasync function loadTranslations(locale: string): Promise\u003CRecord\u003Cstring, string>> {\n  try {\n    \u002F\u002F Try loading from Lokalise\u002FCDN\u002FAPI\n    const response = await fetch(`\u002Fapi\u002Ftranslations\u002F${locale}`, {\n      signal: AbortSignal.timeout(3000),  \u002F\u002F 3-second timeout\n    });\n    if (!response.ok) throw new Error(`HTTP ${response.status}`);\n    return await response.json();\n  } catch (error) {\n    console.error(`Translation fetch failed for ${locale}, using fallback:`, error);\n    \u002F\u002F Fall back to bundled English translations\n    return bundledTranslations;\n  }\n}\n```\n\n```bash\n# 3. If your app crashes without the API, set the env var to enable static fallback:\nexport LOKALISE_FALLBACK_ENABLED=true\n# Then restart the application\n\n# 4. Monitor for recovery\nwatch -n 30 'curl -sf -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\"'\n```\n\n### Triage D: File Upload Failures\n\n**When CI fails to upload source strings to Lokalise.**\n\n```bash\n# 1. Validate the source file locally\njq empty src\u002Flocales\u002Fen.json && echo \"Valid JSON\" || echo \"INVALID JSON — fix syntax\"\n\n# 2. Check file size (Lokalise limit: 50MB per file)\ndu -h src\u002Flocales\u002Fen.json\n\n# 3. Test upload with verbose output\nlokalise2 file upload \\\n  --token \"$LOKALISE_API_TOKEN\" \\\n  --project-id \"$LOKALISE_PROJECT_ID\" \\\n  --file \"src\u002Flocales\u002Fen.json\" \\\n  --lang-iso \"en\" \\\n  --replace-modified \\\n  --poll \\\n  --poll-timeout 120s 2>&1\n\n# 4. Common fixes:\n# - \"Unsupported file format\": Check file extension matches --format\n# - \"Key name too long\": Lokalise limit is 1024 chars per key\n# - \"Too many keys\": Split into multiple files if > 10,000 keys per upload\n# - 429 error: Wait and retry, or reduce upload frequency\n```\n\n### Step 3: Fallback to Cached Translations\n\nIf the Lokalise API is down and you need the app to keep running, use bundled translations.\n\n```typescript\n\u002F\u002F src\u002Fi18n\u002Ffallback-loader.ts\nimport fs from 'fs';\nimport path from 'path';\n\nconst CACHE_DIR = path.resolve(__dirname, '..\u002Flocales');\nconst FALLBACK_DIR = path.resolve(__dirname, '..\u002Flocales-fallback');\n\n\u002F**\n * Copy current translations to fallback directory.\n * Run this as a post-build step: `cp -r src\u002Flocales\u002F src\u002Flocales-fallback\u002F`\n *\u002F\nexport function loadWithFallback(locale: string): Record\u003Cstring, unknown> {\n  const primaryPath = path.join(CACHE_DIR, `${locale}.json`);\n  const fallbackPath = path.join(FALLBACK_DIR, `${locale}.json`);\n  const defaultPath = path.join(FALLBACK_DIR, 'en.json');\n\n  \u002F\u002F Try primary (freshly downloaded)\n  if (fs.existsSync(primaryPath)) {\n    try {\n      return JSON.parse(fs.readFileSync(primaryPath, 'utf-8'));\n    } catch { \u002F* fall through *\u002F }\n  }\n\n  \u002F\u002F Try locale-specific fallback\n  if (fs.existsSync(fallbackPath)) {\n    console.warn(`Using fallback translations for ${locale}`);\n    return JSON.parse(fs.readFileSync(fallbackPath, 'utf-8'));\n  }\n\n  \u002F\u002F Last resort: English fallback\n  console.error(`No translations available for ${locale}, falling back to English`);\n  return JSON.parse(fs.readFileSync(defaultPath, 'utf-8'));\n}\n```\n\n### Step 4: Communication Templates\n\n**Initial notification (post within 5 minutes of detection):**\n\n```\n[INCIDENT] Translation service degraded\nStatus: Investigating\nImpact: [Users in DE\u002FFR\u002FES\u002FJA locales may see English text | All translations unavailable]\nStart time: YYYY-MM-DD HH:MM UTC\nCause: [Lokalise API outage | Stale translation cache | Missing keys in deployment]\nNext update: 15 minutes\n```\n\n**Mitigation applied:**\n\n```\n[UPDATE] Translation service — Mitigation in progress\nStatus: Mitigating\nAction taken: [Enabled fallback translations | Redeployed with fresh downloads | Reverted to previous build]\nETA for full resolution: [30 minutes | Next deployment cycle | Pending Lokalise recovery]\n```\n\n**Resolved:**\n\n```\n[RESOLVED] Translation service restored\nDuration: X hours Y minutes\nRoot cause: [Brief description]\nImpact: [Number of affected users\u002Frequests]\nFollow-up: Postmortem scheduled for YYYY-MM-DD\n```\n\n### Step 5: Post-Incident Checklist\n\nAfter the incident is resolved:\n\n1. Verify all locales are loading correctly in production\n2. Check for any data loss (keys deleted or overwritten during incident)\n3. Review rate limit consumption during the incident\n4. Document the timeline in your incident tracker\n5. Schedule a postmortem with findings:\n   - What failed and why\n   - How it was detected (monitoring alert or user report?)\n   - Time to detection, time to mitigation, time to resolution\n   - What changes would prevent recurrence\n\n## Output\n\nAfter executing this runbook:\n- Root cause identified and documented\n- Immediate mitigation applied (fallback translations, redeployment, or cache clear)\n- Stakeholders notified via communication templates\n- Post-incident evidence collected for postmortem\n\n## Error Handling\n\n| Issue During Response | Cause | Solution |\n|----------------------|-------|----------|\n| Can't access Lokalise dashboard | Lokalise fully down | Use CLI with API token; check status.lokalise.com on mobile |\n| Token from secret manager fails | Secret manager also experiencing issues | Use break-glass procedure (documented token in secure vault) |\n| Fallback translations not present | Never set up fallback mechanism | Deploy English-only as emergency, then implement fallback |\n| App crashes on missing translations | No null-safe translation access | Hotfix: wrap translation calls in try-catch, return key name |\n| Rate limited during recovery | Too many API calls fixing the issue | Wait 1 second between requests; max 6 req\u002Fsec |\n| Git deploy blocked by CI | CI translation checks failing | Bypass with `[skip-translation-check]` in commit message (if configured) |\n\n## Examples\n\n### One-Line Health Check\n\n```bash\ncurl -sf \"https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${LOKALISE_PROJECT_ID}\" \\\n  -H \"X-Api-Token: ${LOKALISE_API_TOKEN}\" \\\n  | jq '{name: .project.name, keys: .project.statistics.keys_total, progress: .project.statistics.progress_total}' \\\n  || echo \"UNHEALTHY — API unreachable or auth failed\"\n```\n\n### Application Health Endpoint\n\n```typescript\n\u002F\u002F GET \u002Fhealth\u002Ftranslations\nexport async function translationHealthCheck(): Promise\u003C{\n  status: 'healthy' | 'degraded' | 'unhealthy';\n  details: Record\u003Cstring, unknown>;\n}> {\n  const checks = {\n    api_reachable: false,\n    translations_loaded: false,\n    cache_fresh: false,\n  };\n\n  \u002F\u002F Check 1: Can we reach the Lokalise API?\n  try {\n    const res = await fetch(`https:\u002F\u002Fapi.lokalise.com\u002Fapi2\u002Fprojects\u002F${process.env.LOKALISE_PROJECT_ID}`, {\n      headers: { 'X-Api-Token': process.env.LOKALISE_API_TOKEN! },\n      signal: AbortSignal.timeout(5000),\n    });\n    checks.api_reachable = res.ok;\n  } catch { \u002F* timeout or network error *\u002F }\n\n  \u002F\u002F Check 2: Are translations loaded in memory?\n  checks.translations_loaded = Object.keys(i18next.store.data).length > 0;\n\n  \u002F\u002F Check 3: Is the cache fresh (less than 1 hour old)?\n  const cacheAge = Date.now() - (globalThis.__translationCacheTimestamp ?? 0);\n  checks.cache_fresh = cacheAge \u003C 3600_000;\n\n  const allHealthy = Object.values(checks).every(Boolean);\n  const anyHealthy = Object.values(checks).some(Boolean);\n\n  return {\n    status: allHealthy ? 'healthy' : anyHealthy ? 'degraded' : 'unhealthy',\n    details: checks,\n  };\n}\n```\n\n## Resources\n\n- [Lokalise Status Page](https:\u002F\u002Fstatus.lokalise.com) — First thing to check during an outage\n- [Lokalise API Rate Limits](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Fapi-rate-limits)\n- [Lokalise API Error Codes](https:\u002F\u002Fdevelopers.lokalise.com\u002Freference\u002Ferrors)\n- [Lokalise Support](mailto:support@lokalise.com) — For P1 issues, also try the in-app chat\n- [Lokalise Community Forum](https:\u002F\u002Fcommunity.lokalise.com)\n\n## Next Steps\n\n- After resolving the incident, run `lokalise-prod-checklist` to verify the system is fully healthy\n- Implement the health endpoint from the examples if you do not already have one\n- Set up automated alerting on the health endpoint (Datadog, PagerDuty, or equivalent)\n- Add the fallback translation mechanism to prevent full outage on future API issues\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","lokalise","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute Lokalise incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Lokalise-related outages, investigating errors,\nor running post-incident reviews for Lokalise integration failures.\nTrigger with phrases like \"lokalise incident\", \"lokalise outage\",\n\"lokalise down\", \"lokalise on-call\", \"lokalise emergency\", \"translations broken\".\n","Read, Grep, Bash(curl:*), Bash(lokalise2:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--lokalise-pack--lokalise-incident-runbook",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill lokalise-incident-runbook",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill lokalise-incident-runbook",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill lokalise-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lokalise-pack--lokalise-incident-runbook\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]