Skip to content
TrustedSkillsbeta
Back to all skills

Neovim Debugging

Checked
bityoungjae·vlatest·testing·MIT

Debug Neovim Lua code directly within your editor using this tool's interactive breakpoints and variable inspection.

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 bityoungjae/marketplace --skill neovim-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

bityoungjae

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 bityoungjae/marketplace at 7edbf275de.

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

Commit
7edbf275de
Manifest
plugins/nvim-doctor/skills/neovim-debugging/SKILL.md
Scanned
5 files, 1,421 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 provides debugging capabilities within Neovim. It allows users to attach a debugger (likely using debug.lua) and step through code, inspect variables, and set breakpoints directly from within the Neovim editor. This streamlines the development workflow for Lua developers working in Neovim environments.

When to use it

  • When debugging a custom Neovim plugin written in Lua.
  • While troubleshooting issues with your personal Neovim configuration files.
  • To step through and understand complex Lua code snippets within Neovim.
  • For developers who prefer an integrated debugging experience without leaving the editor.

Key capabilities

  • Integration with debug.lua for debugging functionality.
  • Provides a debugging environment directly within Neovim.
  • Allows stepping through code execution.
  • Enables inspection of variables during debugging.
  • Supports setting breakpoints in Lua code.

Example prompts

  • "Debug this file: my_plugin.lua."
  • "Step into the next line of code."
  • "Print the value of variable 'x'."

Tips & gotchas

  • Requires a working Neovim installation and familiarity with Lua debugging concepts.
  • The specific debugger used (e.g., debug.lua) might require additional configuration or setup.