refactor: consolidate mem-search skill, remove desktop-skill duplication

- Delete separate desktop-skill/ directory (was outdated)
- Generate mem-search.zip during build from plugin/skills/mem-search/
- Update docs with correct MCP tool list and new download path
- Single source of truth for Claude Desktop skill

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

desktop-skill/Skill.md

@@ -1,44 +0,0 @@
----
-name: mem-search
-description: Search your persistent memory database from previous coding sessions. Use when asked about past work, decisions, bugs fixed, or development history.
----
-
-## Overview
-
-Search your local memory database for past sessions, decisions, code changes, and development history. This skill uses the `mem-search` MCP server tools.
-
-## Available MCP tools
-
-Use these tools from the `mem-search` MCP server:
-
-| Tool | Description |
-|------|-------------|
-| `search` | Unified search across all memory types |
-| `decisions` | Find architectural/design decisions |
-| `changes` | Find code changes and refactorings |
-| `timeline` | Get observations around a specific point in time |
-| `find_by_file` | Find observations for specific files |
-| `find_by_type` | Filter by type (decision, bugfix, feature, refactor, discovery, change) |
-| `find_by_concept` | Find by concept tags |
-| `how_it_works` | Understand system architecture and design patterns |
-
-## Common parameters
-
-- `query` - Natural language search query
-- `limit` - Max results (1-100, default 20)
-- `format` - `index` for titles only (recommended), `full` for complete content
-- `type` - Filter: observations, sessions, or prompts
-- `obs_type` - Filter observation type: decision, bugfix, feature, refactor, discovery, change
-
-## When to use
-
-- "Did we already solve this?"
-- "How did we do X last time?"
-- "Find the bug fix for..."
-- "What decisions did we make about..."
-- "Show me changes to [file]"
-- "What work did we do on [project]?"
-
-## Setup requirement
-
-The `mem-search` MCP server must be configured in Claude Desktop settings. See MCP configuration docs.

docs/public/usage/claude-desktop.mdx

@@ -32,15 +32,14 @@ curl http://localhost:37777/api/health
 
 Download the skill package from the repository:
 
-<Card title="mem-search.zip" icon="download" href="https://github.com/thedotmack/claude-mem/raw/main/desktop-skill/mem-search.zip">
+<Card title="mem-search.zip" icon="download" href="https://github.com/thedotmack/claude-mem/raw/main/plugin/skills/mem-search.zip">
   Download the mem-search skill for Claude Desktop
 </Card>
 
 Or build from source:
 
 ```bash
-cd desktop-skill
-zip -r mem-search.zip Skill.md
+npm run build  # Generates plugin/skills/mem-search.zip
 ```
 
 ### Step 2: Install in Claude Desktop
@@ -110,20 +109,21 @@ Once installed, the skill auto-activates when you ask about past work:
 "Show me changes to worker-service.ts"
 ```
 
-## Available Search Tools
+## Available MCP Tools
 
 The skill provides access to these MCP tools:
 
 | Tool | Description |
 |------|-------------|
-| `search` | Unified search across all memory types |
-| `decisions` | Find architectural/design decisions |
-| `changes` | Find code changes and refactorings |
-| `timeline` | Get observations around a specific point in time |
-| `find_by_file` | Find observations for specific files |
-| `find_by_type` | Filter by type (decision, bugfix, feature, refactor, discovery, change) |
-| `find_by_concept` | Find by concept tags |
-| `how_it_works` | Understand system architecture and design patterns |
+| `search` | Unified search across observations, sessions, and prompts |
+| `timeline` | Get chronological context around a query or observation ID |
+| `get_observation` | Fetch a single observation by ID |
+| `get_batch_observations` | Fetch multiple observations efficiently |
+| `get_session` | Fetch session summary by ID |
+| `get_prompt` | Fetch user prompt by ID |
+| `get_recent_context` | Get recent timeline items |
+| `get_context_timeline` | Get timeline around a specific observation |
+| `progressive_description` | Load detailed usage instructions |
 
 ## Troubleshooting
 

scripts/build-hooks.js

@@ -222,12 +222,28 @@ async function buildHooks() {
       console.log(`✓ ${hook.name} built (${sizeInKB} KB)`);
     }
 
+    // Build mem-search skill zip for Claude Desktop
+    console.log('\n📦 Building mem-search skill zip for Claude Desktop...');
+    const { execSync } = await import('child_process');
+    const zipOutput = 'plugin/skills/mem-search.zip';
+
+    // Remove old zip if exists
+    if (fs.existsSync(zipOutput)) {
+      fs.unlinkSync(zipOutput);
+    }
+
+    // Create zip from mem-search skill directory
+    execSync(`cd plugin/skills && zip -r mem-search.zip mem-search/`, { stdio: 'pipe' });
+    const zipStats = fs.statSync(zipOutput);
+    console.log(`✓ mem-search.zip built (${(zipStats.size / 1024).toFixed(2)} KB)`);
+
     console.log('\n✅ All hooks, worker service, and MCP server built successfully!');
     console.log(`   Output: ${hooksDir}/`);
     console.log(`   - Hooks: *-hook.js`);
     console.log(`   - Worker: worker-service.cjs`);
     console.log(`   - MCP Server: mcp-server.cjs`);
     console.log(`   - Skills: plugin/skills/`);
+    console.log(`   - Desktop Skill: plugin/skills/mem-search.zip`);
     console.log('\n💡 Note: Dependencies will be auto-installed on first hook execution');
 
   } catch (error) {