# Luciq Symbolicate

> Use when crash reports or stack traces are unreadable — obfuscated, minified, or showing raw hex addresses and memory offsets instead of class and method names — or when symbol files need to reach Luciq for a build. Covers uploading iOS dSYMs, Android ProGuard/R8 mapping files, NDK .so symbols, React Native source maps and Flutter Dart symbols, and wiring those uploads permanently into a release pipeline (GitHub Actions, Fastlane, Gradle, Bitrise, CircleCI, an Xcode build phase, cron). Triggers include "my crashes aren't symbolicated", "the stack trace is obfuscated / unreadable / just hex", "upload dSYMs / mapping / source maps to Luciq", "symbolicate in CI", "add symbol upload to our build", "deobfuscate our crashes", "our beta builds need symbols too". There is NO MCP tool for symbol uploads: the luciq CLI is the only path, and this skill installs, authenticates and drives it. For investigating why a crash happens once its trace is already readable use luciq-debug; for exports, scheduled reports or build gating on a metric use luciq-automate.

## Facts
- Page: https://tashan.sh/capability/skill-luciqai-luciq-symbolicate
- tashan id: skill:luciqai/luciq-symbolicate
- Source: https://github.com/luciqai/agent-skills
- Type: skill
- Category: devtools
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: 96.0
- Freshness: 91.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: Apache-2.0
- Official: no

## Install

```sh
cp -r luciq-symbolicate ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-25 by tashan (https://tashan.sh) from public evidence. Scorer s5.