Individual skill
ember-trace
Zuko's ember trace for runtime forensics. Follow the embers back to the fire that started them. Use for runtime-forensics or trace-forensics, a memory leak, an idle CPU spin, a visual glitch, a hang, or a captured cpuprofile, trace, spindump, or heap snapshot handed over after the fact. The deliverable is a cited diagnosis, not a fix.
plugins/team-avatar/skills/ember-trace/SKILL.md
Source commit 1a301358f7fa8786a5fb8151aea47d93ca547f54
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 112
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-orchestration Repository topic
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- multi-agent Repository topic
- subagents Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,586 bytesSKILL.mdcore · 2,586 bytesSKILL.mdcore · 2,586 bytesSKILL.mdcore · 2,586 bytesSKILL.mdcore · 2,586 bytesreferences/artifact.mddoc · 1,836 bytesreferences/live.mddoc · 1,535 bytes
Read excerpt
# Zuko's ember trace
When Zuko tracked the Avatar, he did not guess where the fire started. He read the scorch marks and followed the embers back to their source. Forensics is the same. You do not theorize from source code. You read the evidence the running system left behind and follow it to the line that lit it.
You own the diagnosis. The deliverable is a cited diagnosis, not a fix. Fix only when asked. Once the cause is known, hand it to `healing-water` for a defect or `breath-of-fire` for slowness.
On Codex, read [avatar-mode/references/codex.md](../avatar-mode/references/codex.md) for tool equivalents.
## Pick the mode
| You have | Mode | Steps |
|----------|------|-------|
| A live process showing the symptom now | Live | [references/live.md](references/live.md) |
| A captured artifact (cpuprofile, `.json.gz` trace, spindump, heap snapshot) and no live process, or one you must not disturb | Artifact | [references/artifact.md](references/artifact.md) |