How do I install the Nvim Plugin Add skill?

Run npx skillmds@latest add diegosouzapw/nvim-plugin-add in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nvim Plugin Add safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nvim Plugin Add?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nvim Plugin Add free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nvim Plugin Add?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nvim Plugin Add by diegosouzapw — Agent Skill

Name: Nvim Plugin Add
Rating: 4.2 (5 reviews)
Author: diegosouzapw

Nvim Plugin Add

Add and configure Neovim plugins in this dotfiles repo using lazy.nvim. Use when asked to install a plugin, create its config module, update lazy.nvim imports, read plugin README/docs, and add keymaps without conflicting with existing mappings under config/nvim.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

Neovim plugin add (lazy.nvim)

Use this workflow when adding a new plugin to config/nvim.

Workflow

Inspect the existing layout

Open config/nvim/init.lua to confirm the lazy.nvim spec import list.
Check config/nvim/lua/plugins/ for the naming pattern of plugin config files.

Read upstream docs

Read the plugin README and docs from its repo (and any doc/*.txt if needed).
Prefer the upstream “recommended” or “minimal working” configuration.

Create a plugin config module

Add a new file under config/nvim/lua/plugins/<plugin-name>.lua.
Return a lazy.nvim spec table (same style as other plugin files).
Keep the module self-contained; avoid global side effects.

Add { import = 'plugins.<plugin-name>' } to the spec list in config/nvim/init.lua.
Keep the ordering consistent with existing imports unless the plugin suggests a dependency order.

Keymap collision check

Before adding keymaps, search existing mappings:
- rg -n "keymap|map\\(" config/nvim
- Also scan for which-key registrations if present.
If a recommended mapping conflicts, choose a nearby alternative under the same mnemonic prefix.
Use desc for every mapping.

Configure defaults and options

Wire up plugin setup() with upstream defaults plus any repo-specific conventions.
Follow existing patterns (e.g., use vim.keymap.set, local helper functions).
Keep options and mappings minimal; avoid speculative tweaks.

Validation

Ensure the plugin file is required by lazy.nvim and no syntax errors are introduced.
If the change impacts keymaps, mention any new keys in the response.

Repo conventions

Neovim config root: config/nvim/.
lazy.nvim bootstrap and imports live in config/nvim/init.lua.
Plugin config modules live in config/nvim/lua/plugins/ and return a plugin spec.
Keep edits ASCII-only unless the file already uses non-ASCII.

Notes on keymaps

Prefer <leader> mappings and keep them consistent with existing prefixes.
Avoid overriding single-letter normal mode bindings unless the repo already does so.
When in doubt, add a which-key entry matching the new mapping.

---name: nvim-plugin-adddescription: Add and configure Neovim plugins in this dotfiles repo using lazy.nvim. Use when asked to install a plugin, create its config module, update lazy.nvim imports, read plugin README/docs, and add keymaps without conflicting with existing mappings under config/nvim.---# Neovim plugin add (lazy.nvim)Use this workflow when adding a new plugin to `config/nvim`.## Workflow1) Inspect the existing layout- Open `config/nvim/init.lua` to confirm the lazy.nvim `spec` import list.- Check `config/nvim/lua/plugins/` for the naming pattern of plugin config files.2) Read upstream docs- Read the plugin README and docs from its repo (and any `doc/*.txt` if needed).- Prefer the upstream “recommended” or “minimal working” configuration.3) Create a plugin config module- Add a new file under `config/nvim/lua/plugins/<plugin-name>.lua`.- Return a lazy.nvim spec table (same style as other plugin files).- Keep the module self-contained; avoid global side effects.4) Register the module in lazy.nvim- Add `{ import = 'plugins.<plugin-name>' }` to the `spec` list in `config/nvim/init.lua`.- Keep the ordering consistent with existing imports unless the plugin suggests a dependency order.5) Keymap collision check- Before adding keymaps, search existing mappings: - `rg -n "keymap|map\\(" config/nvim` - Also scan for `which-key` registrations if present.- If a recommended mapping conflicts, choose a nearby alternative under the same mnemonic prefix.- Use `desc` for every mapping.6) Configure defaults and options- Wire up plugin `setup()` with upstream defaults plus any repo-specific conventions.- Follow existing patterns (e.g., use `vim.keymap.set`, local helper functions).- Keep options and mappings minimal; avoid speculative tweaks.7) Validation- Ensure the plugin file is required by lazy.nvim and no syntax errors are introduced.- If the change impacts keymaps, mention any new keys in the response.## Repo conventions- Neovim config root: `config/nvim/`.- lazy.nvim bootstrap and imports live in `config/nvim/init.lua`.- Plugin config modules live in `config/nvim/lua/plugins/` and return a plugin spec.- Keep edits ASCII-only unless the file already uses non-ASCII.## Notes on keymaps- Prefer `<leader>` mappings and keep them consistent with existing prefixes.- Avoid overriding single-letter normal mode bindings unless the repo already does so.- When in doubt, add a `which-key` entry matching the new mapping.

Frequently asked questions