Skip to content
TrustedSkillsbeta
Back to all skills

Debug

Checked
v1-io·vlatest·testing·MIT

Inspects v1-io data input/output streams to identify errors and bottlenecks during testing workflows.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it v1-debug, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add v1-io/v1tamins --skill v1-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

v1-io

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 v1-io/v1tamins at 7ea8162f49.

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

Commit
7ea8162f49
Manifest
plugins/v1tamins/skills/v1-debug/SKILL.md
Scanned
3 files, 284 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 v1-io-debug skill provides debugging capabilities for AI agents. It allows users to inspect the agent's internal state, including variables and function calls, during execution. This facilitates understanding of the agent’s decision-making process and identification of potential issues or errors.

When to use it

  • Troubleshooting unexpected behavior: When an agent isn't performing as expected, use this skill to examine its intermediate steps.
  • Understanding complex logic: If you need to understand how a specific function or decision was reached within the agent’s workflow.
  • Validating internal state: To confirm that variables and data structures hold the values you anticipate during execution.
  • Debugging custom code: When integrating custom functions, this skill helps pinpoint errors in their implementation.

Key capabilities

  • Inspect variable values
  • Trace function calls
  • Examine agent's internal state

Example prompts

  • "Show me the value of user_input."
  • "What was the last function called?"
  • “Debug step by step”

Tips & gotchas

The skill requires access to the agent’s internal execution environment. Ensure that the agent is configured to allow debugging requests for this skill to function correctly.