Skip to content
TrustedSkillsbeta
Back to all skills

Debug Tools

Checked
adeonir·vlatest·testing

Provides automated debugging assistance, including breakpoint insertion, variable inspection, and error analysis, streamlining test troubleshooting.

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 adeonir/agent-skills --skill debug-tools -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

adeonir

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 adeonir/agent-skills at 41688525da.

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

Commit
41688525da
Manifest
skills/engineering/debug-tools/SKILL.md
Scanned
7 files, 459 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 debug-tools skill provides access to various debugging utilities. It allows agents to inspect their own internal state, trace execution paths, and identify potential errors in reasoning or action selection. This is particularly useful for understanding why an agent made a specific decision or encountered unexpected behavior.

When to use it

  • Troubleshooting failed tasks: If an agent consistently fails at a task, use debug-tools to examine its thought process and pinpoint the source of the problem.
  • Analyzing complex reasoning chains: When dealing with multi-step processes, debug tools can help visualize the flow of logic and identify where errors might be introduced.
  • Understanding unexpected actions: If an agent takes an action that seems illogical or incorrect, use this skill to inspect its internal state leading up to that decision.
  • Improving agent performance: By identifying bottlenecks and inefficiencies in the agent's workflow, debug-tools can contribute to overall performance improvements.

Key capabilities

  • Internal state inspection
  • Execution tracing
  • Error identification
  • Reasoning analysis

Example prompts

  • "Show me the last 5 steps of your reasoning process."
  • "What was your confidence level when deciding to [action]?"
  • "Trace the execution path that led to this error message: [error message]"

Tips & gotchas

The effectiveness of debug-tools depends on the agent's underlying architecture and logging capabilities. Some agents may have more detailed debugging information available than others.