# Jinn Node Support Triage

> Collect diagnostics and troubleshoot jinn-node operator issues covering setup, runtime, and connectivity failures. Use when user says "something is broken", "worker not running", "setup failed", "debug jinn", "node won't start", or reports any error.

- Skill: `jinn-network/jinn-node-support-triage` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jinn-network/jinn-node-support-triage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jinn-network/jinn-node-support-triage/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Jinn-Network (https://skillmd.com/u/jinn-network)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/jinn-network/jinn-node-support-triage

---


# jinn-node-support-triage

Use this skill when the operator reports failures and needs actionable diagnostics.

## 1. Collect support bundle

```bash
cd jinn-node
yarn support:bundle
```

Bundle includes system/runtime state and excludes private keys and API secret values.

## 2. Collect runtime logs

If local worker:
```bash
cd jinn-node
yarn worker  # reproduce with fresh logs if needed
```

If Railway worker:
```bash
railway logs --tail 100
```

## 3. Capture context for escalation

Always include:
- expected behavior,
- actual behavior,
- first occurrence time,
- reproduction steps,
- support bundle JSON,
- relevant log excerpt.

## 4. First-line checks

Use `references/troubleshooting.md` for symptom -> fix mapping.

## 5. Escalate

If unresolved after first-line checks, provide:
- support bundle,
- last 100-300 log lines,
- current `.env` key presence summary (not values),
- exact failing command and error text.