Skip to content
TrustedSkillsbeta
Back to all skills

Agent Debugging

Checked
onesmartguy·vlatest·testing

Identifies and suggests fixes for logical errors and inefficiencies in agent code and 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 onesmartguy/next-level-real-estate --skill agent-debugging -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

onesmartguy

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 onesmartguy/next-level-real-estate at b8266e8105.

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

Commit
b8266e8105
Manifest
.claude/skills/agent-debugging/SKILL.md
Scanned
1 file, 1,013 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 agent-debugging skill helps identify and resolve issues within AI agent workflows. It analyzes agent interactions, pinpoints error sources, and suggests corrective actions to improve performance and reliability. This allows for faster iteration cycles and more robust agent deployments.

When to use it

  • Unexpected Agent Behavior: When an agent consistently produces incorrect or undesirable outputs.
  • Workflow Failures: When a multi-step agent workflow fails at specific points, requiring root cause analysis.
  • Performance Bottlenecks: To identify slow response times or inefficient resource utilization within the agent's process.
  • Post-Deployment Issues: After deploying an agent, to proactively monitor and address emerging problems in real-world scenarios.

Key capabilities

  • Interaction Analysis
  • Error Source Identification
  • Corrective Action Suggestions
  • Workflow Failure Point Detection

Example prompts

  • "Analyze the last 10 interactions of my agent and identify any patterns of incorrect responses."
  • "My agent workflow fails at step 3. Can you diagnose the problem?"
  • "What are the potential causes for slow response times in this agent's process?"

Tips & gotchas

The skill requires access to the agent’s interaction logs and workflow definitions for effective debugging. Ensure sufficient logging is enabled within your agent configuration to maximize the skill’s diagnostic capabilities.