Skip to content
TrustedSkillsbeta
Back to all skills

Vscode Extension Debugger

Checked
s-hiraoku·vlatest·backend·MIT

This VSCode extension debugger allows developers to step through and debug their extensions' code in real-time, streamlining development and 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 s-hiraoku/vscode-sidebar-terminal --skill vscode-extension-debugger -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

s-hiraoku

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 s-hiraoku/vscode-sidebar-terminal at 17ccc31243.

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

Commit
17ccc31243
Manifest
.claude/skills/vscode-extension-debugger/SKILL.md
Scanned
4 files, 1,999 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

This skill allows an AI agent to debug VS Code extensions. It provides the capability to set breakpoints, step through code, inspect variables, and evaluate expressions within a running VS Code extension's context. This enables developers to diagnose and resolve issues in their extensions more effectively.

When to use it

  • Debugging Extension Logic: Troubleshoot unexpected behavior or errors occurring within a custom VS Code extension.
  • Analyzing Performance Bottlenecks: Identify slow code paths or inefficient operations impacting an extension's performance.
  • Reproducing User-Reported Issues: Step through the execution flow to understand and fix bugs reported by users of a VS Code extension.
  • Testing Extension Features: Verify that new features or modifications within an extension function as intended.

Key capabilities

  • Breakpoint Setting
  • Code Stepping (Step Over, Step Into, Step Out)
  • Variable Inspection
  • Expression Evaluation

Example prompts

  • "Debug this VS Code extension and set a breakpoint at line 25 of the main.ts file."
  • "Step through the execution of this extension's command handler to find out why it’s not responding correctly."
  • "Inspect the value of the 'currentWord' variable while debugging this extension."

Tips & gotchas

Requires a VS Code development environment and an understanding of VS Code extension development principles. The agent needs access to the extension's source code to effectively debug it.