Lokalise ObservabilitySAFE
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-observability description: 'Set up comprehensive observability for Lokalise integrations with metrics, traces, and alerts. Use when implementing monitoring for Lokalise operations, setting up dashboards, or configuring alerting for Lokalise integration health. Trigger with phrases like "lokalise monitoring", "lokalise metrics", "lokalise observability", "monitor lokalise", "lokalise alerts", "lokalise tracing". ' allowed-tools: Read, Write, Edit, Bash(curl:*), Bash(jq:*), Bash(npm:*) version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - lokalise - monitoring - observability - dashboard compatibility: Designed for Claude Code --- # Lokalise Observability ## Overview Monitor Lokalise translation pipeline health: API response times, rate limit consumption, translation completion rates, webhook delivery reliability, file upload/download status, and per-word cost tracking. Built around the `@lokalise/node-api` SDK with Prometheus-compatible metrics and alerting rules. ## Prerequisites - `@lokalise/node-api` SDK installed - Metrics backend (Prometheus, Datadog, CloudWatch, or OpenTelemetry collector) - Lokalise API token with read access - Optional: webhook endpoint for real-time event monitoring ## Instructions ### Step 1: Instrument API Calls with Metrics Wrap every SDK call to emit duration, success/failure counts, and rate limit status. ```typescript import { LokaliseApi } from "@lokalise/node-api"; interface MetricLabels { operation: string; status: "ok" | "error"; code?: string; } // Implement this to emit to your metrics backend declare function emitHistogram(name: string, value: number, labels: MetricLabels): void; declare function emitCounter(name: string, value: number, labels: MetricLabels): void; const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! }); async function trackedApiCall<T>( operation: string, fn: () => Promise<T> ): Promise<T> { const start = performance.now(); try { const result = await fn(); const durationMs = performance.now() - start; emitHistogram("lokalise_api_duration_ms", durationMs, { operation, status: "ok", }); emitCounter("lokalise_api_requests_total", 1, { operation, status: "ok", }); return result; } catch (err: unknown) { const code = (err as { code?: number })?.code?.toString() ?? "unknown"; const durationMs = performance.now() - start; emitHistogram("lokalise_api_duration_ms", durationMs, { operation, status: "error", code, }); emitCounter("lokalise_api_requests_total", 1, { operation, status: "error", code, }); throw err; } } // Usage — wrap every SDK call const keys = await trackedApiCall("keys.list", () => lok.keys().list({ project_id: projectId, limit: 500 }) ); const bundle = await trackedApiCall("files.download", () => lok.files().download(projectId, { format: "json", filter_langs: ["en"], original_filenames: false, }) ); ``` ### Step 2: Monitor Translation Completion Poll project statistics and emit per-locale progress as gauge metrics. ```typescript declare function emitGauge(name: string, value: number, labels: Record<string, string>): void; async function collectTranslationMetrics(projectId: string): Promise<void> { const project = await trackedApiCall("projects.get", () => lok.projects().get(projectId) ); // Overall progress emitGauge("lokalise_translation_progress_pct", project.statistics?.progress_total ?? 0, { project: projectId, locale: "all", }); emitGauge("lokalise_keys_total", project.statistics?.keys_total ?? 0, { project: projectId, }); // Per-language progress const languages = await trackedApiCall("languages.list", () => lok.languages().list({ project_id: projectId, limit: 100 }) ); for (const lang of languages.items) { emitGauge("lokalise_translation_progress_pct", lang.statistics?.progress ?? 0, { project: projectId, locale: lang.lang_iso, }); emitGauge("lokalise_words_to_do", lang.statistics?.words_to_do ?? 0, { project: projectId, locale: lang.lang_iso, }); } } // Run on a schedule (every 5 minutes) // setInterval(() => collectTranslationMetrics(projectId), 5 * 60_000); ``` ### Step 3: Track Rate Limit Consumption ```bash set -euo pipefail # Quick rate limit check — call from a monitoring cron job HEADERS=$(curl -sI "https://api.lokalise.com/api2/projects?limit=1" \ -H "X-Api-Token: ${LOKALISE_API_TOKEN}" 2>/dev/null) LIMIT=$(echo "$HEADERS" | grep -i "x-ratelimit-limit" | awk '{print $2}' | tr -d '\r') REMAINING=$(echo "$HEADERS" | grep -i "x-ratelimit-remaining" | awk '{print $2}' | tr -d '\r') RESET=$(echo "$HEADERS" | grep -i "x-ratelimit-reset" | awk '{print $2}' | tr -d '\r') echo "Rate limit: ${REMAINING}/${LIMIT} remaining (resets at ${RESET})" # Emit as metrics for Prometheus/Datadog # lokalise_rate_limit_remaining ${REMAINING} # lokalise_rate_limit_max ${LIMIT} ``` ### Step 4: Monitor Webhook Delivery Track webhook processing success and latency in your webhook handler. ```typescript import express from "express"; const webhookMetrics = { received: 0, processed: 0, failed: 0, totalLatencyMs: 0, }; app.post("/webhooks/lokalise", async (req: express.Request, res: express.Response) => { webhookMetrics.received++; const start = performance.now(); // Respond immediately — Lokalise times out after 8 seconds res.status(200).json({ received: true }); try { await processWebhookEvent(req.body); webhookMetrics.processed++; } catch (error) { webhookMetrics.failed++; console.error("Webhook processing failed:", error); } const latencyMs = performance.now() - start; webhookMetrics.totalLatencyMs += latencyMs; emitCounter("lokalise_webhook_received_total", 1, { event: req.body.event, status: webhookMetrics.failed >
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 (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__lokalise-observability.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 Observability 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 Observability 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 Observability access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Lokalise Observability 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.