config/claude/skills/open-in-editor/SKILL.md
Use when the user says "open", "show me", "nvr", "open in editor", "open in nvr", "open in neovim", or wants to view a file in their editor rather than in the CLI. Also use proactively after creating or editing a file the user will want to review.
npx skillsauth add alexpopov/dots open-in-editorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Opens files in the user's neovim instance via nvr, using the tmux window name to find the correct socket.
# Open in new tab (default)
~/dots/bin/scripts/llm-open-nvr /path/to/file
# Open at specific line
~/dots/bin/scripts/llm-open-nvr --line 42 /path/to/file
# Open in split / vsplit
~/dots/bin/scripts/llm-open-nvr --split /path/to/file
~/dots/bin/scripts/llm-open-nvr --vsplit /path/to/file
# Diff two files
~/dots/bin/scripts/llm-open-nvr --diff file1 file2
# Send keystrokes (e.g. save current buffer)
~/dots/bin/scripts/llm-open-nvr --send ':w<CR>'
# Evaluate neovim expression
~/dots/bin/scripts/llm-open-nvr --expr 'expand("%:p")'
If the script errors with "No nvr socket", ask the user to start neovim in this tmux window by running the nvr shell function.
tools
Use this skill when working with the token-based Notion MCP servers (e.g. `mcp__notion-wife__API-*`) that wrap the raw Notion REST API — distinct from the OAuth `mcp__notion__*` server covered by notion-tricks. Covers native API JSON property shapes, the two-step page-then-content creation flow, and using `curl` with the `NOTION_TOKEN_*` env var to bypass MCP entirely for bulk/precise operations.
tools
Use this skill when adding, querying, or updating recipes in Cay's Notion (the `notion-wife` MCP). Covers the Recipes data source schema, tag conventions, the `recipes-helper.sh` script for fast tag/recipe operations via curl, and the rule that new tags must be confirmed with the user before creation.
tools
Walk through git commit history using git prev/next for interactive editing. Use when you need to amend multiple commits in a stack (e.g., adding Differential Revision lines, fixing commit messages, or making small edits across a commit series).
tools
Use when the user says "open", "show me", "nvr", "open in editor", "open in nvr", "open in neovim", or wants to view a file in their editor rather than in the CLI. Also use proactively after creating or editing a file the user will want to review.