Lokalise Prod ChecklistSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: lokalise-prod-checklist description: 'Execute Lokalise production deployment checklist and rollback procedures. Use when deploying Lokalise integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "lokalise production", "deploy lokalise", "lokalise go-live", "lokalise launch checklist". ' allowed-tools: Read, Bash(lokalise2:*), Bash(curl:*), Grep version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - lokalise - deployment compatibility: Designed for Claude Code --- # Lokalise Production Checklist ## Overview A structured pre-deployment checklist for Lokalise integrations covering nine verification areas: translation coverage, missing key detection, format validation, API token security, rate limit preparedness, fallback language configuration, download verification, OTA configuration, and contributor access review. Run through each section before any production deployment. ## Prerequisites - Lokalise project with production API token - `lokalise2` CLI installed and authenticated - `curl` and `jq` available in your environment - Access to the Lokalise dashboard (Team Owner or Admin role) - Application codebase with i18n integration ready for deployment ## Instructions ### Step 1: Translation Coverage Audit Verify that every supported locale meets the coverage threshold before deploying. ```bash #!/bin/bash # scripts/audit-translation-coverage.sh set -euo pipefail : "${LOKALISE_API_TOKEN:?Required}" : "${LOKALISE_PROJECT_ID:?Required}" REQUIRED_COVERAGE=100 # Percentage required for production REQUIRED_LOCALES=("en" "de" "fr" "es" "ja") echo "=== Translation Coverage Audit ===" # Get project statistics from Lokalise API STATS=$(curl -sf "https://api.lokalise.com/api2/projects/${LOKALISE_PROJECT_ID}/statistics" \ -H "X-Api-Token: ${LOKALISE_API_TOKEN}") TOTAL_KEYS=$(echo "$STATS" | jq '.project_statistics.keys_total') echo "Total keys in project: $TOTAL_KEYS" # Get per-language statistics LANGUAGES=$(curl -sf "https://api.lokalise.com/api2/projects/${LOKALISE_PROJECT_ID}/languages" \ -H "X-Api-Token: ${LOKALISE_API_TOKEN}") FAILED=0 echo "" echo "Locale | Progress | Words | Status" echo "---------|----------|-----------|-------" for locale in "${REQUIRED_LOCALES[@]}"; do progress=$(echo "$LANGUAGES" | jq -r ".languages[] | select(.lang_iso == \"${locale}\") | .statistics.progress") words=$(echo "$LANGUAGES" | jq -r ".languages[] | select(.lang_iso == \"${locale}\") | .statistics.words_to_do") if [[ -z "$progress" || "$progress" == "null" ]]; then echo "${locale} | MISSING | - | FAIL" FAILED=1 continue fi if (( $(echo "$progress < $REQUIRED_COVERAGE" | bc -l) )); then echo "${locale} | ${progress}% | ${words} remaining | FAIL" FAILED=1 else echo "${locale} | ${progress}% | 0 | PASS" fi done echo "" if [[ $FAILED -eq 1 ]]; then echo "RESULT: FAILED — Resolve incomplete translations before deploying." exit 1 fi echo "RESULT: PASSED — All locales meet ${REQUIRED_COVERAGE}% coverage." ``` ### Step 2: Missing Key Detection Detect keys present in source code but absent from Lokalise, and vice versa. ```bash #!/bin/bash # scripts/detect-missing-keys.sh set -euo pipefail : "${LOKALISE_API_TOKEN:?Required}" : "${LOKALISE_PROJECT_ID:?Required}" echo "=== Missing Key Detection ===" # Download current translation keys from Lokalise TEMP_DIR=$(mktemp -d) trap 'rm -rf "$TEMP_DIR"' EXIT lokalise2 file download \ --token "$LOKALISE_API_TOKEN" \ --project-id "$LOKALISE_PROJECT_ID" \ --format json \ --original-filenames=true \ --directory-prefix="" \ --unzip-to "$TEMP_DIR/" 2>/dev/null # Extract keys from Lokalise download LOKALISE_KEYS=$(jq -r '[paths(scalars)] | map(join(".")) | .[]' "$TEMP_DIR/en.json" | sort) # Extract keys referenced in source code (adjust pattern for your framework) # React/i18next: t('key'), t("key"), <Trans i18nKey="key"> SOURCE_KEYS=$(grep -roh "t(['\"][^'\"]*['\"])" src/ 2>/dev/null \ | sed "s/t(['\"]//;s/['\"])//" \ | sort -u || true) echo "" echo "Keys in Lokalise: $(echo "$LOKALISE_KEYS" | wc -l)" echo "Keys in source code: $(echo "$SOURCE_KEYS" | wc -l)" # Keys in code but not in Lokalise MISSING_IN_LOKALISE=$(comm -23 <(echo "$SOURCE_KEYS") <(echo "$LOKALISE_KEYS") || true) if [[ -n "$MISSING_IN_LOKALISE" ]]; then echo "" echo "MISSING IN LOKALISE (used in code but not uploaded):" echo "$MISSING_IN_LOKALISE" | head -20 COUNT=$(echo "$MISSING_IN_LOKALISE" | wc -l) [[ $COUNT -gt 20 ]] && echo " ... and $((COUNT - 20)) more" fi # Keys in Lokalise but not in code (potential dead keys) ORPHANED=$(comm -13 <(echo "$SOURCE_KEYS") <(echo "$LOKALISE_KEYS") || true) if [[ -n "$ORPHANED" ]]; then echo "" echo "ORPHANED IN LOKALISE (not referenced in code):" echo "$ORPHANED" | head -20 COUNT=$(echo "$ORPHANED" | wc -l) [[ $COUNT -gt 20 ]] && echo " ... and $((COUNT - 20)) more" fi if [[ -z "$MISSING_IN_LOKALISE" && -z "$ORPHANED" ]]; then echo "" echo "RESULT: PASSED — Keys are in sync." fi ``` ### Step 3: Format Validation Validate that downloaded translation files are well-formed JSON and contain no placeholder mismatches. ```typescript // scripts/validate-translation-format.ts import fs from 'fs'; import path from 'path'; const LOCALES_DIR = 'src/locales'; const SOURCE_LOCALE = 'en'; const PLACEHOLDER_REGEX = /\{\{?\w+\}?\}|%[sd@]|\$\{[\w.]+\}/g; interface ValidationResult { locale: string; valid: boolean; errors: string[]; } function validate(): ValidationResult[] { const results: ValidationResult[] = []; const sourceFile = path.join(LOCALES_DIR, `${SOURCE_LOCALE}.json`); const sourceContent = JSON.parse(fs.readFileSync(sourceFile, 'utf-8')); const sourcePlaceholders = extractPlaceholders(sourceContent); for (const file of fs.readdirSync(LOCALES_DIR)) { if (!file.endsWith('.js
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (1)
echo " - Admin: Full access (limit to 2-3 people)"
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__lokalise-prod-checklist.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Lokalise Prod Checklist skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Lokalise Prod Checklist safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Lokalise Prod Checklist access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Lokalise Prod Checklist work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.