How do I install the Meta Stack Trace Investigator skill?

Run npx skillmds@latest add gabrielmoreira/meta-stack-trace-investigator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Meta Stack Trace Investigator safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Meta Stack Trace Investigator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Meta Stack Trace Investigator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Meta Stack Trace Investigator?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meta Stack Trace Investigator by gabrielmoreira

Name: Meta Stack Trace Investigator
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Meta Stack Trace Investigator

Use this meta-skill instead of answering directly when the user gives a stack trace, traceback, runtime error, or failing log that benefits from multi-skill orchestration across trace parsing, repo/history inspection, patch-target analysis, reproduction guidance, and verification commands.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Stack-Trace Investigator (Meta-Skill)

A combinator-style meta-skill that converts a pasted stack trace into a structured root-cause report. It now classifies Python, JavaScript, TypeScript, Go, Rust, or unknown traces before running the investigation. After parsing the trace once, heterogeneous investigations run in parallel:

grep_repo — ripgrep for the symbols in the current repo
search_issues — gh issue list for similar reported problems
git_history — recent commits touching the affected files
diff_context — git-diff skill for current worktree context
history_patterns — history-explorer skill for prior skill/router usage patterns
memory_recall — prior incidents stored under the traceback topic
language_probe — routed to the language-specific helper skill (stack-trace-python-probe, stack-trace-js-probe, stack-trace-go-probe, stack-trace-rust-probe, or generic fallback)

The root_cause and repro_suggestion steps fan the signals into a hypothesis, concrete fix targets, and verification commands. The final summary labels degraded evidence sources explicitly before persisting the incident.

Trigger surface

Fire by saying investigate stack trace or one of the localized triggers listed in the frontmatter, with the traceback pasted into the same turn.

Fallback

If any leaf step fails, the orchestrator surfaces partial outputs in step_outputs. Operator should manually run rg <symbols>, gh issue list --search, git log, and memory search and synthesize the report by hand.

---name: meta-stack-trace-investigatordescription: Use this meta-skill instead of answering directly when the user gives a stack trace, traceback, runtime error, or failing log that benefits from multi-skill orchestration across trace parsing, repo/history inspection, patch-target analysis, reproduction guidance, and verification commands.--- # Stack-Trace Investigator (Meta-Skill) A **combinator-style** meta-skill that converts a pasted stack trace into a structured root-cause report. It now classifies Python, JavaScript, TypeScript, Go, Rust, or unknown traces before running the investigation. After parsing the trace once, heterogeneous investigations run in parallel: 1. **`grep_repo`** — ripgrep for the symbols in the current repo 2. **`search_issues`** — `gh issue list` for similar reported problems 3. **`git_history`** — recent commits touching the affected files 4. **`diff_context`** — `git-diff` skill for current worktree context 5. **`history_patterns`** — `history-explorer` skill for prior skill/router usage patterns 6. **`memory_recall`** — prior incidents stored under the `traceback` topic 7. **`language_probe`** — routed to the language-specific helper skill (`stack-trace-python-probe`, `stack-trace-js-probe`, `stack-trace-go-probe`, `stack-trace-rust-probe`, or generic fallback) The `root_cause` and `repro_suggestion` steps fan the signals into a hypothesis, concrete fix targets, and verification commands. The final summary labels degraded evidence sources explicitly before persisting the incident. ## Trigger surface Fire by saying `investigate stack trace` or one of the localized triggers listed in the frontmatter, with the traceback pasted into the same turn. ## Fallback If any leaf step fails, the orchestrator surfaces partial outputs in `step_outputs`. Operator should manually run `rg <symbols>`, `gh issue list --search`, `git log`, and `memory search` and synthesize the report by hand.

Frequently asked questions