Agentic Neovim Documentation
carlos-algms/agentic.nvim
A skill your agent uses when neovim documentation is needed for the current task or the user asks for specific neovim features or neovim lua apis.
Search and read Neovim's built-in :help documentation to look up API signatures, parameter types, option values, and event specifications from the user's installed runtime.
$ npx skills add S1M0N38/love2d.nvim --skill nvim-help -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install S1M0N38/love2d.nvim nvim-help --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nvim-help .claude/skills/nvim-help && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nvim-help" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-help into .claude/skills/nvim-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-help", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-helpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add S1M0N38/love2d.nvim --skill nvim-help -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install S1M0N38/love2d.nvim nvim-help --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/nvim-help .agents/skills/nvim-help && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nvim-help" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-help into .agents/skills/nvim-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-help", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add S1M0N38/love2d.nvim --skill nvim-help -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install S1M0N38/love2d.nvim nvim-help --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/nvim-help .cursor/skills/nvim-help && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nvim-help" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-help into .cursor/skills/nvim-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-help", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/S1M0N38/love2d.nvim.git --path .agents/skills/nvim-help--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add S1M0N38/love2d.nvim --skill nvim-help -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install S1M0N38/love2d.nvim nvim-help --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/nvim-help .gemini/skills/nvim-help && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nvim-help" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-help into .gemini/skills/nvim-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-help", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install S1M0N38/love2d.nvim nvim-helpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add S1M0N38/love2d.nvim --skill nvim-help -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/nvim-help .github/skills/nvim-help && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nvim-help" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-help into .github/skills/nvim-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-help", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add S1M0N38/love2d.nvim --skill nvim-help -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install S1M0N38/love2d.nvim nvim-help --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/nvim-help .opencode/skills/nvim-help && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nvim-help" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-help into .opencode/skills/nvim-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-help", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
nvim-helpSearch and read Neovim's built-in :help documentation to look up API signatures, parameter types, option values, and event specifications from the user's installed runtime.
Nvim Help is an agent skill from S1M0N38/love2d.nvim. Search and read Neovim's built-in :help documentation to look up API signatures, parameter types, option values, and event specifications from the user's installed runtime. Use when the user wants to consult reference material — function docs, help tags, option descriptions — not when they want to write, create, or debug something. Pairs with Context7 (neovim/neovim) for code examples; this skill provides exact local signatures and docs.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: ♡ A simple Neovim plugin to build games with LÖVE. The licence is MIT.
Read from SKILL.md and the folder at commit 2c31946. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and vimdoc).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Nvim Help loads about 681 tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 225 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from S1M0N38/love2d.nvim at commit 2c31946, republished under its MIT licence (© S1M0N38). 225 words, ~681 tokens.
.claude/skills/nvim-help/SKILL.md (or your agent's skills folder).Neovim's help docs are plain text in $VIMRUNTIME/doc/. Resolve the path once per session:
VIMRUNTIME=$(nvim -l /dev/stdin <<< 'io.write(vim.env.VIMRUNTIME)' 2>/dev/null)Tags are *like-this*, cross-references are |like-this|, code blocks are between > and < lines.
grep -i '<keyword>' "$VIMRUNTIME/doc/tags"Output: <tag>\t<help-file>\t<search-pattern>
When presenting tag search results, show the full path to each file.
Escape dots (\.) and parens (\(\)) for sed.
sed -n '/\*<exact-tag>\*/,/^====/p' "$VIMRUNTIME/doc/<help-file>"
# e.g. sed -n '/\*vim\.keymap\.set()\*/,/^====/p' "$VIMRUNTIME/doc/lua.txt"
# e.g. sed -n '/\*nvim_open_win()\*/,/^====/p' "$VIMRUNTIME/doc/api.txt"grep -rn '<pattern>' "$VIMRUNTIME/doc/"*.txtawk '/^===/{getline; print " L" NR ": " $0}' "$VIMRUNTIME/doc/<file>"awk -F'\t' '$2 == "<file>" {print $1}' "$VIMRUNTIME/doc/tags"ls "$VIMRUNTIME/doc/"*.txtAlways return the full raw help text — not a summary or paraphrase.
State the file path above the code block, then the raw vimdoc in a fenced block:
From $VIMRUNTIME/doc/lua.txt:
vim.keymap.set({modes}, {lhs}, {rhs}, {opts}) *vim.keymap.set()*
...Use separate code blocks for each help file, each with its own file path above.
When a keyword search returns multiple tags, show the most relevant section in full. Then list other relevant tags the user can request next.
If the Context7 MCP tool is available, query it for richer Lua code examples using
library ID neovim/neovim. This complements the exact parameter signatures from
local help docs.
© S1M0N38, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/nvim-help of S1M0N38/love2d.nvim.
Open the folder on GitHubat commit 2c31946
Nvim Help next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nvim Help this skillS1M0N38/love2d.nvim | 215 | — | ~681 | Automated safety check: Pass | MIT | |
| Agentic Neovim Documentationcarlos-algms/agentic.nvim | 640 | — | ~418 | Automated safety check: Pass | MIT | |
| Infant Looking Time DesignerNeuroAIHub/BrainPilot | 1.1k | — | ~4.5k | Automated safety check: Pass | AGPL-3.0 | |
| Nvim Buffersscott-fryxell/brayness | 124 | — | ~862 | Automated safety check: Pass | MIT | |
| Nvim Configwcygan/dotfiles | 196 | — | ~4.4k | Automated safety check: Pass | None | |
| Premiere Look Effectsayushozha/AdobePremiereProMCP | 119 | — | ~648 | Automated safety check: Pass | MIT |
carlos-algms/agentic.nvim
A skill your agent uses when neovim documentation is needed for the current task or the user asks for specific neovim features or neovim lua apis.
NeuroAIHub/BrainPilot
Designs habituation and preferential-looking paradigms with age-appropriate timing parameters and exclusion criteria
scott-fryxell/brayness
Read the user's currently open Neovim buffers and active view so you can discuss their actual working files and teach them their own nvim keymaps in context.
wcygan/dotfiles
Configure Neovim editor with init.lua, plugin management, LSP setup, keymaps, and options.
ayushozha/AdobePremiereProMCP
Build consistent, reversible visual effect recipes in Adobe Premiere Pro from effects confirmed as installed.
deanpeters/Product-Manager-Skills
Guides a three-phase canvas, looking inward, looking outward, then reframing, to produce an equity-aware problem statement.
S1M0N38/love2d.nvim
Create conventional commits for love2d.nvim that are compatible with release-please and follow SemVer.
S1M0N38/love2d.nvim
Write, update, and improve love2d.nvim help documentation (vimdoc) in doc/love2d.txt.
S1M0N38/love2d.nvim
Execute tests and diagnose failures for love2d.nvim. An agent skill from S1M0N38/love2d.nvim.
S1M0N38/love2d.nvim
Neovim plugin development best practices and patterns for love2d.nvim.
Search and read Neovim's built-in :help documentation to look up API signatures, parameter types, option values, and event specifications from the user's installed runtime. nvim. Search and read Neovim's built-in :help documentation to look up API signatures, parameter types, option values, and event specifications from the user's installed runtime.
Nvim Help fits situations like: the user wants to consult reference material — function docs; option descriptions — not when they want to write; debug something.
Run `npx skills add S1M0N38/love2d.nvim --skill nvim-help -a claude-code`. Or copy the skill folder (.agents/skills/nvim-help in S1M0N38/love2d.nvim) into .claude/skills/nvim-help in your project. Claude Code loads it when a task matches its description.
Run `npx skills add S1M0N38/love2d.nvim --skill nvim-help -a codex`. Or copy the skill folder (.agents/skills/nvim-help in S1M0N38/love2d.nvim) into .agents/skills/nvim-help in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add S1M0N38/love2d.nvim --skill nvim-help -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nvim-help, .gemini/skills/nvim-help, .github/skills/nvim-help and .opencode/skills/nvim-help in your project.
SKILL.md names no scripts, command-line tools or credentials: Nvim Help is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Nvim Help is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 681 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Nvim Help: Agentic Neovim Documentation (carlos-algms/agentic.nvim, 640 stars), Infant Looking Time Designer (NeuroAIHub/BrainPilot, 1.1k stars), Nvim Buffers (scott-fryxell/brayness, 124 stars) and Nvim Config (wcygan/dotfiles, 196 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
S1M0N38 (a GitHub user) maintains it in S1M0N38/love2d.nvim, which has 215 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on July 7, 2026.
Source: S1M0N38/love2d.nvim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.