Skills neovim-debugging
📦

neovim-debugging

Content revision r2 High Risk ⚡ Contains scripts📁 Filesystem access⚙️ External commands

Diagnose Neovim and LazyVim Problems

Neovim configuration failures are difficult to isolate across plugins, mappings, and runtime state. This skill applies targeted tests to identify causes and propose verified fixes.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "neovim-debugging" from https://skillstore.io/skills/bityoungjae-neovim-debugging.md and its manifest at https://skillstore.io/api/skills/bityoungjae-neovim-debugging/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/bityoungjae-neovim-debugging.md Signed manifest GET /api/skills/bityoungjae-neovim-debugging/manifest Signed lockfile GET /api/skills/bityoungjae-neovim-debugging/lockfile

Test it

Using "neovim-debugging". The local leader mappings exist, but which-key does not open for the local leader.

Expected outcome:

Diagnosis: which-key is loaded, but its automatic trigger excludes the local leader. Verify manual opening, then add the local leader trigger.

Using "neovim-debugging". A Telescope function became unavailable after updating plugins.

Expected outcome:

Diagnosis: the update likely changed an exported API or extension load order. Confirm the function and locked versions before changing configuration.

Using "neovim-debugging". Neovim startup is slow, but a minimal configuration starts quickly.

Expected outcome:

Diagnosis: plugin or user configuration overhead is the likely source. Compare timing entries and test the slowest component in isolation.

Security Audit

High Risk
v10 • 7/23/2026 Open versioned report

Most matches are scanner false positives caused by Neovim terms, Markdown fences, local configuration paths, and headless diagnostic commands. Fixed filenames under /tmp create symlink and log-disclosure risks, while executable templates can become injection vectors if placeholders contain untrusted input. Publication should wait until command templates and temporary-file handling are hardened.

5
Files scanned
1,573
Lines analyzed
6
Review items
0
False positives ignored

Confirmed security concerns (1)

High
SKILL.md:42-60
Unvalidated Placeholders in Executable Commands
The skill encourages headless execution with PLUGIN_NAME, CONFIG_PATH, and MODULE inside a double-quoted shell argument. Untrusted substitutions can trigger shell expansion or execute arbitrary Lua.
The executable templates and placeholders are explicit, and no validation or safe argument-passing rule is provided. Exploitation still depends on unsafe substitution by the agent.
Capability review items (6)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
diagnostic-flowchart.md:167
Temp directory access
│ nvim --startuptime /tmp/startup.log +q │
This writes to predictable shared path /tmp/startup.log. A local attacker could use a symlink for file clobbering, and the log may be broadly readable.
Medium
diagnostic-flowchart.md:189
Temp directory access
│ nvim -u NONE --startuptime /tmp/minimal.log +q │
This writes to predictable shared path /tmp/minimal.log. A local attacker could use a symlink for file clobbering, and the log may be broadly readable.
Medium
diagnostic-flowchart.md:207
Temp directory access
│ :profile start /tmp/profile.log │
Profiling writes to predictable shared path /tmp/profile.log. A local attacker could use a symlink for file clobbering, and profile data may be exposed.
Medium
error-patterns.md:268
Temp directory access
nvim 2>&1 | tee /tmp/nvim-startup.log
Tee writes startup output to predictable shared path /tmp/nvim-startup.log. Symlink clobbering and broad readability can expose diagnostic content.
Medium
error-patterns.md:271
Temp directory access
nvim -V10/tmp/verbose.log --startuptime /tmp/startup.log +q
The command writes two predictable files under shared /tmp. Existing symlinks can redirect writes, and verbose logs can expose local paths or configuration details.
Medium
information-gathering.md:220
Temp directory access
`nvim --startuptime /tmp/startup.log +q && tail -1 /tmp/startup.log`
The command writes to predictable shared path /tmp/startup.log. A local attacker could redirect the write through a symlink, and timing data may be exposed.

Risk Factors

⚡ Contains scripts (3)
diagnostic-flowchart.md:182 error-patterns.md:82 error-patterns.md:145
📁 Filesystem access (39)
diagnostic-flowchart.md:154 diagnostic-flowchart.md:294 diagnostic-flowchart.md:154 diagnostic-flowchart.md:294 diagnostic-flowchart.md:167 diagnostic-flowchart.md:168 diagnostic-flowchart.md:179 diagnostic-flowchart.md:189 diagnostic-flowchart.md:207 diagnostic-flowchart.md:212 error-patterns.md:268 error-patterns.md:271 information-gathering.md:60 information-gathering.md:63 information-gathering.md:66 information-gathering.md:69 information-gathering.md:79 information-gathering.md:82 information-gathering.md:286 information-gathering.md:289 information-gathering.md:60 information-gathering.md:63 information-gathering.md:66 information-gathering.md:69 information-gathering.md:79 information-gathering.md:82 information-gathering.md:286 information-gathering.md:289 information-gathering.md:60 information-gathering.md:220 plugin-specifics.md:378 plugin-specifics.md:406 plugin-specifics.md:449 plugin-specifics.md:378 plugin-specifics.md:406 plugin-specifics.md:449 SKILL.md:60 SKILL.md:60 SKILL.md:60
⚙️ External commands (20)
information-gathering.md:123-128 information-gathering.md:136-139 information-gathering.md:148-150 information-gathering.md:155 information-gathering.md:173 information-gathering.md:186-190 information-gathering.md:197-201 information-gathering.md:201-202 information-gathering.md:210-211 information-gathering.md:211-212 information-gathering.md:220-227 information-gathering.md:262-263 SKILL.md:34 SKILL.md:44-61 SKILL.md:61-65 SKILL.md:65-83 SKILL.md:83-100 SKILL.md:100-115 SKILL.md:115-134 SKILL.md:134-148
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/bityoungjae-neovim-debugging/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/bityoungjae-neovim-debugging/security.svg)](https://skillstore.io/skills/bityoungjae-neovim-debugging?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/bityoungjae-neovim-debugging?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bityoungjae-neovim-debugging/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/bityoungjae-neovim-debugging.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

BitYoungjae. (2026). neovim-debugging security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bityoungjae-neovim-debugging/audits/10

BibTeX citation

@techreport{bityoungjae-bityoungjae-neovim-debugging-2026, author = {BitYoungjae}, title = {neovim-debugging security audit report (audit version 10)}, institution = {Skillstore}, year = {2026}, number = {10}, url = {https://skillstore.io/skills/bityoungjae-neovim-debugging/audits/10}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "neovim-debugging security audit report (audit version 10)" version: "unspecified" type: report authors: - name: "BitYoungjae" date-released: "2026-07-23" url: "https://skillstore.io/skills/bityoungjae-neovim-debugging/audits/10" identifiers: - type: other value: "skillstore:bityoungjae-neovim-debugging:audit:10" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance

What You Can Build

Repair a Broken Keymap

Trace missing or conflicting mappings, leader settings, plugin loading, and which-key triggers.

Investigate Plugin Failures

Check plugin installation, load conditions, exported functions, configuration calls, and version changes.

Profile Editor Performance

Separate startup and runtime delays, collect timing evidence, and identify slow plugins or functions.

Try These Prompts

Explain an Error 
Diagnose this Neovim error: [complete error]. Explain its likely cause and give one focused verification step.
Trace a Keymap 
My Neovim key [key] should [expected behavior], but [actual behavior]. Build a short hypothesis list and test the most likely cause first.
Debug a Plugin 
Investigate why [plugin] is not working in [Neovim or LazyVim]. Use this configuration and error evidence: [details]. Confirm loading before proposing changes.
Analyze Performance 
Diagnose this Neovim performance problem: [symptom and trigger]. Design a minimal comparison, interpret the measurements, and identify the strongest root-cause evidence.

Best Practices

  • Provide the complete error, exact trigger, expected behavior, and recent configuration changes.
  • Run the smallest diagnostic that can distinguish between the leading hypotheses.
  • Review commands, validate placeholders, and protect diagnostic logs before execution.

Avoid

  • Do not run every diagnostic command without a specific hypothesis.
  • Do not interpolate untrusted names or expressions into shell or Lua commands.
  • Do not modify configuration until evidence identifies the responsible layer.

Frequently Asked Questions

Does this skill support standard Neovim?
Yes. Core error, keymap, LSP, UI, and performance methods apply without LazyVim.
Does it edit my configuration automatically?
It can propose changes, but configuration edits should follow a confirmed diagnosis and user approval.
Can it debug visual problems?
It can inspect relevant settings and plugins. User feedback is still needed for appearance and interactive behavior.
Which plugins receive specific guidance?
The references cover lazy.nvim, which-key, LSP, Treesitter, Telescope, nvim-cmp, Snacks, and LazyVim.
Why does it use headless Neovim?
Headless checks provide repeatable evidence about modules, options, mappings, and plugin state without opening the interface.
What information should I provide?
Provide the full error, exact reproduction steps, expected result, actual result, versions, and recent changes.

Developer Details

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/BitYoungjae/marketplace/tree/main/plugins/nvim-doctor/skills/neovim-debugging

Ref

8c3e20bba512c392d9b02ee748b18e0b09d4982c

Maintenance freshness

7/24/2026

Usage

6 downloads · 235 views

File structure

📄 diagnostic-flowchart.md

📄 error-patterns.md

📄 information-gathering.md

📄 plugin-specifics.md

📄 SKILL.md