ember-trace
From the author
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.
Install
npx skills add tmcfarlane/team-avatar --skill ember-trace -a claude-code
Installs to .claude/skills/ember-trace/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- breath-of-firetmcfarlane/team-avatarZuko's breath of fire for performance work. Use for slowness, high latency, memory growth, CPU spin, bundle size, cloud cost, "make this faster", or the old perf-issue playbook. Captures a baseline trace, finds the real limit, fixes the cheapest thing that meets the target, and reports a number it can explain.Marketing★ 111
- steady-flametmcfarlane/team-avatarZuko's steady flame for vetting a performance number. A flame that flickers is not a measurement. Use for benchmark-checklist, /benchmark-checklist, before you report or act on a speedup, a regression, a latency, a throughput, a hillclimb harness, or a library or config choice you measured. Checks the limiter, tuning, physical limits, errors, repeatability, relevance, and whether the work happened at all.Other★ 111
- redemption-arctmcfarlane/team-avatarZuko's redemption arc for incidents and postmortems. Use for an outage, a bad deploy, data loss, a production incident, "what went wrong", "write the postmortem", or owning a mistake. Stabilizes first, then builds a blameless timeline, finds the root cause, and turns the lesson into structure.DevOps★ 111
- bug-reviewathola/claude-night-marketHunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.Engineering★ 343
- reproduction-trace-instrumenterArabelaTso/Skills-4-SEInstruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.Planning★ 260
- root-cause-tracingsecondsky/claude-skillsSystematically trace bugs backward through call stack to find original trigger. Use when errors occur deep in execution and you need to trace back to find the original trigger.Other★ 240
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in