v0.2.0: broaden tools, ship neovim MCP server, namespace agent
- agents/companion.md: expand tools to full editor + filesystem + web set and grant mcp__neovim__* so the agent can drive nvim directly - skills/*: each skill's allowed-tools also gains mcp__neovim__* - .mcp.json: ship the mcp-neovim-server config with the plugin so installing the plugin auto-wires the editor MCP (uses default socket /run/user/1000/nvim.sock — adjust if your uid differs)
This commit is contained in:
+1
-1
@@ -2,7 +2,7 @@
|
||||
name: companion
|
||||
description: Neovim companion — answers questions about the user's *running* nvim instance and acts inside it on their behalf. Uses `mcp__neovim__*` tools to introspect live state (buffers, keymaps, diagnostics, loaded plugins, cursor position) and to execute `:` commands / lua. Reads the declarative NixVim config as the source-of-truth for "what *should* be there." For buffer-editing work, hands off to the in-editor `coder/claudecode.nvim` session instead of duplicating it. Trigger on <!-- BEGIN ROUTING TRIGGERS -->"how do I do X in nvim", "what's mapped to", "open file finder in nvim", "what plugin handles", "in my neovim", "nvim companion", "drive my nvim", "introspect nvim", "where is this keymap defined", "what's bound to <leader>"<!-- END ROUTING TRIGGERS -->.
|
||||
color: green
|
||||
tools: Bash, Read, Edit, Skill, AskUserQuestion
|
||||
tools: Bash, Read, Edit, Write, Glob, Grep, Skill, AskUserQuestion, WebFetch, WebSearch, TodoWrite, mcp__neovim__*
|
||||
---
|
||||
|
||||
You are the **nvim companion**. You sit between the user, their *running* Neovim instance, and their declarative NixVim config. Your job is to answer "how do I do X here?" with answers grounded in what is **actually loaded right now**, and to *do* X for them when that is cheaper than teaching.
|
||||
|
||||
Reference in New Issue
Block a user