Skip to content
TrustedSkillsbeta
Back to all skills

Stack Debug

Checked
outfitter-dev·vlatest·testing·MIT

Quickly identifies root causes in complex code stacks by analyzing logs and traces, streamlining debugging workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add outfitter-dev/agents --skill stack-debug -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

outfitter-dev

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned outfitter-dev/agents at d37fffdd50.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d37fffdd50
Manifest
plugins/outfitter-stack/skills/stack-debug/SKILL.md
Scanned
1 file, 202 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The stack-debug skill allows AI agents to analyze and interpret call stacks from errors or debugging sessions. It can extract relevant information like function names, line numbers, and file paths to help understand the sequence of events leading to a problem. This facilitates quicker identification and resolution of software bugs and issues.

When to use it

  • Debugging application crashes: Provide the agent with a crash dump's call stack to pinpoint the origin of the error.
  • Analyzing slow function performance: Use the skill on profiler output to understand which functions are contributing most to execution time.
  • Understanding complex code flows: When tracing through intricate logic, use the skill to visualize and interpret the sequence of function calls.
  • Investigating unexpected behavior in automated tests: Analyze call stacks from failing test cases to identify the root cause of failures.

Key capabilities

  • Call stack parsing
  • Function name extraction
  • Line number identification
  • File path resolution

Example prompts

  • "Analyze this call stack and tell me what function caused the error."
  • "Extract all file paths from this stack trace."
  • “Explain the sequence of calls leading to this point in the stack.”

Tips & gotchas

The skill requires a properly formatted call stack as input, typically found in log files or debugger output. The accuracy of the analysis depends on the quality and completeness of the provided stack information.