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)

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "nvim-agentic-companion",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Neovim companion that pairs the running editor (via mcp-neovim-server) with the official Claude Code IDE plugin (coder/claudecode.nvim). Provides an opinionated agent and skills for introspecting your live nvim state (buffers, keymaps, diagnostics, plugins), driving it on your behalf (open files, run keymaps, execute lua), and handing work cleanly to the in-editor Claude Code session for buffer edits.",
   "author": {
     "name": "oleks",

.mcp.json

@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "neovim": {
+      "command": "npx",
+      "args": ["-y", "mcp-neovim-server"],
+      "env": {
+        "NVIM_SOCKET_PATH": "/run/user/1000/nvim.sock"
+      }
+    }
+  }
+}

agents/companion.md

@@ -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.

skills/claude-code-handoff/SKILL.md

@@ -12,7 +12,7 @@ description: |
   buffer", "have Claude edit my file", "send this to Claude in nvim",
   "let Claude in the editor handle it".
 disable-model-invocation: false
-allowed-tools: Bash, Read, Skill, AskUserQuestion
+allowed-tools: Bash, Read, Skill, AskUserQuestion, mcp__neovim__*
 ---
 
 # claude-code-handoff — let the in-editor Claude do the editing

skills/editor-act/SKILL.md

@@ -12,7 +12,7 @@ description: |
   neo-tree", "run this command in my nvim", "go to next diagnostic",
   "save my buffer".
 disable-model-invocation: false
-allowed-tools: Bash, Read, Skill, AskUserQuestion
+allowed-tools: Bash, Read, Skill, AskUserQuestion, mcp__neovim__*
 ---
 
 # editor-act — do things in the user's nvim

skills/editor-introspect/SKILL.md

@@ -12,7 +12,7 @@ description: |
   "current selection", "what's the cursor on", "any diagnostics",
   "lualine theme actually applied".
 disable-model-invocation: false
-allowed-tools: Bash, Read
+allowed-tools: Bash, Read, Glob, Grep, mcp__neovim__*
 ---
 
 # editor-introspect — read the live nvim instance