Agent skill

Acp Local Runner

by rebornix in rebornix/Agmente

Run and debug Agmente ACP end-to-end scenarios from the repo-owned e2e/scenarios/acp specs.

MITAuto-check passedTesting & QA

Install Acp Local Runner

skills CLI
$ npx skills add rebornix/Agmente --skill acp-local-runner -a claude-code

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

GitHub CLI
$ gh skill install rebornix/Agmente acp-local-runner --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/rebornix/Agmente.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/acp-local-runner .claude/skills/acp-local-runner && 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
acp-local-runner
GitHub stars
546
Token cost
~804 tokens
SKILL.md length
416 words
Files
2
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Run and debug Agmente ACP end-to-end scenarios from the repo-owned e2e/scenarios/acp specs.

  • Validating ACP websocket compatibility
  • SKILL.md covers Overview, Workflow and Guardrails
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Session creation

What it does

Acp Local Runner is an agent skill from rebornix/Agmente. Run and debug Agmente ACP end-to-end scenarios from the repo-owned e2e/scenarios/acp specs. Use when validating ACP websocket compatibility, session creation, cwd handling, reconnect flows, or reproducing ACP-only UI failures against a real local ACP backend.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA, covering End-to-end testing and Realtime and WebSockets. The repository describes itself as: iOS client for coding agents via ACP or Codex app-server. The licence is MIT.

When your agent uses it

  • Validating ACP websocket compatibility
  • Session creation
  • Reconnect flows
  • Reproducing ACP-only UI failures against a real local ACP backend

Example prompts

  • “/acp-local-runner”

What it can do on your machine

Read from SKILL.md and the folder at commit 87f224e. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Acp Local Runner loads about 804 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 416 words of instructions outside code blocks.

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

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 rebornix/Agmente at commit 87f224e, republished under its MIT licence (© rebornix). 416 words, ~804 tokens.

Download SKILL.mdSave it as .claude/skills/acp-local-runner/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
acp-local-runner
description
Run and debug Agmente ACP end-to-end scenarios from the repo-owned e2e/scenarios/acp specs. Use when validating ACP websocket compatibility, session creation, cwd handling, reconnect flows, or reproducing ACP-only UI failures against a real local ACP backend.

ACP Local Runner

Overview

Execute a repo-owned ACP scenario against a real local ACP backend, capture enough logs and UI state to diagnose failures, and always clean up backend and simulator app state.

For run, execute, validate, or reproduce requests, this skill is execute-only. Use real tools to perform the scenario; do not modify repository files unless the user explicitly asks to fix, stabilize, or make the flow executable.

Workflow

  1. Resolve the scenario.
  • Read the requested scenario from e2e/scenarios/acp/.
  • If the user names no scenario, choose the closest match from that directory and state the choice.
  • Treat the scenario file as the source of truth for setup, steps, assertions, and cleanup intent.
  1. Resolve the backend.
  • Read the backend id from the scenario front matter.
  • Open the matching file in e2e/backends/.
  • Use the backend file for canonical endpoint, start command, stop command, and capability notes.
  1. Prepare execution.
  • Prefer simulator execution when the scenario target is ios-simulator.
  • Use XcodeBuildMCP tools when available for boot/build/run/log/screenshot/interaction.
  • If simulator interaction tools are incomplete, use the best available non-editing fallback and state the limitation.
  • Verify the backend is reachable before debugging app behavior.
  1. Run the scenario.
  • Follow the scenario steps in order.
  • Capture wire or console checkpoints around initialize, session/list, session/new, session/prompt, session/load, and reconnect events when relevant.
  • Use the scenario assertions and e2e/assertions/common.md to judge pass/fail.
  1. Report and clean up.
  • Report backend, endpoint, simulator target, scenario path, and pass/fail status.
  • On failure, report the concrete broken step and the most likely root cause.
  • Always stop the backend if this run started it.
  • Always uninstall Agmente from the simulator unless the user explicitly asks to preserve state.
Show full SKILL.md (140 more words)Show less

Guardrails

  • Do not invent ACP behavior that is not in the scenario or backend docs.
  • Do not make the skill the source of truth for scenario semantics.
  • Prefer protocol-level explanations over tool-level explanations in failure reports.
  • If the scenario and backend docs disagree, treat that as repo drift and report it.
  • Treat run, execute, validate, and reproduce as execute-only requests.
  • Agentic testing means actually running the backend, simulator, and relevant protocol tooling rather than describing manual steps.
  • During execute-only runs, do not add accessibility identifiers, write harness code, patch docs, or create new tests to make the scenario pass.
  • If the run is blocked by missing automation hooks or incomplete tooling, report the blocker and stop instead of editing the repo.
  • Only make repository changes when the user explicitly asks to fix, stabilize, add hooks, or make the scenario executable.

© rebornix, 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 1 other file in .agents/skills/acp-local-runner of rebornix/Agmente.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 87f224e

Compare with similar skills

Acp Local Runner 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.

Acp Local Runner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Acp Local Runner this skillrebornix/Agmente546—~804Automated safety check: PassMIT
Protocol MarchatCod-e-Codes/marchat137—~540Automated safety check: PassMIT
Playwright Best Practicessanity-io/sanity6.4k7 repos~6.4kAutomated safety check: PassMIT
Slack E2Eopenclaw/openclaw392k—~1.7kAutomated safety check: PassMIT
Verify Lemonz80dev/lemon133—~4kAutomated safety check: NotesMIT
SsrSAP/spartacus784—~229Automated safety check: PassApache-2.0

Similar skills

  • Protocol Marchat

    Cod-e-Codes/marchat

    Maintains marchat WebSocket JSON protocol and shared wire types including E2E encoding.

    137 GitHub stars~540 tokensUpdated 7 days ago
    Testing & QAAuto-check passed
  • Official

    A skill your agent uses when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling…

    6.4k GitHub starsUsed in 7 repos~6.4k tokens
    Testing & QAAuto-check passed
  • Slack E2E

    openclaw/openclaw

    Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

    392k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Verify Lemon

    z80dev/lemon

    Verify lemon features against a running (or disposable) instance using the cheapest sufficient tier: DIRECT (attach/RPC + control-plane WS + bus observation, no Telegram), FAKE TELEGRAM (hermetic…

    133 GitHub stars~4k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes
  • Ssr

    SAP/spartacus

    Official

    A skill your agent uses when working with Spartacus Server-Side Rendering (SSR).

    784 GitHub stars~229 tokensUpdated today
    Testing & QAAuto-check passed
  • Tanstack Start

    asmyshlyaev177/test-proxy-recorder

    Record and replay TanStack Start SSR with test-proxy-recorder.

    78 GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check: notes

More from rebornix/Agmente

  • Codex Local CLI E2E

    rebornix/Agmente

    Run and debug Agmente iOS end-to-end tests against a real local Codex CLI app-server instance.

    546 GitHub stars~625 tokensUpdated 4 mo ago
    Auto-check passed
  • Repeat With Delay

    rebornix/Agmente

    Execute repeated shell commands as separate tool calls with a delay between each iteration.

    546 GitHub stars~473 tokensUpdated 4 mo ago
    Auto-check passed
  • Dynamically inspect ACP and Codex upstream repos using .agmente.paths, detect protocol/API/spec drift, and produce a risk-scored regression report.

    546 GitHub stars~914 tokensUpdated 4 mo ago
    Auto-check passed
  • Run Agmente Codex E2E

    rebornix/Agmente

    Run Agmente iOS end-to-end tests against a local Codex app-server endpoint, validate Codex thread/turn protocol flow, and perform mandatory cleanup.

    546 GitHub stars~464 tokensUpdated 4 mo ago
    Auto-check passed
  • Run Agmente E2E

    rebornix/Agmente

    Run Agmente iOS end-to-end tests against a local ACP agent (Gemini, Claude, Qwen, or Vibe), validate core RPC flow, and perform mandatory cleanup.

    546 GitHub stars~414 tokensUpdated 4 mo ago
    Auto-check passed

Questions about Acp Local Runner

What does Acp Local Runner do?

Run and debug Agmente ACP end-to-end scenarios from the repo-owned e2e/scenarios/acp specs. Acp Local Runner is an agent skill from rebornix/Agmente. Run and debug Agmente ACP end-to-end scenarios from the repo-owned e2e/scenarios/acp specs.

When should I use Acp Local Runner?

Acp Local Runner fits situations like: validating ACP websocket compatibility; session creation; reconnect flows; reproducing ACP-only UI failures against a real local ACP backend.

How do I install Acp Local Runner in Claude Code?

Run `npx skills add rebornix/Agmente --skill acp-local-runner -a claude-code`. Or copy the skill folder (.agents/skills/acp-local-runner in rebornix/Agmente) into .claude/skills/acp-local-runner in your project. Claude Code loads it when a task matches its description.

How do I install Acp Local Runner in Codex?

Run `npx skills add rebornix/Agmente --skill acp-local-runner -a codex`. Or copy the skill folder (.agents/skills/acp-local-runner in rebornix/Agmente) into .agents/skills/acp-local-runner in your project. Codex loads it when a task matches its description.

Can I use Acp Local Runner 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 rebornix/Agmente --skill acp-local-runner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/acp-local-runner, .gemini/skills/acp-local-runner, .github/skills/acp-local-runner and .opencode/skills/acp-local-runner in your project.

What does Acp Local Runner need to run?

SKILL.md names no scripts, command-line tools or credentials: Acp Local Runner is instructions for the agent only.

Does Acp Local Runner 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 Acp Local Runner 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 Acp Local Runner use?

Acp Local Runner 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 Acp Local Runner use?

About 804 tokens (SKILL.md is roughly 3.2k 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 Acp Local Runner?

Skills that share tags, products or a category with Acp Local Runner: Protocol Marchat (Cod-e-Codes/marchat, 137 stars), Playwright Best Practices (sanity-io/sanity, 6.4k stars), Slack E2E (openclaw/openclaw, 392k stars) and Verify Lemon (z80dev/lemon, 133 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Acp Local Runner?

rebornix (a GitHub user) maintains it in rebornix/Agmente, which has 546 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on May 31, 2026.

Source: rebornix/Agmente on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.