Agent skill

Opencode Acp Control

by LeoYeAI in LeoYeAI/openclaw-master-skills

Control OpenCode directly via the Agent Client Protocol (ACP).

MITAuto-check passedBackend & APIs

Install Opencode Acp Control

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill opencode-acp-control -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills opencode-acp-control --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/opencode-acp-control-v2 .claude/skills/opencode-acp-control && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
opencode-acp-control
GitHub stars
2.2k
Token cost
~4.5k tokens
SKILL.md length
922 words
Files
5
Skills in repo
1,215
Repo updated
First seen
Licence
MIT

At a glance

Control OpenCode directly via the Agent Client Protocol (ACP).

  • Works in 7 steps: Pre-flight Check → Start OpenCode → Initialize (with retry) → …
  • Tasks that involve Authentication
  • SKILL.md covers 🆕 What's New in v2.0, Quick Reference, 🚀 Quick Start (Simple) and 📁 Skill Files, plus 6 more sections
  • Runs Shell scripts from its folder

What it does

Opencode Acp Control is an agent skill from LeoYeAI/openclaw-master-skills. Control OpenCode directly via the Agent Client Protocol (ACP). Start sessions, send prompts, resume conversations, and manage OpenCode updates. Includes automatic recovery, stuck detection, and session management.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `_meta.json`, `config.default.json` and `opencode-session.sh`).

It sits in Backend & APIs, covering Authentication. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve Authentication

Example prompts

  • “/opencode-acp-control”

Requirements

  • A Bash shell

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Pre-flight Check
  2. Start OpenCode
  3. Initialize (with retry)
  4. Create Session (with retry)
  5. Send Prompts (with adaptive polling)
  6. Health Check (Smart - No Token Waste)
  7. Cleanup

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Opencode Acp Control loads about 4.5k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 922 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 922 words, ~4,456 tokens.

Download SKILL.mdSave it as .claude/skills/opencode-acp-control/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
opencode-acp-control
description
Control OpenCode directly via the Agent Client Protocol (ACP). Start sessions, send prompts, resume conversations, and manage OpenCode updates. Includes automatic recovery, stuck detection, and session management.
metadata.version
2.0.0
metadata.author
Bastian Berrios <bastianberrios.a@gmail.com>
metadata.license
MIT
metadata.github_url
https://github.com/berriosb/Opencode-Acp-Control

OpenCode ACP Skill v2.0

Control OpenCode directly via the Agent Client Protocol (ACP) with automatic recovery and stuck detection.

🆕 What's New in v2.0

FeatureDescription
Auto-retryAutomatically retries on failure (max 3 attempts)
Stuck detectionDetects when OpenCode is not responding
Lock cleanupAutomatically removes stale lock files
Adaptive pollingPolls faster at start, slower when stable
Health checksPeriodic checks that OpenCode is alive
Configurable timeoutsShorter timeouts with escalation
Session recoveryCan recover from crashes mid-task

Quick Reference

ActionHow
Start OpenCodeexec(command: "opencode acp --cwd /path", background: true)
Send messageprocess.write(sessionId, data: "<json-rpc>\n")
Read responseprocess.poll(sessionId) - adaptive polling
Health checkprocess.poll(sessionId, timeout: 5000) - only when no output >60s
Stop OpenCodeprocess.kill(sessionId) + cleanup locks
Clean locksexec(command: "rm -f ~/.openclaw/agents/*/sessions/*.lock")
List sessionsexec(command: "opencode session list", workdir: "...")
Resume sessionList sessions → session/load

🚀 Quick Start (Simple)

For most use cases, use this simple workflow:

1. exec(command: "opencode acp --cwd /path/to/project", background: true)
   -> sessionId: "bg_42"

2. process.write(sessionId: "bg_42", data: initialize_json + "\n")
   process.poll(sessionId: "bg_42", timeout: 10000)

3. process.write(sessionId: "bg_42", data: session_new_json + "\n")
   process.poll(sessionId: "bg_42", timeout: 10000)
   -> opencodeSessionId: "sess_xyz"

4. process.write(sessionId: "bg_42", data: prompt_json + "\n")
   adaptivePoll(sessionId: "bg_42", maxWaitMs: 120000)

5. When done: process.kill(sessionId: "bg_42")
   cleanupLocks()

📁 Skill Files

FilePurpose
SKILL.mdThis file - main documentation
config.default.jsonDefault configuration (copy to config.json to customize)
templates.mdPrompt templates for common tasks

⚙️ Configuration

Option 1: Use defaults

All defaults are built-in. No config file needed.

Option 2: Customize

Copy config.default.json to config.json in the same folder and modify:

bash
cp config.default.json config.json
# Edit config.json with your preferences

Config structure:

json
{
  "timeouts": { "initialize": 10000, "prompt": {...} },
  "retry": { "maxAttempts": 3, "initialDelay": 2000 },
  "polling": { "initial": 1000, "active": 2000 },
  "healthCheck": { "noOutputThreshold": 60000 },
  "recovery": { "autoRecover": true },
  "mcpServers": { "default": [], "supabase": ["supabase"] }
}

Timeouts (Configurable)
OperationDefaultMaxWhen to increase
Initialize10s30sSlow machine
Session new10s30sLarge project
Prompt (simple)60s120sComplex query
Prompt (complex)120s300sRefactor, code gen
Health check5s10sNetwork issues
Retry Configuration
SettingDefaultDescription
Max retries3How many times to retry on failure
Retry delay2sInitial delay between retries
Backoff multiplier2Delay doubles each retry
Max retry delay10sMaximum delay between retries
Adaptive Polling
PhaseIntervalDuration
Initial1sFirst 10s
Active2s10s - 60s
Stable3s60s - 120s
Slow5s120s+

🔄 Automatic Recovery

Stuck Detection

OpenCode is considered "stuck" when:

  • No response after 2x expected timeout
  • Health check fails 3 times in a row
  • Process is still running but not responding to polls
Recovery Steps

When stuck is detected:

1. Cancel current operation: session/cancel
2. Wait 2 seconds
3. If still stuck: process.kill
4. Clean up locks
5. Restart OpenCode
6. Resume from last known session (if available)
Lock Cleanup

Lock files can become stale when OpenCode crashes. Always clean up:

bash
# Before starting a new session
exec(command: "find ~/.openclaw/agents -name '*.lock' -mmin +30 -delete")

# After killing a stuck process
exec(command: "rm -f ~/.openclaw/agents/*/sessions/*.lock")

📋 Step-by-Step Workflow

Step 1: Pre-flight Check

Before starting, verify environment:

bash
# Check OpenCode is installed
exec(command: "opencode --version")

# Clean stale locks (older than 30 minutes)
exec(command: "find ~/.openclaw/agents -name '*.lock' -mmin +30 -delete")
Step 2: Start OpenCode
bash
exec(
  command: "opencode acp --cwd /path/to/project",
  background: true,
  workdir: "/path/to/project"
)
# Save sessionId for all subsequent operations
Step 3: Initialize (with retry)
json
// Send initialize
{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":1,"clientCapabilities":{"fs":{"readTextFile":true,"writeTextFile":true},"terminal":true},"clientInfo":{"name":"clawdbot","title":"Clawdbot","version":"2.0.0"}}}

Retry logic:

for attempt in 1..3:
    process.write(sessionId, initialize_json + "\n")
    response = process.poll(sessionId, timeout: 10000)
    
    if response contains protocolVersion:
        break  # Success
    
    if attempt < 3:
        sleep(2 * attempt)  # Backoff: 2s, 4s
    else:
        # Recovery mode
        process.kill(sessionId)
        cleanupLocks()
        restart from Step 2
Step 4: Create Session (with retry)
json
{"jsonrpc":"2.0","id":1,"method":"session/new","params":{"cwd":"/path/to/project","mcpServers":[]}}

Same retry logic as initialize.

Step 5: Send Prompts (with adaptive polling)
json
{"jsonrpc":"2.0","id":2,"method":"session/prompt","params":{"sessionId":"sess_xyz","prompt":[{"type":"text","text":"Your question here"}]}}

Adaptive polling:

elapsed = 0
interval = 1000  # Start at 1s
maxWait = 120000  # 2 minutes for complex tasks

while elapsed < maxWait:
    response = process.poll(sessionId, timeout: interval)
    
    if response contains stopReason:
        return response  # Done
    
    if response contains error:
        handle_error(response)
        break
    
    # Adaptive interval
    elapsed += interval
    if elapsed < 10000:
        interval = 1000      # First 10s: poll every 1s
    elif elapsed < 60000:
        interval = 2000      # 10-60s: poll every 2s
    elif elapsed < 120000:
        interval = 3000      # 60-120s: poll every 3s
    else:
        interval = 5000      # 120s+: poll every 5s

# Timeout reached - check if stuck
if is_stuck(sessionId):
    recover(sessionId)
Step 6: Health Check (Smart - No Token Waste)

⚠️ Don't poll constantly - wastes tokens!

Only do health checks when:

  1. No output for >60s (possible stuck)
  2. Approaching timeout (verify before declaring stuck)
  3. Something looks wrong (partial errors, etc.)

DO NOT health check when:

  • OpenCode is actively generating output
  • <60s since last output
# Smart health check - only when needed
if time_since_last_output > 60000:  # 60s
    response = process.poll(sessionId, timeout: 5000)
    
    if response contains new data:
        last_output_time = now()
        continue  # Not stuck, just slow
    
    if response is "Process still running" with no data:
        # Still alive, just thinking - wait more
        continue
    
    if response is "No active session":
        # Process died - recover
        recover(sessionId)
Step 7: Cleanup

When done, always clean up:

process.kill(sessionId)
exec(command: "rm -f ~/.openclaw/agents/*/sessions/*.lock")

🛠️ Error Handling

Common Errors and Solutions
ErrorDetectionSolution
Process diedprocess.poll returns "No active session"Restart OpenCode, resume session
Stuck (no response)No response after 2x timeoutCancel, kill, clean locks, restart
Lock file exists.lock file from previous runRemove stale locks (>30min old)
JSON parse errorMalformed responseSkip line, continue polling
Timeoutelapsed >= maxWaitCheck if stuck, retry or escalate
Rate limitedHTTP 429 from OpenCodeExponential backoff, max 10s
Recovery Function
function recover(sessionId, opencodeSessionId):
    # Step 1: Try to cancel gracefully
    process.write(sessionId, cancel_json + "\n")
    sleep(2000)
    
    # Step 2: Check if recovered
    response = process.poll(sessionId, timeout: 5000)
    if response is valid:
        return  # Recovered!
    
    # Step 3: Force kill
    process.kill(sessionId)
    
    # Step 4: Clean up
    exec("rm -f ~/.openclaw/agents/*/sessions/*.lock")
    
    # Step 5: Restart
    newSessionId = startOpenCode()
    initialize(newSessionId)
    
    # Step 6: Resume if we had a session
    if opencodeSessionId:
        session_load(newSessionId, opencodeSessionId)
    
    return newSessionId

🔌 Session Management

Multiple Sessions

OpenCode supports multiple concurrent sessions. Track them:

json
{
  "sessions": {
    "process_42": {
      "processSessionId": "bg_42",
      "opencodeSessionId": "sess_abc",
      "project": "/path/to/project1",
      "lastActivity": "2026-03-05T10:00:00Z",
      "status": "active"
    },
    "process_43": {
      "processSessionId": "bg_43",
      "opencodeSessionId": "sess_def",
      "project": "/path/to/project2",
      "lastActivity": "2026-03-05T09:30:00Z",
      "status": "idle"
    }
  }
}
Session Recovery

If OpenCode crashes mid-task:

1. Find the last opencodeSessionId
2. Start new OpenCode process
3. Initialize
4. session/load with the old sessionId
5. Continue from where it left off

📊 Monitoring

Show full SKILL.md (384 more words)Show less
Health Metrics

Track these to detect problems early:

MetricHealthyWarningCritical
Response time<5s5-15s>15s
Polls without data<1010-30>30
Lock file age<5min5-30min>30min
Consecutive errors01-2≥3
Logging

Log important events for debugging:

[2026-03-05 10:00:00] Started OpenCode, sessionId=bg_42
[2026-03-05 10:00:02] Initialized successfully
[2026-03-05 10:00:03] Created session sess_abc
[2026-03-05 10:00:05] Sent prompt: "Refactor auth module"
[2026-03-05 10:00:15] Received update (thinking)
[2026-03-05 10:00:45] Received update (tool use)
[2026-03-05 10:01:30] Completed, stopReason=end_turn

🎯 Best Practices

DO:
  • ✅ Always clean up locks before starting
  • ✅ Use adaptive polling (saves tokens)
  • ✅ Implement retry logic (makes it robust)
  • ✅ Track session state (enables recovery)
  • ✅ Set appropriate timeouts per task type
  • ✅ Kill and restart if stuck >2x timeout
DON'T:
  • ❌ Poll every 2s for 5 minutes (wastes tokens)
  • ❌ Health check every 30s when output is active (wastes tokens)
  • ❌ Ignore stuck processes (blocks future work)
  • ❌ Leave lock files after crashes
  • ❌ Use same timeout for all operations
  • ❌ Skip health checks when no output for >60s (misses stuck detection)

📝 Example: Robust Implementation

# State tracking
state = {
  processSessionId: null,
  opencodeSessionId: null,
  messageId: 0,
  retries: 0,
  lastActivity: null
}

# Start with cleanup
cleanupStaleLocks()

# Start OpenCode
state.processSessionId = exec("opencode acp --cwd /path", background: true)

# Initialize with retry
for attempt in 1..3:
  process.write(state.processSessionId, initialize())
  response = process.poll(state.processSessionId, timeout: 10000)
  
  if is_valid(response):
    break
  
  if attempt == 3:
    throw Error("Failed to initialize after 3 attempts")

# Create session with retry
for attempt in 1..3:
  process.write(state.processSessionId, session_new())
  response = process.poll(state.processSessionId, timeout: 10000)
  
  if is_valid(response):
    state.opencodeSessionId = response.result.sessionId
    break
  
  if attempt == 3:
    throw Error("Failed to create session after 3 attempts")

# Send prompt with adaptive polling
process.write(state.processSessionId, prompt(state.messageId, "Your task"))

elapsed = 0
interval = 1000
maxWait = 120000

while elapsed < maxWait:
  response = process.poll(state.processSessionId, timeout: interval)
  state.lastActivity = now()
  
  if contains_stop_reason(response):
    return parse_response(response)
  
  elapsed += interval
  interval = get_adaptive_interval(elapsed)
  
  # Smart health check - only if no output for >60s
  if elapsed > 60000 && no_recent_output:
    if is_stuck(state.processSessionId):
      state = recover(state)
      # Re-send prompt
      process.write(state.processSessionId, prompt(state.messageId, "Your task"))
      elapsed = 0

# Timeout
throw Error("Operation timed out after ${maxWait}ms")

🔧 Utility Functions

cleanupStaleLocks()
bash
# Remove locks older than 30 minutes
find ~/.openclaw/agents -name '*.lock' -mmin +30 -delete
isStuck(sessionId)
# Check if process is alive but not responding
response = process.poll(sessionId, timeout: 5000)
return response == "Process still running" && no_data_for_60s
getAdaptiveInterval(elapsedMs)
if elapsedMs < 10000: return 1000
if elapsedMs < 60000: return 2000
if elapsedMs < 120000: return 3000
return 5000

📝 Prompt Templates


📝 Prompt Templates

See templates.md for pre-built prompts for common tasks:

CategoryTemplates
RefactoringExtract function, convert to TS, improve readability
FeaturesAdd endpoint, add component, implement feature
Bug fixesDebug and fix, TypeScript errors
TestingUnit tests, integration tests
DocumentationJSDoc/TSDoc, README updates
DatabaseMigrations, RLS policies
PerformanceQuery optimization, bundle size
SecuritySecurity audit

Usage:

1. Read templates.md
2. Find appropriate template
3. Replace placeholders with your specifics
4. Send as prompt

📊 Metrics & Monitoring

Track these for health monitoring:
MetricHow to trackHealthyWarningCritical
Avg response timeLog timestamps<30s30-60s>60s
Polls per requestCounter<2020-50>50
Retry rateRetries/requests<5%5-15%>15%
Stuck rateStucks/sessions<1%1-5%>5%
Success rateCompleted/started>95%85-95%<85%
Logging format:
[2026-03-05 10:00:00] INFO: Started OpenCode, sessionId=bg_42
[2026-03-05 10:00:02] INFO: Initialized successfully
[2026-03-05 10:00:03] INFO: Created session sess_abc
[2026-03-05 10:00:05] INFO: Sent prompt (refactor)
[2026-03-05 10:00:15] DEBUG: Received update (thinking)
[2026-03-05 10:00:45] DEBUG: Received update (tool use)
[2026-03-05 10:01:30] INFO: Completed, stopReason=end_turn
[2026-03-05 10:01:31] INFO: Metrics: duration=91s, polls=15, retries=0
Log levels:
  • ERROR - Failures, exceptions, stuck detected
  • WARN - Retries, slow responses, near-timeout
  • INFO - Start, complete, cleanup
  • DEBUG - Detailed output, updates received

📦 Skill Files

opencode-acp-control-3/
├── SKILL.md              # This file
├── opencode-session.sh   # Helper script (executable)
├── config.default.json   # Default configuration
├── templates.md          # Prompt templates
├── _meta.json            # Skill metadata
└── .clawhub/             # ClawHub metadata

Use opencode-session.sh for automatic workflow:

bash
# Simple usage
~/.openclaw/workspace/skills/opencode-acp-control-3/opencode-session.sh \
  --project /path/to/project \
  --prompt "Add error handling to the API"

# With template
opencode-session.sh \
  --project ~/myapp \
  --template "Add API endpoint" \
  --prompt "POST /api/users with validation"

# Complex task
opencode-session.sh \
  --project ~/myapp \
  --timeout complex \
  --mcp '["supabase"]' \
  --prompt "Create migration for users table"
Script options:
OptionDescription
--project PATHProject directory (required)
--prompt "TEXT"Prompt to send (required if no template)
--template NAMEUse template from templates.md
--timeout TYPEsimple (60s) | medium (120s) | complex (300s)
--mcp SERVERSMCP servers as JSON array
--verboseEnable debug logging
--dry-runShow JSON-RPC without executing
--helpShow help
What the script provides:

The script outputs a complete workflow with:

  • ✅ Pre-flight cleanup
  • ✅ Exact JSON-RPC messages to send
  • ✅ Retry logic hints
  • ✅ Adaptive polling intervals
  • ✅ Health check thresholds
  • ✅ Cleanup commands

CYPHER should:

  1. Execute the script with options
  2. Parse the output
  3. Execute the steps in order
  4. Log metrics at the end

Version 2.2.0 - Released 2026-03-05 Changes: Added opencode-session.sh helper script

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files in skills/opencode-acp-control-v2 of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • config.default.json
  • opencode-session.sh
  • templates.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Opencode Acp Control next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Opencode Acp Control compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Opencode Acp Control this skillLeoYeAI/openclaw-master-skills2.2k—~4.5kAutomated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Supabase Development and Debuggingsupabase/agent-skills2.7k3 repos~3.6kAutomated safety check: PassMIT
Better Auth Best Practiceslatitude-dev/latitude-llm4.7k7 repos~1.6kAutomated safety check: PassMIT
Supabasecurvenote/curvenote1695 repos~2.2kAutomated safety check: PassCustom licence
Gitnexus Exploringaws-samples/sample-kolya-br-proxy10611 repos~749Automated safety check: PassMIT-0

Similar skills

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed
  • Official

    General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.

    2.7k GitHub starsUsed in 3 repos~3.6k tokens
    Backend & APIsAuto-check passed
  • Better Auth Best Practices

    latitude-dev/latitude-llm

    Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.

    4.7k GitHub starsUsed in 7 repos~1.6k tokens
    Backend & APIsAuto-check passed
  • Supabase

    curvenote/curvenote

    A skill your agent uses when doing ANY task involving Supabase.

    169 GitHub starsUsed in 5 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • Gitnexus Exploring

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.

    106 GitHub starsUsed in 11 repos~749 tokens
    Backend & APIsAuto-check passed
  • Gemini Live API Dev

    google-gemini/gemini-skills

    Official

    A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.

    4.3k GitHub stars~4.6k tokensUpdated today
    Backend & APIsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,215 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Opencode Acp Control

What does Opencode Acp Control do?

Control OpenCode directly via the Agent Client Protocol (ACP). Opencode Acp Control is an agent skill from LeoYeAI/openclaw-master-skills. Control OpenCode directly via the Agent Client Protocol (ACP).

When should I use Opencode Acp Control?

Opencode Acp Control fits situations like: tasks that involve Authentication.

How do I install Opencode Acp Control in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill opencode-acp-control -a claude-code`. Or copy the skill folder (skills/opencode-acp-control-v2 in LeoYeAI/openclaw-master-skills) into .claude/skills/opencode-acp-control in your project. Claude Code loads it when a task matches its description.

How do I install Opencode Acp Control in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill opencode-acp-control -a codex`. Or copy the skill folder (skills/opencode-acp-control-v2 in LeoYeAI/openclaw-master-skills) into .agents/skills/opencode-acp-control in your project. Codex loads it when a task matches its description.

Can I use Opencode Acp Control in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill opencode-acp-control -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opencode-acp-control, .gemini/skills/opencode-acp-control, .github/skills/opencode-acp-control and .opencode/skills/opencode-acp-control in your project.

What does Opencode Acp Control need to run?

Going by SKILL.md and its folder, Opencode Acp Control needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Opencode Acp Control access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Opencode Acp Control safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Opencode Acp Control use?

Opencode Acp Control is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Opencode Acp Control use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Opencode Acp Control?

Skills that share tags, products or a category with Opencode Acp Control: Fortify Development (coollabsio/coolify, 63k stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars) and Supabase (curvenote/curvenote, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Opencode Acp Control?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,158 GitHub stars. The repository holds 1,215 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.