Skip to content
TrustedSkillsbeta
Back to all skills

Mole Debug

Checked
autumnsgrove·vlatest·testing

Simulates user interactions to uncover hidden bugs and edge cases in applications, improving test coverage.

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 autumnsgrove/lattice --skill mole-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

autumnsgrove

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 autumnsgrove/groveengine at edebdc71a7.

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

Commit
edebdc71a7
Manifest
.claude/skills/mole-debug/SKILL.md
Scanned
3 files, 422 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 mole-debug skill allows you to inject debug statements into your AI agent's execution flow. It provides a mechanism to observe internal state and decision-making processes, facilitating troubleshooting and understanding of complex agent behavior. This is achieved by inserting print statements at specified locations within the agent’s code or workflow.

When to use it

  • Troubleshooting unexpected behavior: When an AI agent produces incorrect or undesirable results, mole-debug can help pinpoint the source of the problem.
  • Understanding decision paths: If you need to understand why an agent made a particular choice, debug statements can reveal the reasoning process.
  • Validating internal state: Verify that variables and data structures within your agent are being updated as expected during execution.
  • Debugging complex workflows: When dealing with multi-step processes or integrations, mole-debug helps trace the flow of information and identify bottlenecks.

Key capabilities

  • Inject debug print statements into code.
  • Observe internal state during agent execution.
  • Trace decision-making paths.
  • Facilitate troubleshooting of complex agent behavior.

Example prompts

  • "Add a debug statement before calling the get_weather function."
  • "Print the value of user_query after parsing the input."
  • "Insert a debug message at line 25 of the main loop to show current iteration."

Tips & gotchas

The skill requires access to the agent's codebase or workflow definition. Be mindful that excessive debugging can slow down execution and potentially impact performance, so remove or disable statements when no longer needed.