Minitest Integration Lua
kokusenz/deltaview.nvim
This skill should be used when the user asks to write integration tests for a Neovim plugin using the MiniTest (mini.test) framework in Lua.
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.
Install Nvim Buffers
$ npx skills add scott-fryxell/brayness --skill nvim-buffers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scott-fryxell/brayness nvim-buffers --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/scott-fryxell/brayness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nvim-buffers .claude/skills/nvim-buffers && 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-buffers" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/nvim-buffers into .claude/skills/nvim-buffers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-buffers", 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/scott-fryxell/brayness/tree/main/skills/nvim-buffersType 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 scott-fryxell/brayness --skill nvim-buffers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scott-fryxell/brayness nvim-buffers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/nvim-buffers .agents/skills/nvim-buffers && 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-buffers" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/nvim-buffers into .agents/skills/nvim-buffers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-buffers", 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 scott-fryxell/brayness --skill nvim-buffers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scott-fryxell/brayness nvim-buffers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/nvim-buffers .cursor/skills/nvim-buffers && 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-buffers" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/nvim-buffers into .cursor/skills/nvim-buffers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-buffers", 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/scott-fryxell/brayness.git --path skills/nvim-buffers--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 scott-fryxell/brayness --skill nvim-buffers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scott-fryxell/brayness nvim-buffers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/nvim-buffers .gemini/skills/nvim-buffers && 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-buffers" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/nvim-buffers into .gemini/skills/nvim-buffers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-buffers", 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 scott-fryxell/brayness nvim-buffersInstalls 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 scott-fryxell/brayness --skill nvim-buffers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/nvim-buffers .github/skills/nvim-buffers && 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-buffers" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/nvim-buffers into .github/skills/nvim-buffers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-buffers", 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 scott-fryxell/brayness --skill nvim-buffers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scott-fryxell/brayness nvim-buffers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/nvim-buffers .opencode/skills/nvim-buffers && 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-buffers" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/nvim-buffers into .opencode/skills/nvim-buffers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-buffers", 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.
Facts
- Skill name
nvim-buffers- GitHub stars
- 125
- Token cost
- ~862 tokens
- SKILL.md length
- 380 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- The user asks to talk about what I have open
- SKILL.md covers Path, Shape, Coaching role (training wheels) and How to use
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Mentions a file theyre working on without naming it
What it does
Nvim Buffers is an agent skill from 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. Use when the user asks to "talk about what I have open", mentions a file they're working on without naming it, asks "how do I do X in vim", wants to learn git/search/navigation keys, or says they have files open and wants you to look at them.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Git and Lua. The repository describes itself as: A harness for the anxious digital mind. A safe place for creatives to keep their creative soul while exploring digital skills. The licence is MIT.
When your agent uses it
- The user asks to talk about what I have open
- Mentions a file theyre working on without naming it
- Asks how do I do X in vim
- Wants to learn git/search/navigation keys
Example prompts
- “talk about what I have open”
- “re working on without naming it, asks”
- “/nvim-buffers”
What it can do on your machine
Read from SKILL.md and the folder at commit 71f10e2. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nvim Buffers loads about 862 tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 380 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from scott-fryxell/brayness at commit 71f10e2, republished under its MIT licence (© scott-fryxell). 380 words, ~862 tokens.
Download SKILL.mdSave it as
.claude/skills/nvim-buffers/SKILL.md (or your agent's skills folder).- name
- nvim-buffers
- description
- 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. Use when the user asks to "talk about what I have open", mentions a file they're working on without naming it, asks "how do I do X in vim", wants to learn git/search/navigation keys, or says they have files open and wants you to look at them.
Nvim Buffers
The user runs LazyVim (~/.config/nvim, config in work/nvim). An autocmd in
lua/config/autocmds.lua writes the open real-file buffers to a state file on
every buffer change. Read that file with the read tool (or cat) to see what
they're working on.
Path
~/.local/state/nvim/open-buffers.json (vim.fn.stdpath("state") on macOS)
Shape
{
"current": "/abs/path/to/current/buffer",
"buffers": ["/abs/path/a", "/abs/path/b"],
"oil": [{ "dir": "/browsed/dir", "highlighted": "file.lua" }],
"view": {
"file": "/abs/path",
"line": 42,
"col": 3,
"visible": { "from_top": 30, "to_bottom": 60 },
"context": ["line 40", "line 41", "line 42"]
},
"updated": "2026-08-11T14:01:00"
}current- the active buffer; null or an oil dir if the active buffer is a terminal/oil/unnamed buffer.buffers- sorted list of all listed real-file buffers (term://, oil://, unnamed excluded).oil- directories currently browsed in oil (strips theoil://prefix), each withhighlighted- the entry name under the cursor in that oil window, or null if the oil buffer isn't shown in a window right now.view- the active window: file, cursor line/col, visible top/bottom lines, and a few lines ofcontextaround the cursor. Use this to answer "what's on my screen" / "what am I looking at" / "what should I press here".updated- when nvim last wrote it. Check it's fresh before trusting it.
Freshness: refreshed on buffer events + FocusGained + a 5s timer; external
file changes are reloaded (never clobbering unsaved edits).
Show full SKILL.md (200 more words)Show less
Coaching role (training wheels)
The user is still learning vim and runs hardtime.nvim, which blocks/"yells" at inefficient keys. Be the patient counterpart:
- When they ask how to do something, teach from THEIR config (
work/nvim/,lua/config/keymaps.lua,lua/plugins/*.lua), never generic defaults. - One key at a time, tied to what their
viewshows. - Read the state file first and confirm what they're looking at before answering, so hints land on their real cursor position.
- Their notable bindings:
-= Oil parent dir,<leader>gg/<leader>gG= gitui,gr= LSP references,<leader>fb= buffers (Snacks),<leader>fg= grep,gd/gi= LSP definition/implementation,K= hover. Git + search are LazyVim defaults (<leader>g...,<leader>f...).
How to use
- When the user mentions files "open in nvim", read this file first and confirm which files you're looking at before going deep - the user shouldn't have to name paths they already have in front of them.
- If the file is missing or stale (no update in a while), nvim may be closed or the autocmd may not have run; say so plainly instead of guessing.
- The write happens on
VimEnter/BufAdd/BufEnter/BufDelete/VimLeavePre. If the user just opened/closed a buffer and the file looks stale, they may need nvim to pick up the change (or nvim config may need a reload).
© scott-fryxell, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/nvim-buffers of scott-fryxell/brayness.
Open the folder on GitHubat commit 71f10e2
Compare with similar skills
Nvim Buffers 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 Buffers this skillscott-fryxell/brayness | 125 | — | ~862 | Automated safety check: Pass | MIT | |
| Minitest Integration Luakokusenz/deltaview.nvim | 127 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
More from scott-fryxell/brayness
All 27 skills in this repoLogo Finder
scott-fryxell/brayness
Find and install brand SVG logos via SVGL (https://svgl.app/) and Wikimedia Commons fallbacks into any project's static asset folder.
Test Coverage
scott-fryxell/brayness
Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.
Flexible Visual System
scott-fryxell/brayness
Derive a project's visual rules from its existing tokens, palette, type scale, logo, and icons (Intake), then generate raw SVG vector graphics from those rules as a small composable set (module…
Hyperframes
scott-fryxell/brayness
Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.
Motion Systems
scott-fryxell/brayness
A skill your agent uses when designing or implementing motion for web interfaces, including CSS transitions and keyframes, linear() easing design, transform strategy (translate/rotate vs…
Vue Inspect
scott-fryxell/brayness
Inspect live Vue 3 component state via agent-browser eval - no Devtools extension, no console.log.
Related
Categories
Questions about Nvim Buffers
What does Nvim Buffers do?
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. Nvim Buffers is an agent skill from 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.
When should I use Nvim Buffers?
Nvim Buffers fits situations like: the user asks to talk about what I have open; mentions a file theyre working on without naming it; asks how do I do X in vim; wants to learn git/search/navigation keys.
How do I install Nvim Buffers in Claude Code?
Run `npx skills add scott-fryxell/brayness --skill nvim-buffers -a claude-code`. Or copy the skill folder (skills/nvim-buffers in scott-fryxell/brayness) into .claude/skills/nvim-buffers in your project. Claude Code loads it when a task matches its description.
How do I install Nvim Buffers in Codex?
Run `npx skills add scott-fryxell/brayness --skill nvim-buffers -a codex`. Or copy the skill folder (skills/nvim-buffers in scott-fryxell/brayness) into .agents/skills/nvim-buffers in your project. Codex loads it when a task matches its description.
Can I use Nvim Buffers in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scott-fryxell/brayness --skill nvim-buffers -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-buffers, .gemini/skills/nvim-buffers, .github/skills/nvim-buffers and .opencode/skills/nvim-buffers in your project.
What does Nvim Buffers need to run?
SKILL.md names no scripts, command-line tools or credentials: Nvim Buffers is instructions for the agent only.
Does Nvim Buffers access the network?
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.
Is Nvim Buffers safe to install?
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.
What licence does Nvim Buffers use?
Nvim Buffers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nvim Buffers use?
About 862 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Nvim Buffers?
Skills that share tags, products or a category with Nvim Buffers: Minitest Integration Lua (kokusenz/deltaview.nvim, 127 stars), Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars) and Code Design Rationale Investigator (cursor/plugins, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nvim Buffers?
scott-fryxell (a GitHub user) maintains it in scott-fryxell/brayness, which has 125 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 28, 2026.
Source: scott-fryxell/brayness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.