feat(skills): Add screenshot and skill-creator, adopt Anthropic schema

- Add screenshot skill for finding and displaying recent screenshots
- Add skill-creator skill (official Anthropic guide)
- Adopt official Anthropic skill structure for all 40 skills
- Add scripts/, references/, assets/ directories to all skills
- Add installation scripts (install.ps1, install.sh)
- Update counts to 40 skills across docs
- Update naming conventions to require bundled resources
- Delete deprecated conclave and pulse commands

All skills now follow consistent structure with bundled resources
(scripts for executable code, references for docs, assets for
templates), even when directories are currently empty.

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

.claude/settings.local.json

@@ -1,108 +1,158 @@
 {
   "permissions": {
     "allow": [
+      "WebSearch",
+      "WebFetch(domain:*)",
+      "Skill(*)",
+      "SlashCommand(*)",
+      "mcp__vibe_kanban__*",
+      "mcp__claude-in-chrome__*",
       "Bash(git:*)",
-      "Bash(ls:*)",
-      "Bash(mkdir:*)",
-      "Bash(cat:*)",
-      "Bash(wc:*)",
-      "Bash(tree:*)",
-      "Bash(curl:*)",
+      "Bash(gh:*)",
+      "Bash(lazygit:*)",
       "Bash(rg:*)",
       "Bash(fd:*)",
       "Bash(fzf:*)",
-      "Bash(z:*)",
-      "Bash(zoxide:*)",
-      "Bash(br:*)",
-      "Bash(broot:*)",
-      "Bash(ast-grep:*)",
-      "Bash(sg:*)",
+      "Bash(grep:*)",
+      "Bash(find:*)",
+      "Bash(which:*)",
+      "Bash(where:*)",
+      "Bash(command:*)",
+      "Bash(cat:*)",
       "Bash(bat:*)",
+      "Bash(head:*)",
+      "Bash(tail:*)",
+      "Bash(less:*)",
+      "Bash(more:*)",
+      "Bash(ls:*)",
       "Bash(eza:*)",
-      "Bash(delta:*)",
-      "Bash(difft:*)",
+      "Bash(dir:*)",
+      "Bash(tree:*)",
+      "Bash(broot:*)",
+      "Bash(br:*)",
+      "Bash(mkdir:*)",
+      "Bash(cp:*)",
+      "Bash(mv:*)",
+      "Bash(rm:*)",
+      "Bash(touch:*)",
+      "Bash(chmod:*)",
+      "Bash(echo:*)",
+      "Bash(printf:*)",
+      "Bash(wc:*)",
+      "Bash(sort:*)",
+      "Bash(uniq:*)",
+      "Bash(cut:*)",
+      "Bash(awk:*)",
+      "Bash(sed:*)",
+      "Bash(sd:*)",
+      "Bash(tr:*)",
+      "Bash(xargs:*)",
+      "Bash(tee:*)",
       "Bash(jq:*)",
       "Bash(yq:*)",
-      "Bash(sd:*)",
-      "Bash(lazygit:*)",
-      "Bash(gh:*)",
-      "Bash(tokei:*)",
-      "Bash(uv:*)",
-      "Bash(just:*)",
+      "Bash(curl:*)",
+      "Bash(wget:*)",
       "Bash(http:*)",
-      "Bash(procs:*)",
-      "Bash(hyperfine:*)",
-      "Bash(npm:*)",
-      "Bash(node:*)",
+      "Bash(firecrawl:*)",
+      "Bash(markitdown:*)",
       "Bash(python:*)",
+      "Bash(python3:*)",
       "Bash(pip:*)",
-      "Bash(powershell -Command:*)",
-      "Bash(powershell.exe:*)",
-      "Bash(bash:*)",
-      "Bash(chmod:*)",
-      "Bash(xargs:*)",
-      "Bash(command -v:*)",
-      "Bash(brew:*)",
-      "Bash(tldr:*)",
+      "Bash(pip3:*)",
+      "Bash(uv:*)",
+      "Bash(pytest:*)",
+      "Bash(node:*)",
+      "Bash(npm:*)",
+      "Bash(npx:*)",
+      "Bash(pnpm:*)",
+      "Bash(yarn:*)",
+      "Bash(bun:*)",
+      "Bash(just:*)",
+      "Bash(make:*)",
+      "Bash(cargo:*)",
+      "Bash(go:*)",
+      "Bash(rustc:*)",
+      "Bash(docker:*)",
+      "Bash(docker-compose:*)",
+      "Bash(tokei:*)",
+      "Bash(hyperfine:*)",
       "Bash(dust:*)",
+      "Bash(procs:*)",
       "Bash(btm:*)",
       "Bash(bottom:*)",
-      "Bash(firecrawl:*)",
-      "Bash(gemini:*)",
+      "Bash(delta:*)",
+      "Bash(difft:*)",
+      "Bash(diff:*)",
+      "Bash(ast-grep:*)",
+      "Bash(sg:*)",
+      "Bash(tldr:*)",
+      "Bash(man:*)",
+      "Bash(z:*)",
+      "Bash(zoxide:*)",
+      "Bash(cd:*)",
+      "Bash(pwd:*)",
+      "Bash(env:*)",
+      "Bash(export:*)",
+      "Bash(source:*)",
+      "Bash(set:*)",
+      "Bash(test:*)",
+      "Bash(ps:*)",
+      "Bash(kill:*)",
+      "Bash(pkill:*)",
+      "Bash(pgrep:*)",
+      "Bash(whoami:*)",
+      "Bash(hostname:*)",
+      "Bash(uname:*)",
+      "Bash(date:*)",
+      "Bash(time:*)",
+      "Bash(ping:*)",
+      "Bash(netstat:*)",
+      "Bash(ss:*)",
+      "Bash(ip:*)",
+      "Bash(ifconfig:*)",
+      "Bash(systeminfo:*)",
+      "Bash(tar:*)",
+      "Bash(zip:*)",
+      "Bash(unzip:*)",
+      "Bash(gzip:*)",
+      "Bash(gunzip:*)",
       "Bash(claude:*)",
+      "Bash(gemini:*)",
       "Bash(codex:*)",
       "Bash(perplexity:*)",
       "Bash(grok:*)",
       "Bash(glm:*)",
-      "Bash(source:*)",
-      "Bash(md5:*)",
-      "Bash(test:*)",
-      "Bash(head:*)",
-      "WebSearch",
-      "WebFetch(domain:www.anthropic.com)",
-      "SlashCommand(/pulse:*)",
-      "WebFetch(domain:simonwillison.net)",
-      "Skill(sync)",
-      "Bash(grep:*)",
-      "Bash(~/.zshrc)",
-      "Bash(env)",
-      "Bash(security find-generic-password:*)",
-      "Bash(security find-generic-password -s \"GEMINI_API_KEY\" -w)",
-      "Bash(~/.env)",
-      "Bash(source /Users/mack/.env)",
-      "Bash(pip3 install:*)",
-      "Bash(/usr/bin/python3:*)",
-      "Bash(/opt/homebrew/bin/python3:*)",
-      "Bash(/opt/homebrew/bin/pip3 install:*)",
-      "WebFetch(domain:docs.z.ai)",
-      "Bash(droid --version:*)",
-      "Bash(droid --help:*)",
-      "Bash(opencode --version:*)",
-      "Bash(droid exec \"What is 2+2? One word.\")",
-      "Bash(opencode --help:*)",
-      "Bash(opencode run \"What is 2+2? One word.\")",
-      "Bash(opencode auth:*)",
-      "Bash(opencode models:*)",
-      "Bash(opencode run:*)",
-      "Bash(markitdown --help:*)",
-      "Bash(where markitdown:*)",
-      "Bash(markitdown:*)"
+      "Bash(droid:*)",
+      "Bash(opencode:*)",
+      "Bash(powershell:*)",
+      "Bash(pwsh:*)",
+      "Bash(cmd:*)",
+      "Bash(bash:*)",
+      "Bash(sh:*)",
+      "Bash(zsh:*)",
+      "Bash(canvas-tui:*)",
+      "Bash(brew:*)",
+      "Bash(apt:*)",
+      "Bash(apt-get:*)",
+      "Bash(choco:*)",
+      "Bash(scoop:*)",
+      "Bash(winget:*)",
+      "Bash(\"E:\\\\Downloads\\\\[TEMPLATE] example-2 Framework - Concierge AI.md\")",
+      "Bash(powershell -ExecutionPolicy Bypass -File \"./scripts/install.ps1\")"
     ],
     "deny": [],
     "ask": [
+      "Bash(rm -rf:*)",
       "Bash(git reset --hard:*)",
-      "Bash(git checkout -- :*)",
       "Bash(git clean -f:*)",
-      "Bash(git stash drop:*)",
-      "Bash(git stash clear:*)",
-      "Bash(git restore --worktree:*)",
       "Bash(git push --force:*)",
       "Bash(git push -f:*)",
-      "Bash(git push origin --force:*)",
-      "Bash(git push origin -f:*)",
       "Bash(git branch -D:*)"
     ]
   },
   "hooks": {},
-  "outputStyle": "Vesper"
+  "outputStyle": "Vesper",
+  "env": {
+    "ENABLE_TOOL_SEARCH": "true"
+  }
 }

AGENTS.md

@@ -5,7 +5,7 @@
 This is **claude-mods** - a collection of custom extensions for Claude Code:
 - **22 expert agents** for specialized domains (React, Python, Go, Rust, AWS, etc.)
 - **3 commands** for session management (/sync, /save) and experimental features (/canvas)
-- **38 skills** for CLI tools, patterns, workflows, and development tasks
+- **40 skills** for CLI tools, patterns, workflows, and development tasks
 - **Custom output styles** for response personality (e.g., Vesper)
 
 ## Installation

README.md

@@ -9,7 +9,7 @@ Claude Code is brilliant - until your session ends and it forgets everything. Yo
 
 **claude-mods fixes that.** It's a plugin that adds session persistence, expert-level domain knowledge, and the modern CLI tools that Claude should've been using all along. Save your work with `/save`, pick up where you left off with `/sync`, and let 22 specialized agents handle everything from React hooks to PostgreSQL optimization. No more "I don't have access to that" - just a smarter, more capable coding assistant that actually remembers.
 
-**22 agents. 38 skills. 3 commands. One install.**
+**22 agents. 40 skills. 3 commands. One install.**
 
 ## Why claude-mods?
 
@@ -100,6 +100,27 @@ Install modern CLI tools (fd, rg, bat, etc.) for better performance:
 ./tools/install-unix.sh
 ```
 
+## Skill Architecture
+
+All skills follow [Anthropic's official pattern](https://github.com/anthropics/skills) with consistent structure:
+
+```
+skill-name/
+├── SKILL.md              # Core workflow (< 500 lines)
+├── scripts/              # Executable code (optional)
+├── references/           # Documentation loaded as needed (optional)
+└── assets/               # Output templates/files (optional)
+```
+
+**Progressive Loading:**
+1. Metadata (name + description) - Always in context (~100 words)
+2. SKILL.md body - Loaded when skill triggers (<5k words)
+3. Bundled resources - Loaded only when Claude needs them
+
+All skills have the complete directory structure, even if `scripts/`, `references/`, or `assets/` are currently empty. This ensures consistency and makes it easy to add bundled resources later.
+
+See [skill-creator](skills/skill-creator/) for the complete guide.
+
 ## What's Included
 
 ### Commands
@@ -140,10 +161,12 @@ Install modern CLI tools (fd, rg, bat, etc.) for better performance:
 | [project-planner](skills/project-planner/) | Track stale plans, suggest session commands |
 | [python-env](skills/python-env/) | Fast Python environment management with uv |
 | [task-runner](skills/task-runner/) | Run project commands with just |
+| [screenshot](skills/screenshot/) | Find and display recent screenshots from common screenshot directories |
 
 #### Development Skills
 | Skill | Description |
 |-------|-------------|
+| [skill-creator](skills/skill-creator/) | Guide for creating effective skills with specialized knowledge, workflows, and tool integrations. |
 | [explain](skills/explain/) | Deep explanation of complex code, files, or concepts. Routes to expert agents. |
 | [spawn](skills/spawn/) | Generate PhD-level expert agent prompts for Claude Code. |
 | [atomise](skills/atomise/) | Atom of Thoughts reasoning - decompose problems into atomic units. |

canvas-tui/README.md

@@ -8,14 +8,19 @@ Works with any terminal that supports split panes: **Warp**, **tmux**, **iTerm2*
 
 ## Installation
 
+### From claude-mods repo (local)
+
 ```bash
-npm install -g @claude-mods/canvas-tui
+cd claude-mods/canvas-tui
+npm link
 ```
 
-Or run directly with npx:
+Then use `canvas-tui` from anywhere on your machine.
+
+### From npm (coming soon)
 
 ```bash
-npx @claude-mods/canvas-tui --watch
+npm install -g @claude-mods/canvas-tui
 ```
 
 ## Usage

commands/canvas.md

@@ -68,12 +68,9 @@ Claude: I'll help you draft that email. Starting canvas mode...
 [Output:]
 Canvas initialized with email template.
 
-To see live preview, open Warp and:
+To see live preview:
 1. Press Cmd+Shift+D (or Ctrl+Shift+D on Windows) to split pane
-2. In the new pane, run: npx @claude-mods/canvas-tui --watch
-
-Or use the launch configuration:
-  warp://launch/claude-canvas
+2. In the new pane, run: canvas-tui --watch
 ```
 
 ### Writing Content
@@ -169,7 +166,7 @@ Write `.claude/canvas/meta.json`:
 Canvas ready with email template.
 
 Setup (one-time):
-  npm install -g @claude-mods/canvas-tui
+  cd claude-mods/canvas-tui && npm link
 
 To view canvas:
   1. Split your terminal (Cmd+Shift+D in Warp)
@@ -303,7 +300,7 @@ windows:
           panes:
             - is_focused: true
             - commands:
-                - exec: "npx @claude-mods/canvas-tui --watch"
+                - exec: "canvas-tui --watch"
 ```
 
 **Usage:**
@@ -314,13 +311,10 @@ windows:
 ### Canvas TUI Package
 
 ```bash
-# Install globally
-npm install -g @claude-mods/canvas-tui
-
-# Or run via npx
-npx @claude-mods/canvas-tui --watch
+# Link globally from claude-mods repo
+cd claude-mods/canvas-tui && npm link
 
-# Options
+# Then use from anywhere
 canvas-tui --watch              # Watch .claude/canvas/content.md
 canvas-tui --file ./draft.md    # Watch specific file
 canvas-tui --help               # Show help

commands/conclave.md

@@ -1,56 +0,0 @@
----
-description: "[DEPRECATED] Use the standalone Conclave CLI instead: https://github.com/0xDarkMatter/conclave"
----
-
-# Conclave - DEPRECATED
-
-> **This command has been deprecated.** Conclave is now a standalone CLI tool.
-
----
-
-## Migration
-
-The `/conclave` command has been replaced by the **Conclave CLI** - a standalone, universal multi-LLM consensus tool that works from any context (Claude Code, OpenCode, Gemini CLI, terminal, CI/CD).
-
-### Install
-
-```bash
-# macOS/Linux
-curl -fsSL https://raw.githubusercontent.com/0xDarkMatter/conclave/main/install.sh | bash
-
-# Or with Go
-go install github.com/0xDarkMatter/conclave@latest
-```
-
-### Usage
-
-```bash
-# Query multiple LLMs with a judge for synthesis
-conclave gemini,openai,glm "Is this code secure?" --judge claude
-
-# Pipe file content
-cat src/auth.ts | conclave gemini,openai "Review this" --judge claude
-
-# Multiple files
-conclave gemini,openai "Compare these" --file a.go --file b.go --judge claude
-
-# Raw results (no synthesis)
-conclave gemini,openai "Analyze this" --no-judge --json
-```
-
-### Why the change?
-
-The original `/conclave` command was 877 lines of documentation that Claude had to parse and manually execute every time. The new CLI:
-
-- **Self-contained** - Handles orchestration and synthesis internally
-- **Universal** - Works from any LLM tool, not just Claude Code
-- **Faster** - Single binary, parallel execution, structured output
-- **Configurable judge** - Any LLM can synthesize the verdict
-
----
-
-## Repository
-
-**GitHub:** [https://github.com/0xDarkMatter/conclave](https://github.com/0xDarkMatter/conclave)
-
-See the repository for full documentation, configuration options, and provider support.

commands/pulse.md

@@ -1,33 +0,0 @@
----
-description: "**[MOVED]** Claude Code ecosystem news digest. Now at github.com/0xDarkMatter/pulse"
----
-
-# Pulse
-
-> **This command has been moved to a standalone repository.**
-
-## New Location
-
-**Repository:** [github.com/0xDarkMatter/pulse](https://github.com/0xDarkMatter/pulse)
-
-## Installation
-
-```bash
-# Clone the repo
-git clone https://github.com/0xDarkMatter/pulse.git
-
-# Copy the command to your Claude Code commands
-cp pulse/COMMAND.md ~/.claude/commands/pulse.md
-```
-
-## Why It Moved
-
-Pulse generates persistent state files and news digests that don't belong in a shared plugin repo. As a standalone tool, it can:
-
-- Track its own state without cluttering claude-mods
-- Have dedicated issue tracking for source curation
-- Evolve independently from the plugin release cycle
-
----
-
-*See the [Pulse repository](https://github.com/0xDarkMatter/pulse) for full documentation.*

commands/save.md

@@ -1,5 +1,5 @@
 ---
-description: "Save session state - persist TodoWrite tasks, plan content, and git context. Complementary to /sync."
+description: "Save session state - persist tasks (via TaskList), plan content, and git context. Complementary to /sync."
 ---
 
 # Save - Session State Persistence
@@ -10,7 +10,7 @@ Persist your current session state for later restoration with `/sync`.
 
 $ARGUMENTS
 
-- No args: Save current state (TodoWrite, plan, git context)
+- No args: Save current state (tasks, plan, git context)
 - `"notes"`: Save with descriptive notes
 - `--archive`: Archive current plan to `PLAN-<date>.md`, then save fresh
 
@@ -18,7 +18,7 @@ $ARGUMENTS
 
 | Data | Source | Destination |
 |------|--------|-------------|
-| TodoWrite tasks | Current session | `.claude/session-cache.json` |
+| Tasks | TaskList API | `.claude/session-cache.json` |
 | Plan content | Conversation context | `docs/PLAN.md` |
 | Git context | `git status/log` | `.claude/session-cache.json` |
 | User notes | Command argument | `.claude/session-cache.json` |
@@ -26,12 +26,21 @@ $ARGUMENTS
 
 ## Execution
 
-### Step 1: Capture TodoWrite State
+### Step 1: Capture Task State
 
-Read current TodoWrite tasks and categorize:
-- Completed tasks
-- In-progress tasks
-- Pending tasks
+Use TaskList and TaskGet to capture full task data:
+
+```
+1. Call TaskList to get all task IDs and summaries
+2. For each task, call TaskGet to retrieve:
+   - subject (title)
+   - description (full details)
+   - status (pending, in_progress, completed)
+   - blockedBy (dependency IDs)
+3. Store as array with index-based dependency mapping
+```
+
+Note: Tasks do not persist across sessions automatically. This is why /save exists.
 
 ### Step 2: Capture Plan Content
 
@@ -57,13 +66,31 @@ git status --porcelain | wc -l
 **`.claude/session-cache.json`** (machine-readable):
 ```json
 {
-  "version": "2.0",
+  "version": "3.0",
   "timestamp": "2025-12-13T10:30:00Z",
-  "todos": {
-    "completed": ["Set up OAuth credentials"],
-    "in_progress": ["Fix callback URL handling"],
-    "pending": ["Add token refresh"]
-  },
+  "tasks": [
+    {
+      "subject": "Set up OAuth credentials",
+      "description": "Configure Google OAuth app in GCP console",
+      "activeForm": "Setting up OAuth credentials",
+      "status": "completed",
+      "blockedBy": []
+    },
+    {
+      "subject": "Fix callback URL handling",
+      "description": "OAuth callback URL mismatch in production config",
+      "activeForm": "Fixing callback URL handling",
+      "status": "in_progress",
+      "blockedBy": [0]
+    },
+    {
+      "subject": "Add token refresh",
+      "description": "Implement JWT refresh token rotation",
+      "activeForm": "Adding token refresh",
+      "status": "pending",
+      "blockedBy": [1]
+    }
+  ],
   "plan": {
     "file": "docs/PLAN.md",
     "goal": "Add user authentication with OAuth2",

commands/sync.md

@@ -25,7 +25,7 @@ $ARGUMENTS
     |      |
     |      +- Read project context (README, AGENTS, CLAUDE)
     |      +- Read saved state (.claude/session-cache.json)
-    |      +- Restore TodoWrite tasks
+    |      +- Restore tasks via TaskCreate
     |      +- Read plan (docs/PLAN.md)
     |      +- Show unified status
     |      +- Suggest next action
@@ -76,9 +76,23 @@ Read these files simultaneously (skip any that don't exist):
 ### Step 2: Restore Session State
 
 If `.claude/session-cache.json` exists:
-1. Parse saved TodoWrite tasks
-2. Restore to TodoWrite (completed, in_progress, pending)
-3. Note time since last save
+
+```
+1. Parse saved tasks array from JSON
+2. For each task, call TaskCreate with:
+   - subject
+   - description
+   - activeForm
+3. Build ID mapping: savedIndex → newTaskId
+4. For each task with blockedBy, call TaskUpdate:
+   - Map saved indices to new task IDs
+   - Set blockedBy relationships
+5. For each task, call TaskUpdate to set status:
+   - "completed" | "in_progress" | "pending"
+6. Note time since last save
+```
+
+Note: Tasks do not persist across sessions automatically, which is why this restore step is needed.
 
 ### Step 3: Parallel Globs
 
@@ -376,6 +390,30 @@ Options:
   2. Start fresh: /save --archive
 ```
 
+### Legacy v2.0 schema (todos object)
+```
+Info: Found v2.0 session-cache.json (legacy format)
+
+Converting todos to tasks:
+  - 3 completed → tasks with status: "completed"
+  - 1 in_progress → tasks with status: "in_progress"
+  - 2 pending → tasks with status: "pending"
+
+Note: Legacy format lacks descriptions and dependencies.
+Consider running /save to upgrade to v3.0 schema.
+```
+
+**Migration logic:**
+```
+if version == "2.0" and "todos" in json:
+    for task in todos.completed:
+        TaskCreate(subject=task, description="(migrated from v2.0)", status="completed")
+    for task in todos.in_progress:
+        TaskCreate(subject=task, description="(migrated from v2.0)", status="in_progress")
+    for task in todos.pending:
+        TaskCreate(subject=task, description="(migrated from v2.0)", status="pending")
+```
+
 ### Branch changed since save
 ```
 Warning: Branch changed since save

docs/DASH.md

@@ -9,7 +9,7 @@
 |----------|-------|-------|
 | 🤖 **Agents** | 21 | 7,552 |
 | ⚡ **Skills** | 16 | 3,850 |
-| 🔧 **Commands** | 10 | 3,776 |
+| 🔧 **Commands** | 9 | 3,720 |
 | 📏 **Rules** | 1 | 113 |
 | 🧩 **Templates** | 2 | — |
 
@@ -80,15 +80,14 @@
 | Command | Purpose |
 |---------|---------|
 | 🔧 `/sync` | Session bootstrap, restore state, show status |
-| 🔧 `/save` | Save session state (TodoWrite, plan, git context) |
+| 🔧 `/save` | Save session state (tasks, plan, git context) |
 | 🔧 `/review` | Code review staged changes |
 | 🔧 `/testgen` | Generate tests with expert routing |
 | 🔧 `/explain` | Deep code/concept explanation |
 | 🔧 `/spawn` | Generate expert agents |
-| 🔧 `/conclave` | Summon external LLMs (Gemini, OpenAI, Perplexity) for consensus |
 | 🔧 `/atomise` | Atom of Thoughts reasoning with confidence tracking |
-| 🔧 `/pulse` | Claude Code ecosystem news digest |
 | 🔧 `/setperms` | Set tool permissions |
+| 🔧 `/introspect` | Analyze previous session logs |
 
 ---
 

docs/PLAN.md

@@ -13,7 +13,7 @@
 | Component | Count | Notes |
 |-----------|-------|-------|
 | Agents | 22 | Domain experts (Python, Go, Rust, React, etc.) |
-| Skills | 38 | Pattern libraries, CLI tools, workflows, dev tasks |
+| Skills | 40 | Pattern libraries, CLI tools, workflows, dev tasks |
 | Commands | 3 | Session management (sync, save) + experimental (canvas) |
 | Rules | 5 | CLI tools, thinking, commit style, naming, skill-agent-updates |
 | Output Styles | 1 | Vesper personality |

docs/RESERVED-COMMANDS.md

@@ -0,0 +1,63 @@
+# Reserved Command Names
+
+**Source:** https://code.claude.com/docs/en/interactive-mode#built-in-commands
+
+These are Claude Code's built-in slash commands. **Do not create skills or commands with these names** to avoid conflicts.
+
+## Built-in Commands (Reserved)
+
+| Command | Purpose |
+|---------|---------|
+| `/clear` | Clear conversation history |
+| `/compact` | Compact conversation with optional focus instructions |
+| `/config` | Open Settings interface (Config tab) |
+| `/context` | Visualize current context usage |
+| `/cost` | Show token usage statistics |
+| `/doctor` | Check installation health |
+| `/exit` | Exit the REPL |
+| `/export` | Export conversation to file or clipboard |
+| `/help` | Get usage help |
+| `/init` | Initialize project with CLAUDE.md |
+| `/mcp` | Manage MCP server connections |
+| `/memory` | Edit CLAUDE.md memory files |
+| `/model` | Select or change AI model |
+| `/permissions` | View or update permissions |
+| `/plan` | Enter plan mode |
+| `/rename` | Rename current session |
+| `/resume` | Resume a conversation |
+| `/rewind` | Rewind conversation and/or code |
+| `/stats` | Visualize daily usage and history |
+| `/status` | Show version, model, account info |
+| `/statusline` | Set up status line UI |
+| `/tasks` | List and manage background tasks |
+| `/teleport` | Resume remote session from claude.ai |
+| `/theme` | Change color theme |
+| `/todos` | List current TODO items |
+| `/usage` | Show plan usage limits |
+| `/vim` | Enable vim-style editing |
+
+## Reserved Patterns
+
+Also avoid:
+- `/mcp__*` - Reserved for MCP server prompts
+- Single-letter commands - May conflict with future shortcuts
+
+## Our Safe Names
+
+Current claude-mods skills/commands (verified no conflicts):
+
+**Commands:**
+- atomise, canvas, explain, introspect, save, setperms, spawn, sync
+
+**Skills:**
+- review, testgen, code-stats, doc-scanner, file-search, find-replace, git-workflow, tool-discovery, task-runner, python-env, structural-search, data-processing, markitdown, etc.
+
+## Before Adding New Skills
+
+1. Check this list
+2. Check https://code.claude.com/docs/en/interactive-mode#built-in-commands for updates
+3. Avoid generic names that Anthropic might add (e.g., `/test`, `/run`, `/build`, `/deploy`)
+
+## Last Updated
+
+2025-01-23

rules/commit-style.md

@@ -65,9 +65,9 @@ dependencies were specified. Now handles arrays properly.
 ### Breaking Change
 
 ```
-refactor(commands): Rename /delegate to /conclave
+refactor(commands): Rename /todos to /tasks
 
-BREAKING CHANGE: /delegate command no longer exists. Use /conclave.
+BREAKING CHANGE: /todos command no longer exists. Use /tasks.
 ```
 
 ### Documentation Update

rules/naming-conventions.md

@@ -37,9 +37,14 @@ model: sonnet|opus|haiku     # Recommended model
 
 ### Skills (`/skills`)
 
+All skills follow the official Anthropic pattern with bundled resources:
+
 ```
-{topic}-patterns/skill.md    # Pattern collections
-{tool-name}/skill.md         # Tool-specific knowledge
+{skill-name}/
+├── SKILL.md              # Core workflow
+├── scripts/              # Executable code (optional)
+├── references/           # Documentation (optional)
+└── assets/               # Output files (optional)
 ```
 
 | Pattern | Example | Notes |
@@ -62,6 +67,11 @@ related-skills: [<skill-names>]
 ---
 ```
 
+**Directory Structure:**
+- All skills MUST include `scripts/`, `references/`, and `assets/` directories
+- Directories may be empty if not currently used
+- Ensures consistency and future extensibility
+
 ### Commands (`/commands`)
 
 ```

scripts/install.ps1

@@ -0,0 +1,133 @@
+<#
+.SYNOPSIS
+    Install claude-mods extensions to ~/.claude/
+
+.DESCRIPTION
+    Copies commands, skills, agents, and rules to the global Claude Code config.
+    Handles cleanup of deprecated items and command-to-skill migrations.
+
+.NOTES
+    Run from the claude-mods directory:
+    .\scripts\install.ps1
+#>
+
+$ErrorActionPreference = "Stop"
+
+Write-Host "================================================================" -ForegroundColor Cyan
+Write-Host "           claude-mods Installer (Windows)                      " -ForegroundColor Cyan
+Write-Host "================================================================" -ForegroundColor Cyan
+Write-Host ""
+
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+$projectRoot = Split-Path -Parent $scriptDir
+$claudeDir = "$env:USERPROFILE\.claude"
+
+# Ensure ~/.claude directories exist
+$dirs = @("commands", "skills", "agents", "rules", "output-styles")
+foreach ($dir in $dirs) {
+    $path = Join-Path $claudeDir $dir
+    if (-not (Test-Path $path)) {
+        New-Item -ItemType Directory -Path $path -Force | Out-Null
+        Write-Host "  Created $path" -ForegroundColor Green
+    }
+}
+
+# =============================================================================
+# DEPRECATED ITEMS - Remove these from user config
+# =============================================================================
+$deprecated = @(
+    "$claudeDir\commands\review.md",
+    "$claudeDir\commands\testgen.md",
+    "$claudeDir\commands\conclave.md",
+    "$claudeDir\commands\pulse.md",
+    "$claudeDir\skills\conclave"
+)
+
+Write-Host "Cleaning up deprecated items..." -ForegroundColor Yellow
+foreach ($item in $deprecated) {
+    if (Test-Path $item) {
+        Remove-Item -Path $item -Recurse -Force
+        Write-Host "  Removed: $item" -ForegroundColor Red
+    }
+}
+Write-Host ""
+
+# =============================================================================
+# COMMANDS - Only copy commands that have not been migrated to skills
+# =============================================================================
+Write-Host "Installing commands..." -ForegroundColor Cyan
+
+$skipCommands = @("review.md", "testgen.md")
+
+$commandsDir = Join-Path $projectRoot "commands"
+Get-ChildItem -Path $commandsDir -Filter "*.md" | ForEach-Object {
+    if ($_.Name -notin $skipCommands -and $_.Name -notlike "archive*") {
+        Copy-Item $_.FullName -Destination "$claudeDir\commands\" -Force
+        Write-Host "  $($_.Name)" -ForegroundColor Green
+    }
+}
+Write-Host ""
+
+# =============================================================================
+# SKILLS - Copy all skill directories
+# =============================================================================
+Write-Host "Installing skills..." -ForegroundColor Cyan
+
+$skillsDir = Join-Path $projectRoot "skills"
+Get-ChildItem -Path $skillsDir -Directory | ForEach-Object {
+    $dest = "$claudeDir\skills\$($_.Name)"
+    if (Test-Path $dest) {
+        Remove-Item -Path $dest -Recurse -Force
+    }
+    Copy-Item $_.FullName -Destination $dest -Recurse -Force
+    Write-Host "  $($_.Name)/" -ForegroundColor Green
+}
+Write-Host ""
+
+# =============================================================================
+# AGENTS - Copy all agent files
+# =============================================================================
+Write-Host "Installing agents..." -ForegroundColor Cyan
+
+$agentsDir = Join-Path $projectRoot "agents"
+Get-ChildItem -Path $agentsDir -Filter "*.md" | ForEach-Object {
+    Copy-Item $_.FullName -Destination "$claudeDir\agents\" -Force
+    Write-Host "  $($_.Name)" -ForegroundColor Green
+}
+Write-Host ""
+
+# =============================================================================
+# RULES - Copy all rule files
+# =============================================================================
+Write-Host "Installing rules..." -ForegroundColor Cyan
+
+$rulesDir = Join-Path $projectRoot "rules"
+Get-ChildItem -Path $rulesDir -Filter "*.md" | ForEach-Object {
+    Copy-Item $_.FullName -Destination "$claudeDir\rules\" -Force
+    Write-Host "  $($_.Name)" -ForegroundColor Green
+}
+Write-Host ""
+
+# =============================================================================
+# OUTPUT STYLES - Copy all output style files
+# =============================================================================
+Write-Host "Installing output styles..." -ForegroundColor Cyan
+
+$stylesDir = Join-Path $projectRoot "output-styles"
+if (Test-Path $stylesDir) {
+    Get-ChildItem -Path $stylesDir -Filter "*.md" | ForEach-Object {
+        Copy-Item $_.FullName -Destination "$claudeDir\output-styles\" -Force
+        Write-Host "  $($_.Name)" -ForegroundColor Green
+    }
+}
+Write-Host ""
+
+# =============================================================================
+# SUMMARY
+# =============================================================================
+Write-Host "================================================================" -ForegroundColor Cyan
+Write-Host "  Installation complete!" -ForegroundColor Green
+Write-Host "================================================================" -ForegroundColor Cyan
+Write-Host ""
+Write-Host "Restart Claude Code to load the new extensions." -ForegroundColor Yellow
+Write-Host ""

scripts/install.sh

@@ -0,0 +1,148 @@
+#!/usr/bin/env bash
+#
+# claude-mods Installer (Linux/macOS)
+# Copies commands, skills, agents, and rules to ~/.claude/
+# Handles cleanup of deprecated items and command-to-skill migrations.
+#
+# Usage: ./scripts/install.sh
+
+set -e
+
+BLUE='\033[0;34m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+RED='\033[0;31m'
+NC='\033[0m'
+
+echo -e "${BLUE}╔══════════════════════════════════════════════════════════════╗${NC}"
+echo -e "${BLUE}║           claude-mods Installer (Unix)                       ║${NC}"
+echo -e "${BLUE}╚══════════════════════════════════════════════════════════════╝${NC}"
+echo ""
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
+CLAUDE_DIR="$HOME/.claude"
+
+# Ensure ~/.claude directories exist
+for dir in commands skills agents rules output-styles; do
+    mkdir -p "$CLAUDE_DIR/$dir"
+done
+
+# =============================================================================
+# DEPRECATED ITEMS - Remove these from user's config
+# =============================================================================
+echo -e "${YELLOW}Cleaning up deprecated items...${NC}"
+
+deprecated_items=(
+    # Removed commands (migrated to skills or deleted)
+    "$CLAUDE_DIR/commands/review.md"      # Migrated to skill
+    "$CLAUDE_DIR/commands/testgen.md"     # Migrated to skill
+    "$CLAUDE_DIR/commands/conclave.md"    # Deprecated
+    "$CLAUDE_DIR/commands/pulse.md"       # Now a skill only
+
+    # Removed skills
+    "$CLAUDE_DIR/skills/conclave"         # Deprecated
+)
+
+for item in "${deprecated_items[@]}"; do
+    if [ -e "$item" ]; then
+        rm -rf "$item"
+        echo -e "  ${RED}Removed: $item${NC}"
+    fi
+done
+echo ""
+
+# =============================================================================
+# COMMANDS - Only copy commands that haven't been migrated to skills
+# =============================================================================
+echo -e "${BLUE}Installing commands...${NC}"
+
+# Commands that should NOT be copied (migrated to skills)
+skip_commands=("review.md" "testgen.md")
+
+for file in "$PROJECT_ROOT/commands"/*.md; do
+    [ -f "$file" ] || continue
+    filename=$(basename "$file")
+
+    # Skip migrated commands
+    skip=false
+    for skip_cmd in "${skip_commands[@]}"; do
+        if [ "$filename" = "$skip_cmd" ]; then
+            skip=true
+            break
+        fi
+    done
+
+    # Skip archive directory contents
+    [[ "$file" == *"/archive/"* ]] && continue
+
+    if [ "$skip" = false ]; then
+        cp "$file" "$CLAUDE_DIR/commands/"
+        echo -e "  ${GREEN}$filename${NC}"
+    fi
+done
+echo ""
+
+# =============================================================================
+# SKILLS - Copy all skill directories
+# =============================================================================
+echo -e "${BLUE}Installing skills...${NC}"
+
+for skill_dir in "$PROJECT_ROOT/skills"/*/; do
+    [ -d "$skill_dir" ] || continue
+    skill_name=$(basename "$skill_dir")
+
+    # Remove existing and copy fresh
+    rm -rf "$CLAUDE_DIR/skills/$skill_name"
+    cp -r "$skill_dir" "$CLAUDE_DIR/skills/"
+    echo -e "  ${GREEN}$skill_name/${NC}"
+done
+echo ""
+
+# =============================================================================
+# AGENTS - Copy all agent files
+# =============================================================================
+echo -e "${BLUE}Installing agents...${NC}"
+
+for file in "$PROJECT_ROOT/agents"/*.md; do
+    [ -f "$file" ] || continue
+    cp "$file" "$CLAUDE_DIR/agents/"
+    echo -e "  ${GREEN}$(basename "$file")${NC}"
+done
+echo ""
+
+# =============================================================================
+# RULES - Copy all rule files
+# =============================================================================
+echo -e "${BLUE}Installing rules...${NC}"
+
+for file in "$PROJECT_ROOT/rules"/*.md; do
+    [ -f "$file" ] || continue
+    cp "$file" "$CLAUDE_DIR/rules/"
+    echo -e "  ${GREEN}$(basename "$file")${NC}"
+done
+echo ""
+
+# =============================================================================
+# OUTPUT STYLES - Copy all output style files
+# =============================================================================
+echo -e "${BLUE}Installing output styles...${NC}"
+
+if [ -d "$PROJECT_ROOT/output-styles" ]; then
+    for file in "$PROJECT_ROOT/output-styles"/*.md; do
+        [ -f "$file" ] || continue
+        cp "$file" "$CLAUDE_DIR/output-styles/"
+        echo -e "  ${GREEN}$(basename "$file")${NC}"
+    done
+fi
+echo ""
+
+# =============================================================================
+# SUMMARY
+# =============================================================================
+echo -e "${BLUE}════════════════════════════════════════════════════════════════${NC}"
+echo -e "  ${GREEN}Installation complete!${NC}"
+echo -e "${BLUE}════════════════════════════════════════════════════════════════${NC}"
+echo ""
+echo -e "${YELLOW}Restart Claude Code to load the new extensions.${NC}"
+echo ""

skills/project-planner/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: project-planner
 description: "Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning."
-allowed-tools: "Read Glob TodoWrite"
+allowed-tools: "Read Glob TaskList TaskCreate"
 ---
 
 # Project Planner Skill

skills/screenshot/SKILL.md

@@ -0,0 +1,201 @@
+---
+name: screenshot
+description: "Find and display recent screenshots. Triggers: screenshot, check screenshot, show screenshot, recent screenshot, last screenshot."
+compatibility: "Windows, macOS, Linux"
+allowed-tools: "Bash, Glob, Read"
+depends-on: []
+related-skills: []
+---
+
+# Screenshot Viewer
+
+Quickly find and display recent screenshots from common screenshot directories.
+
+## Usage
+
+```
+/screenshot          # Show last 5 screenshots (default)
+/screenshot 1        # Show only the most recent
+/screenshot 10       # Show last 10 screenshots
+```
+
+## How It Works
+
+1. **Auto-detect screenshot locations** - Checks common directories in this order:
+   - Windows: `Pictures\Screenshots`, ShareX, Greenshot, OneDrive\Screenshots
+   - macOS: `~/Desktop`, `~/Screenshots`
+   - Linux: `~/Pictures`, `~/Desktop`
+
+2. **Find recent screenshots** - Uses Glob to find image files (png, jpg, jpeg, gif, webp) sorted by modification time
+
+3. **Display visually** - Uses Read tool to show screenshots so you can analyze and discuss them
+
+## Implementation
+
+### Step 1: Detect Screenshot Directory
+
+Check common locations and use the first one that exists:
+
+**Windows:**
+```bash
+# Priority order
+1. %USERPROFILE%\Pictures\Screenshots           # Windows 11 native
+2. %USERPROFILE%\Documents\ShareX\Screenshots   # ShareX
+3. %USERPROFILE%\Pictures\Greenshot             # Greenshot
+4. %USERPROFILE%\OneDrive\Pictures\Screenshots  # OneDrive sync
+5. %USERPROFILE%\Pictures                       # Fallback
+```
+
+**macOS:**
+```bash
+1. ~/Desktop              # Default macOS location
+2. ~/Screenshots          # Custom folder
+3. ~/Pictures             # Fallback
+```
+
+**Linux:**
+```bash
+1. ~/Pictures/Screenshots # GNOME/KDE
+2. ~/Pictures             # Fallback
+3. ~/Desktop              # Alternative
+```
+
+### Step 2: Find Recent Screenshots
+
+Use Glob to find image files, sorted by modification time:
+
+```bash
+# Find all image files in screenshot directory
+fd -e png -e jpg -e jpeg -e gif -e webp . "$SCREENSHOT_DIR" --max-depth 1 -t f --exec stat --format="%Y %n" {} \; | sort -rn | head -n $COUNT
+```
+
+Or using native tools:
+
+**Windows (PowerShell):**
+```powershell
+Get-ChildItem "$env:USERPROFILE\Pictures\Screenshots" -File |
+  Where-Object {$_.Extension -match '\.(png|jpg|jpeg|gif|webp)$'} |
+  Sort-Object LastWriteTime -Descending |
+  Select-Object -First $COUNT
+```
+
+**Unix (Bash):**
+```bash
+find "$SCREENSHOT_DIR" -maxdepth 1 -type f \( -iname "*.png" -o -iname "*.jpg" -o -iname "*.jpeg" -o -iname "*.gif" -o -iname "*.webp" \) -printf '%T@ %p\n' | sort -rn | head -n $COUNT | cut -d' ' -f2-
+```
+
+### Step 3: Display Screenshots
+
+For each screenshot found, use Read tool to display it visually:
+
+```
+Found 3 screenshots in C:\Users\...\Pictures\Screenshots
+
+1. Screenshot_2026-01-28_14-32-10.png (45 KB, 2 minutes ago)
+[Read tool displays image visually]
+
+2. Screenshot_2026-01-28_14-15-03.png (128 KB, 19 minutes ago)
+[Read tool displays image visually]
+
+3. Screenshot_2026-01-28_13-58-22.png (67 KB, 36 minutes ago)
+[Read tool displays image visually]
+```
+
+## Arguments
+
+| Argument | Default | Description |
+|----------|---------|-------------|
+| `count` | 5 | Number of screenshots to show |
+
+**Examples:**
+- `/screenshot` - Show last 5
+- `/screenshot 1` - Show only most recent
+- `/screenshot 10` - Show last 10
+
+## Output Format
+
+```
+Screenshots from [directory]
+
+## Screenshot 1 of N
+**File**: [filename]
+**Size**: [size] KB
+**Modified**: [time ago]
+
+[Visual display of screenshot via Read tool]
+
+## Screenshot 2 of N
+...
+```
+
+## Edge Cases
+
+### No Screenshot Directory Found
+
+```
+No screenshot directory found.
+
+Checked locations:
+  - C:\Users\...\Pictures\Screenshots (not found)
+  - C:\Users\...\Documents\ShareX\Screenshots (not found)
+  - C:\Users\...\Pictures\Greenshot (not found)
+
+To use this skill, either:
+  1. Take a screenshot (Win+Shift+S on Windows)
+  2. Specify a custom directory: /screenshot --dir="C:\path\to\screenshots"
+```
+
+### No Screenshots Found
+
+```
+No screenshots found in C:\Users\...\Pictures\Screenshots
+
+Directory exists but contains no image files (.png, .jpg, .jpeg, .gif, .webp)
+```
+
+### Count Exceeds Available
+
+```
+Found 3 screenshots (requested 10)
+
+Showing all 3:
+[displays all available screenshots]
+```
+
+## Performance
+
+- **Fast** - Uses filesystem tools (fd or native) instead of reading all files
+- **Efficient** - Only reads the exact number requested
+- **Token-conscious** - Large screenshots are automatically resized by Read tool
+
+## Custom Directory (Optional)
+
+To use a non-standard directory:
+
+```
+/screenshot 5 --dir="C:\Custom\Path"
+```
+
+Or create a project-specific config in `.claude/screenshot.json`:
+
+```json
+{
+  "directory": "C:\\Custom\\Screenshots",
+  "default_count": 3,
+  "file_extensions": ["png", "jpg", "webp"]
+}
+```
+
+## Integration
+
+Works well with:
+- `/explain` - Explain what's in the screenshot
+- `/review` - Review UI/code in screenshot
+- Browser automation tools - Verify screenshot matches expected state
+
+## Notes
+
+- Respects modification time (newest first)
+- Ignores subdirectories (only top-level)
+- Supports common image formats (png, jpg, jpeg, gif, webp)
+- Works across Windows, macOS, Linux with platform-specific paths

skills/skill-creator/LICENSE.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

skills/skill-creator/SKILL.md

@@ -0,0 +1,356 @@
+---
+name: skill-creator
+description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
+license: Complete terms in LICENSE.txt
+---
+
+# Skill Creator
+
+This skill provides guidance for creating effective skills.
+
+## About Skills
+
+Skills are modular, self-contained packages that extend Claude's capabilities by providing
+specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
+domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
+equipped with procedural knowledge that no model can fully possess.
+
+### What Skills Provide
+
+1. Specialized workflows - Multi-step procedures for specific domains
+2. Tool integrations - Instructions for working with specific file formats or APIs
+3. Domain expertise - Company-specific knowledge, schemas, business logic
+4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
+
+## Core Principles
+
+### Concise is Key
+
+The context window is a public good. Skills share the context window with everything else Claude needs: system prompt, conversation history, other Skills' metadata, and the actual user request.
+
+**Default assumption: Claude is already very smart.** Only add context Claude doesn't already have. Challenge each piece of information: "Does Claude really need this explanation?" and "Does this paragraph justify its token cost?"
+
+Prefer concise examples over verbose explanations.
+
+### Set Appropriate Degrees of Freedom
+
+Match the level of specificity to the task's fragility and variability:
+
+**High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.
+
+**Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.
+
+**Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.
+
+Think of Claude as exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom).
+
+### Anatomy of a Skill
+
+Every skill consists of a required SKILL.md file and optional bundled resources:
+
+```
+skill-name/
+├── SKILL.md (required)
+│   ├── YAML frontmatter metadata (required)
+│   │   ├── name: (required)
+│   │   └── description: (required)
+│   └── Markdown instructions (required)
+└── Bundled Resources (optional)
+    ├── scripts/          - Executable code (Python/Bash/etc.)
+    ├── references/       - Documentation intended to be loaded into context as needed
+    └── assets/           - Files used in output (templates, icons, fonts, etc.)
+```
+
+#### SKILL.md (required)
+
+Every SKILL.md consists of:
+
+- **Frontmatter** (YAML): Contains `name` and `description` fields. These are the only fields that Claude reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.
+- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).
+
+#### Bundled Resources (optional)
+
+##### Scripts (`scripts/`)
+
+Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
+
+- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
+- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
+- **Benefits**: Token efficient, deterministic, may be executed without loading into context
+- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments
+
+##### References (`references/`)
+
+Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
+
+- **When to include**: For documentation that Claude should reference while working
+- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
+- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
+- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed
+- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
+- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
+
+##### Assets (`assets/`)
+
+Files not intended to be loaded into context, but rather used within the output Claude produces.
+
+- **When to include**: When the skill needs files that will be used in the final output
+- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
+- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
+- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context
+
+#### What to Not Include in a Skill
+
+A skill should only contain essential files that directly support its functionality. Do NOT create extraneous documentation or auxiliary files, including:
+
+- README.md
+- INSTALLATION_GUIDE.md
+- QUICK_REFERENCE.md
+- CHANGELOG.md
+- etc.
+
+The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxilary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.
+
+### Progressive Disclosure Design Principle
+
+Skills use a three-level loading system to manage context efficiently:
+
+1. **Metadata (name + description)** - Always in context (~100 words)
+2. **SKILL.md body** - When skill triggers (<5k words)
+3. **Bundled resources** - As needed by Claude (Unlimited because scripts can be executed without reading into context window)
+
+#### Progressive Disclosure Patterns
+
+Keep SKILL.md body to the essentials and under 500 lines to minimize context bloat. Split content into separate files when approaching this limit. When splitting out content into other files, it is very important to reference them from SKILL.md and describe clearly when to read them, to ensure the reader of the skill knows they exist and when to use them.
+
+**Key principle:** When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details (patterns, examples, configuration) into separate reference files.
+
+**Pattern 1: High-level guide with references**
+
+```markdown
+# PDF Processing
+
+## Quick start
+
+Extract text with pdfplumber:
+[code example]
+
+## Advanced features
+
+- **Form filling**: See [FORMS.md](FORMS.md) for complete guide
+- **API reference**: See [REFERENCE.md](REFERENCE.md) for all methods
+- **Examples**: See [EXAMPLES.md](EXAMPLES.md) for common patterns
+```
+
+Claude loads FORMS.md, REFERENCE.md, or EXAMPLES.md only when needed.
+
+**Pattern 2: Domain-specific organization**
+
+For Skills with multiple domains, organize content by domain to avoid loading irrelevant context:
+
+```
+bigquery-skill/
+├── SKILL.md (overview and navigation)
+└── reference/
+    ├── finance.md (revenue, billing metrics)
+    ├── sales.md (opportunities, pipeline)
+    ├── product.md (API usage, features)
+    └── marketing.md (campaigns, attribution)
+```
+
+When a user asks about sales metrics, Claude only reads sales.md.
+
+Similarly, for skills supporting multiple frameworks or variants, organize by variant:
+
+```
+cloud-deploy/
+├── SKILL.md (workflow + provider selection)
+└── references/
+    ├── aws.md (AWS deployment patterns)
+    ├── gcp.md (GCP deployment patterns)
+    └── azure.md (Azure deployment patterns)
+```
+
+When the user chooses AWS, Claude only reads aws.md.
+
+**Pattern 3: Conditional details**
+
+Show basic content, link to advanced content:
+
+```markdown
+# DOCX Processing
+
+## Creating documents
+
+Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).
+
+## Editing documents
+
+For simple edits, modify the XML directly.
+
+**For tracked changes**: See [REDLINING.md](REDLINING.md)
+**For OOXML details**: See [OOXML.md](OOXML.md)
+```
+
+Claude reads REDLINING.md or OOXML.md only when the user needs those features.
+
+**Important guidelines:**
+
+- **Avoid deeply nested references** - Keep references one level deep from SKILL.md. All reference files should link directly from SKILL.md.
+- **Structure longer reference files** - For files longer than 100 lines, include a table of contents at the top so Claude can see the full scope when previewing.
+
+## Skill Creation Process
+
+Skill creation involves these steps:
+
+1. Understand the skill with concrete examples
+2. Plan reusable skill contents (scripts, references, assets)
+3. Initialize the skill (run init_skill.py)
+4. Edit the skill (implement resources and write SKILL.md)
+5. Package the skill (run package_skill.py)
+6. Iterate based on real usage
+
+Follow these steps in order, skipping only if there is a clear reason why they are not applicable.
+
+### Step 1: Understanding the Skill with Concrete Examples
+
+Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
+
+To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
+
+For example, when building an image-editor skill, relevant questions include:
+
+- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
+- "Can you give some examples of how this skill would be used?"
+- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
+- "What would a user say that should trigger this skill?"
+
+To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
+
+Conclude this step when there is a clear sense of the functionality the skill should support.
+
+### Step 2: Planning the Reusable Skill Contents
+
+To turn concrete examples into an effective skill, analyze each example by:
+
+1. Considering how to execute on the example from scratch
+2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
+
+Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
+
+1. Rotating a PDF requires re-writing the same code each time
+2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
+
+Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
+
+1. Writing a frontend webapp requires the same boilerplate HTML/React each time
+2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
+
+Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
+
+1. Querying BigQuery requires re-discovering the table schemas and relationships each time
+2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
+
+To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
+
+### Step 3: Initializing the Skill
+
+At this point, it is time to actually create the skill.
+
+Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
+
+When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
+
+Usage:
+
+```bash
+scripts/init_skill.py <skill-name> --path <output-directory>
+```
+
+The script:
+
+- Creates the skill directory at the specified path
+- Generates a SKILL.md template with proper frontmatter and TODO placeholders
+- Creates example resource directories: `scripts/`, `references/`, and `assets/`
+- Adds example files in each directory that can be customized or deleted
+
+After initialization, customize or remove the generated SKILL.md and example files as needed.
+
+### Step 4: Edit the Skill
+
+When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Include information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
+
+#### Learn Proven Design Patterns
+
+Consult these helpful guides based on your skill's needs:
+
+- **Multi-step processes**: See references/workflows.md for sequential workflows and conditional logic
+- **Specific output formats or quality standards**: See references/output-patterns.md for template and example patterns
+
+These files contain established best practices for effective skill design.
+
+#### Start with Reusable Skill Contents
+
+To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
+
+Added scripts must be tested by actually running them to ensure there are no bugs and that the output matches what is expected. If there are many similar scripts, only a representative sample needs to be tested to ensure confidence that they all work while balancing time to completion.
+
+Any example files and directories not needed for the skill should be deleted. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.
+
+#### Update SKILL.md
+
+**Writing Guidelines:** Always use imperative/infinitive form.
+
+##### Frontmatter
+
+Write the YAML frontmatter with `name` and `description`:
+
+- `name`: The skill name
+- `description`: This is the primary triggering mechanism for your skill, and helps Claude understand when to use the skill.
+  - Include both what the Skill does and specific triggers/contexts for when to use it.
+  - Include all "when to use" information here - Not in the body. The body is only loaded after triggering, so "When to Use This Skill" sections in the body are not helpful to Claude.
+  - Example description for a `docx` skill: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
+
+Do not include any other fields in YAML frontmatter.
+
+##### Body
+
+Write instructions for using the skill and its bundled resources.
+
+### Step 5: Packaging a Skill
+
+Once development of the skill is complete, it must be packaged into a distributable .skill file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:
+
+```bash
+scripts/package_skill.py <path/to/skill-folder>
+```
+
+Optional output directory specification:
+
+```bash
+scripts/package_skill.py <path/to/skill-folder> ./dist
+```
+
+The packaging script will:
+
+1. **Validate** the skill automatically, checking:
+
+   - YAML frontmatter format and required fields
+   - Skill naming conventions and directory structure
+   - Description completeness and quality
+   - File organization and resource references
+
+2. **Package** the skill if validation passes, creating a .skill file named after the skill (e.g., `my-skill.skill`) that includes all files and maintains the proper directory structure for distribution. The .skill file is a zip file with a .skill extension.
+
+If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
+
+### Step 6: Iterate
+
+After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
+
+**Iteration workflow:**
+
+1. Use the skill on real tasks
+2. Notice struggles or inefficiencies
+3. Identify how SKILL.md or bundled resources should be updated
+4. Implement changes and test again

templates/conclave.yaml

@@ -1,61 +0,0 @@
-# ~/.claude/conclave.yaml
-# Configuration for /conclave command - Multi-LLM task dispatch
-
-# API Keys (preferred over environment variables)
-# Uncomment and add your keys:
-# api_keys:
-#   gemini: "your-gemini-api-key"
-#   openai: "your-openai-api-key"
-#   anthropic: "your-anthropic-api-key"
-#   perplexity: "your-perplexity-api-key"
-
-# Provider Configuration
-providers:
-  gemini:
-    model: gemini-2.5-pro        # Recommended: 1M context, best for code analysis
-    # model: gemini-2.5-flash    # Faster, still 1M context
-    # model: gemini-3-pro        # Requires Ultra subscription (waitlist for free tier)
-    default_flags:
-      - --output-format
-      - text
-    # IMPORTANT: Use stdin piping for file content, not @file.md syntax
-    # Example: cat file.md | gemini -m gemini-2.5-pro "prompt"
-
-  openai:
-    model: gpt-5.2          # Strongest (requires ChatGPT login)
-    # model: gpt-5.1-codex-max   # Default for Pro subscription
-    # model: gpt-4o              # API key only (pay per token)
-    auth: chatgpt                 # chatgpt (subscription) or api-key
-    default_flags:
-      - --json
-
-  claude:
-    model: sonnet                 # Best balance of speed and capability
-    # model: opus                 # Most capable - complex reasoning
-    # model: haiku                # Fastest - quick analysis
-    default_flags:
-      - --print
-      - --output-format
-      - text
-    # Uses ANTHROPIC_API_KEY env var or existing Claude Code login
-
-  perplexity:
-    model: sonar-pro             # Best balance: complex queries, more citations
-    # model: sonar               # Fast, cost-effective for quick facts
-    # model: sonar-reasoning     # Multi-step problem solving
-    # model: sonar-reasoning-pro # Deep reasoning (DeepSeek-R1 based)
-    default_flags: []
-    # Unique: returns web citations with every response
-    # Get API key at: https://www.perplexity.ai/settings/api
-
-# Consensus Mode (--all) Settings
-consensus:
-  providers: [gemini, openai, claude]  # Which providers participate
-  # providers: [gemini, openai, claude, perplexity]  # Include Perplexity for web-grounded consensus
-  require_consensus: true              # All must agree for YES/NO verdicts
-
-# Default behavior
-defaults:
-  provider: gemini                # Default provider when none specified
-  output: text                    # text or json
-  verbosity: default              # brief, default, or detailed

templates/settings.local.json

@@ -42,5 +42,8 @@
     "deny": [],
     "ask": []
   },
-  "hooks": {}
+  "hooks": {},
+  "env": {
+    "ENABLE_TOOL_SEARCH": "true"
+  }
 }

tools/README.md

@@ -165,9 +165,8 @@ perplexity --list-models
 # Set API key (get from https://www.perplexity.ai/settings/api)
 export PERPLEXITY_API_KEY="your-key-here"
 
-# Or add to ~/.claude/conclave.yaml:
-# api_keys:
-#   perplexity: "your-key-here"
+# Add to shell profile for persistence:
+# echo 'export PERPLEXITY_API_KEY="your-key-here"' >> ~/.bashrc
 ```
 
 ---

tools/perplexity.py

@@ -12,7 +12,7 @@ Usage:
     perplexity --json "query" > output.json
 
 Environment:
-    PERPLEXITY_API_KEY - API key (or set in ~/.claude/conclave.yaml)
+    PERPLEXITY_API_KEY - API key (required)
     PERPLEXITY_VERBOSE - Show token usage when set
 """
 import argparse
@@ -34,42 +34,8 @@ DEFAULT_MODEL = "sonar-pro"
 
 
 def get_api_key():
-    """Get API key from env or config file."""
-    import re
-
-    # Try environment variable first
-    key = os.getenv("PERPLEXITY_API_KEY")
-    if key:
-        return key
-
-    # Try ~/.claude/conclave.yaml
-    config_path = os.path.expanduser("~/.claude/conclave.yaml")
-    if os.path.exists(config_path):
-        try:
-            with open(config_path, encoding="utf-8") as f:
-                content = f.read()
-            # Look for perplexity key in api_keys section
-            # Parse the api_keys block and find perplexity
-            in_api_keys = False
-            for line in content.split('\n'):
-                stripped = line.strip()
-                # Detect api_keys section
-                if stripped.startswith('api_keys:'):
-                    in_api_keys = True
-                    continue
-                # Exit section on non-indented line (new section)
-                if in_api_keys and stripped and not line.startswith(' ') and not line.startswith('\t'):
-                    if not stripped.startswith('#'):
-                        in_api_keys = False
-                # Look for perplexity key within api_keys section
-                if in_api_keys and 'perplexity:' in stripped.lower():
-                    match = re.search(r'perplexity:\s*["\']?([^"\'\n#]+)', stripped, re.IGNORECASE)
-                    if match:
-                        return match.group(1).strip()
-        except Exception:
-            pass
-
-    return None
+    """Get API key from environment variable."""
+    return os.getenv("PERPLEXITY_API_KEY")
 
 
 def query_perplexity(prompt, model=DEFAULT_MODEL, system_prompt=None, recency=None, domains=None):
@@ -79,7 +45,7 @@ def query_perplexity(prompt, model=DEFAULT_MODEL, system_prompt=None, recency=No
         sys.exit(
             "Error: PERPLEXITY_API_KEY not set.\n"
             "Set via: export PERPLEXITY_API_KEY='your-key'\n"
-            "Or add to ~/.claude/conclave.yaml under api_keys:"
+            "Get key from: https://www.perplexity.ai/settings/api"
         )
 
     messages = []
@@ -196,7 +162,7 @@ Examples:
   perplexity --domains "github.com,docs.python.org" "Python asyncio best practices"
 
 Environment:
-  PERPLEXITY_API_KEY  API key (required, or set in ~/.claude/conclave.yaml)
+  PERPLEXITY_API_KEY  API key (required)
   PERPLEXITY_VERBOSE  Show token usage when set
 """,
     )