root-cause-tracing agent skill by NeoLabHQ
Traces bugs backward through the call stack, adding instrumentation when needed, to find the original source of invalid data or incorrect behavior.
At a glance
| Publisher | NeoLabHQ |
|---|---|
| Repository | NeoLabHQ/context-engineering-kit (53 listed skills) |
| Category | Testing and QA |
| License | GPL-3.0 |
| Last commit | August 26, 2026 (repository) |
| SKILL.md | 183 lines, 736 words |
| Bundled files | 1 file |
| Quality score | 78/100 · C Passes all seven graded checks |
| Security scan | Not scanned |
| README badge | Get the listing badge and raise the score |
Before you install
Read from the skill's files at the directory's October 19, 2026 snapshot: what ships with it, what its code reads, and the terms it is published under.
- Bundled scripts: none.
- License: GPL-3.0, an open-source or open-content license.
Install root-cause-tracing
The skills CLI works with Claude Code, Codex, Cursor and other agents; the other routes copy the folder by hand.
npx skills add https://github.com/NeoLabHQ/context-engineering-kit/tree/master/skills/root-cause-tracingtmp="$(mktemp -d)"
git clone --depth 1 --branch master https://github.com/NeoLabHQ/context-engineering-kit.git "$tmp/repo"
mkdir -p .claude/skills
cp -R "$tmp/repo/"skills/root-cause-tracing .claude/skills/
rm -rf "$tmp"python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo NeoLabHQ/context-engineering-kit \
--path skills/root-cause-tracing \
--ref masterNeoLabHQ/context-engineering-kit is third-party code. Read SKILL.md and any bundled scripts before you install it.
How the author describes it
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
From the description field of SKILL.md. Agents read this line to decide when to load the skill.
Sections in SKILL.md
- Overview
- When to Use
- The Tracing Process
- 1. Observe the Symptom
- 2. Find Immediate Cause
- 3. Ask: What Called This?
- 4. Keep Tracing Up
- 5. Find Original Trigger
- Adding Stack Traces
- Finding Which Test Causes Pollution
- Real Example: Empty projectDir
- Key Principle
- Stack Trace Tips
- Real-World Impact
Files in the skill folder
SKILL.md
Suede Skill Check: 78/100 · C
Report snapshot · · graded-v2
The rubric totals 100 points; published scores are capped at 99. Security scan: not scanned.
Source revision: 23e2428e809d. Report version 9fc27edcff7b. Badge URLs follow the latest listing; save the report to keep this version.
Download report · Request a fresh review
What to review next
- Boundary clause: 0 of 4 points. 4 when the description says when not to use the skill (“Not for …”, “Do not use …”, “Use … instead”).
- Example request: 0 of 3 points. 3 when the description quotes an example request (3–60 characters in quotation marks).
- Reference files: 0 of 3 points. 3 when the skill folder ships a references/, reference/ or docs/ folder.
Add declarations and bundled files when they describe the skill’s actual needs. Update the source, then request a fresh review with the changed commit or PR.
root-cause-tracing passes the required frontmatter check and all seven graded checks, which cover the SKILL.md format, a declared license and a commit in the last year. Those checks earn 56 of the score’s points; the rest come from description quality, instruction depth, bundled files, maintenance and curated-list citations. How the score works.
See the checks and points
| Check | Result |
|---|---|
| Frontmatter parses and declares a name and a description | Pass |
| Name uses lowercase letters, digits and hyphens, 64 characters or fewer | Pass |
| Name matches the skill's folder name | Pass |
| Description is between 50 and 1,024 characters | Pass |
| Description says when an agent should use the skill | Pass |
| SKILL.md body is 500 lines or fewer | Pass |
| A license is declared in the frontmatter or the repository | Pass |
| Repository has a commit in the last 12 months | Pass |
| Score component | Points |
|---|---|
| Structural checks | 56 of 56 |
| Description length | 5 of 5 |
| Boundary clause | 0 of 4 |
| Example request | 0 of 3 |
| Instruction depth | 7 of 7 |
| Reference files | 0 of 3 |
| Bundled scripts | 0 of 2 |
| Recent maintenance | 6 of 9 |
| Curated-list citations | 4 of 7 |
| Tool permissions declared | 0 of 2 |
| Compatibility declared | 0 of 2 |
Show the listing and raise the score
root-cause-tracing is listed with 78/100 · C. This badge links to its Suede listing. Skills scoring 80–99 add a numeric and a letter quality shield; the largest open points for root-cause-tracing are boundary clause (4), example request (3) and recent maintenance (3). Send your repository and the points you want to raise, then request a fresh review after updating the skill.
[](https://skills.suedeai.ai/directory/neolabhq/context-engineering-kit/root-cause-tracing/)<a href="https://skills.suedeai.ai/directory/neolabhq/context-engineering-kit/root-cause-tracing/"><img src="https://skills.suedeai.ai/directory/badge.svg" alt="Suede Skills Directory: listed" height="20"></a>Where this skill is cited
NeoLabHQ/context-engineering-kit appears in 3 curated lists: ComposioHQ/awesome-claude-skills, VoltAgent/awesome-agent-skills, hesreallyhim/awesome-claude-code.