Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/dev-guide-debug-troubleshoot
Nested lingtai-dev-guide reference for diagnosing LingTai failures: agent process state, OOM/crashes, avatar spawn issues, post-molt memory loss, mail delivery, scheduled messages, tool timeouts, and escalation.
Passed 21 of 22 test cases with the skill, and 4 of 22 without it.
and 27 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
After inspecting an agent whose working pad was wiped, I confirmed pad.md is 0 bytes. What two-tool combination sequence rebuilds the working pad from archived codex knowledge?
| Checked | Without skill | With skill |
|---|---|---|
| Export knowledge entries from codex to file paths before attaching them via pad edit. | Missed | Passed |
The instructions your model reads when the skill loads.
Nested lingtai-dev-guide reference. Read this after the top-level router sends you here.
Read the
lingtai-kernel-anatomyskill first. It owns the concepts — lifecycle states, memory layers, mail protocol, tool surface — that every section below assumes. This document is only the diagnosis-and-recovery procedure; the per-section concept map is at the end.
Problem?
├── Process issues?
│ ├── Peer unresponsive → §1.1
│ ├── Peer OOM / crashed → §1.2
│ └── Cannot spawn avatar → §1.3
├── Memory issues?
│ ├── Post-molt amnesia → §2.1
│ ├── Codex entries missing → §2.2
│ ├── Pad not loaded → §2.3
│ └── Molt imminent, critical operations incomplete → §2.4
├── Communication issues?
│ ├── Pigeon not delivered → §3.1
│ ├── Pigeon bounced "No agent at X" → §3.2
│ └── Scheduled pigeon not firing → §3.3
└── Tool issues?
├── Tool timeout → §4.1
├── Tool not found → §4.2
└── Tool output truncated → §4.3
Pigeons go unanswered; the peer is in contacts but silent. Possible states: busy (long LLM turn), stuck (LLM timeout/upstream error), asleep (energy depleted or lulled), suspended (process dead), or wrong address.
Diagnose in order — system(show) (your own health) → email(contacts) (verify the address) → email(send, address=<peer>, message="ping") → the heartbeat:
ls -la <work-dir>/.lingtai/<peer>/.agent.heartbeat
cat <work-dir>/.lingtai/<peer>/.agent.heartbeat
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.