claude-code-skill
Control Claude Code via MCP protocol. Execute commands, read/write files, search code, and use all Claude Code tools programmatically with agent team support.
What this skill does
# Claude Code Skill
Control Claude Code via MCP (Model Context Protocol). This skill unleashes the full power of Claude Code for openclaw agents, including persistent sessions, agent teams, and advanced tool control.
## โก Quick Start
```bash
# Start a persistent Claude session for your project
claude-code-skill session-start myproject -d ~/project \
--permission-mode plan \
--allowed-tools "Bash,Read,Edit,Write,Glob,Grep" \
--max-budget 2.00
# Send a complex task (Claude will autonomously use tools)
claude-code-skill session-send myproject "Find all TODO comments and create GitHub issues" --stream
# Check progress
claude-code-skill session-status myproject
```
## ๐ฏ When to Use This Skill
### Use Persistent Sessions When:
- โ
Multi-step tasks requiring multiple tool calls
- โ
Iterative development (write code โ test โ fix โ repeat)
- โ
Long conversations needing full context
- โ
Agent needs to work autonomously
- โ
You want streaming real-time feedback
### Use Direct MCP Tools When:
- โ
Single command execution
- โ
Quick file read/write
- โ
One-off searches
- โ
No context needed between operations
## ๐ Command Reference
### Basic MCP Operations
```bash
# Connect to Claude Code MCP
claude-code-skill connect
claude-code-skill status
claude-code-skill tools
# Direct tool calls (no persistent session)
claude-code-skill bash "npm test"
claude-code-skill read /path/to/file.ts
claude-code-skill glob "**/*.ts" -p ~/project
claude-code-skill grep "TODO" -p ~/project -c
claude-code-skill call Write -a '{"file_path":"/tmp/test.txt","content":"Hello"}'
# Disconnect
claude-code-skill disconnect
```
### Persistent Sessions (Agent Loop)
#### Starting Sessions
```bash
# Basic start
claude-code-skill session-start myproject -d ~/project
# With custom API endpoint (for Gemini/GPT proxy)
claude-code-skill session-start gemini-task -d ~/project \
--base-url http://127.0.0.1:8082 \
--model gemini-2.0-flash
# With permission mode (plan = preview changes before applying)
claude-code-skill session-start review -d ~/project --permission-mode plan
# With tool whitelist (auto-approve these tools)
claude-code-skill session-start safe -d ~/project \
--allowed-tools "Bash(git:*),Read,Glob,Grep"
# With budget limit
claude-code-skill session-start limited -d ~/project --max-budget 1.50
# Full configuration
claude-code-skill session-start advanced -d ~/project \
--permission-mode acceptEdits \
--allowed-tools "Bash,Read,Edit,Write" \
--disallowed-tools "Task" \
--max-budget 5.00 \
--model claude-opus-4-5 \
--append-system-prompt "Always write tests" \
--add-dir "/tmp,/var/log"
```
**Permission Modes:**
| Mode | Description |
|------|-------------|
| `acceptEdits` | Auto-accept file edits (default) |
| `plan` | Preview changes before applying |
| `default` | Ask for each operation |
| `bypassPermissions` | Skip all prompts (dangerous!) |
| `delegate` | Delegate decisions to parent |
| `dontAsk` | Never ask, reject by default |
#### Sending Messages
```bash
# Basic send (blocks until complete)
claude-code-skill session-send myproject "Write unit tests for auth.ts"
# Streaming (see progress in real-time)
claude-code-skill session-send myproject "Refactor this module" --stream
# With custom timeout
claude-code-skill session-send myproject "Run all tests" -t 300000
```
#### Managing Sessions
```bash
# List active sessions
claude-code-skill session-list
# Get detailed status
claude-code-skill session-status myproject
# View conversation history
claude-code-skill session-history myproject -n 50
# Pause and resume
claude-code-skill session-pause myproject
claude-code-skill session-resume-paused myproject
# Fork a session (create a branch for experiments)
claude-code-skill session-fork myproject myproject-experiment
# Stop
claude-code-skill session-stop myproject
# Restart a failed session
claude-code-skill session-restart myproject
```
### Session History & Search
```bash
# Browse all Claude Code sessions
claude-code-skill sessions -n 20
# Search sessions by project
claude-code-skill session-search --project ~/myapp
# Search by time
claude-code-skill session-search --since "2h"
claude-code-skill session-search --since "2024-02-01"
# Search by query
claude-code-skill session-search "bug fix"
# Resume a historical session
claude-code-skill resume <session-id> "Continue where we left off" -d ~/project
```
### Batch Operations
```bash
# Read multiple files at once
claude-code-skill batch-read "src/**/*.ts" "tests/**/*.test.ts" -p ~/project
```
## ๐ค Agent Team Features
Deploy multiple Claude agents working together on complex tasks.
### Basic Agent Team
```bash
# Define a team of agents
claude-code-skill session-start team-project -d ~/project \
--agents '{
"architect": {
"description": "Designs system architecture",
"prompt": "You are a senior software architect. Design scalable, maintainable systems."
},
"developer": {
"description": "Implements features",
"prompt": "You are a full-stack developer. Write clean, tested code."
},
"reviewer": {
"description": "Reviews code quality",
"prompt": "You are a code reviewer. Check for bugs, style issues, and improvements."
}
}' \
--agent architect
# Switch between agents mid-conversation
claude-code-skill session-send team-project "Design the authentication system"
# (architect responds)
claude-code-skill session-send team-project "@developer implement the design"
# (developer agent takes over)
claude-code-skill session-send team-project "@reviewer review the implementation"
# (reviewer agent takes over)
```
### Pre-configured Team Templates
```bash
# Code review team
claude-code-skill session-start review -d ~/project \
--agents '{
"security": {"prompt": "Focus on security vulnerabilities"},
"performance": {"prompt": "Focus on performance issues"},
"quality": {"prompt": "Focus on code quality and maintainability"}
}' \
--agent security
# Full-stack team
claude-code-skill session-start fullstack -d ~/project \
--agents '{
"frontend": {"prompt": "React/TypeScript frontend specialist"},
"backend": {"prompt": "Node.js/Express backend specialist"},
"database": {"prompt": "PostgreSQL/Redis database specialist"}
}' \
--agent frontend
```
## ๐ง Advanced Features
### Tool Control
```bash
# Allow specific tools with patterns
--allowed-tools "Bash(git:*,npm:*),Read,Edit"
# Deny dangerous operations
--disallowed-tools "Bash(rm:*,sudo:*),Write(/etc/*)"
# Limit to specific tool set
--tools "Read,Glob,Grep"
# Disable all tools
--tools ""
```
### System Prompts
```bash
# Replace system prompt completely
--system-prompt "You are a Python expert. Always use type hints."
# Append to existing prompt
--append-system-prompt "Always run tests after changes."
```
### Session Management
```bash
# Resume with fork (create a branch)
--resume <session-id> --fork-session
# Use custom UUID for session
--session-id "550e8400-e29b-41d4-a716-446655440000"
# Add additional working directories
--add-dir "/var/log,/tmp/workspace"
```
### Multi-Model Support (Proxy)
Use `--base-url` to route requests through a proxy, enabling other models (Gemini, GPT) to power Claude Code:
```bash
# Use Gemini via claude-code-proxy
claude-code-skill session-start gemini-task -d ~/project \
--base-url http://127.0.0.1:8082 \
--model claude-3-5-sonnet-20241022 # Proxy will map to Gemini
# Use GPT via proxy
claude-code-skill session-start gpt-task -d ~/project \
--base-url http://127.0.0.1:8082 \
--model claude-3-haiku-20240307 # Proxy will map to GPT
```
**Note:** Requires `claude-code-proxy` running on port 8082 with proper API keys configured.
```bash
# Start the proxy
cd ~/clawd/claude-code-proxy && source .venv/bin/activate
uvicorn server:app --host 127.0.0.1 --port 8082
```
## ๐ Best Practices
### For OpenClaw Agents
1. **Always use persistent sessions for multi-step tasks**
```bash
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts โ single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score โฅ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.