Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lokalise-debug-bundle
Collect Lokalise debug evidence for support tickets and troubleshooting.
Passed 18 of 20 test cases with the skill, and 11 of 20 without it.
and 8 more in the full report
8 fixed12 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When scrubbing application logs before archiving a diagnostic bundle for localization troubleshooting, what substitution string should replace matched email addresses?
| Checked | Without skill | With skill |
|---|---|---|
| Output replaces matched email addresses with [REDACTED_EMAIL] | Missed | Passed |
The instructions your model reads when the skill loads.
!node --version 2>/dev/null || echo 'N/A'
!python3 --version 2>/dev/null || echo 'N/A'
!uname -a
Collect all diagnostic information needed to troubleshoot Lokalise integration issues or file a support ticket — environment versions, SDK/CLI status, API connectivity, project listings with key counts, upload process status, and redacted logs, bundled into a timestamped .tar.gz archive.
LOKALISE_API_TOKEN environment variable set (or token available to provide)curl and jq available on PATH@lokalise/node-api SDK installed in current projectlokalise2 CLI installedset -euo pipefail
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
BUNDLE_DIR="lokalise-debug-${TIMESTAMP}"
mkdir -p "${BUNDLE_DIR}"
echo "Bundle directory: ${BUNDLE_DIR}"
set -euo pipefail
cat > "${BUNDLE_DIR}/environment.txt" <<ENVEOF
=== System ===
OS: $(uname -srm)
Shell: ${SHELL:-unknown}
Date: $(date -u +"%Y-%m-%dT%H:%M:%SZ")
test cases passed, vs 11 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.