run-agent — for Claude Code run-agent, orchestrate, community, for Claude Code, ide skills, Routes to the correct CLI (, model MODEL, agent NAME, skills a,b,c, strict-skills

v1.0.0

이 스킬 정보

적합한 상황: Ideal for AI agents that need run-agent — execution engine. 현지화된 요약: skills to orchestrate multiple harnesses together # Run-Agent — Execution Engine Single entry point for agent execution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

기능

Run-Agent — Execution Engine
Skills source: sibling skills (../). Runtime artifacts: .orchestrate/.
Runner scripts (relative to this skill directory):
scripts/run-agent.sh — launch a subagent run
scripts/run-index.sh — inspect and manage runs

# Core Topics

haowjy haowjy
[16]
[4]
Updated: 3/25/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
67
Canonical Locale
en
Detected Body Locale
en

적합한 상황: Ideal for AI agents that need run-agent — execution engine. 현지화된 요약: skills to orchestrate multiple harnesses together # Run-Agent — Execution Engine Single entry point for agent execution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

이 스킬을 사용하는 이유

추천 설명: run-agent helps agents run-agent — execution engine. skills to orchestrate multiple harnesses together # Run-Agent — Execution Engine Single entry point for agent execution. This AI agent skill supports Claude

최적의 용도

적합한 상황: Ideal for AI agents that need run-agent — execution engine.

실행 가능한 사용 사례 for run-agent

사용 사례: Applying Run-Agent — Execution Engine
사용 사례: Applying Skills source: sibling skills (../). Runtime artifacts: .orchestrate/
사용 사례: Applying Runner scripts (relative to this skill directory):

! 보안 및 제한 사항

  • 제한 사항: Requires repository-specific context from the skill documentation
  • 제한 사항: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is run-agent?

적합한 상황: Ideal for AI agents that need run-agent — execution engine. 현지화된 요약: skills to orchestrate multiple harnesses together # Run-Agent — Execution Engine Single entry point for agent execution. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install run-agent?

Run the command: npx killer-skills add haowjy/orchestrate/run-agent. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for run-agent?

Key use cases include: 사용 사례: Applying Run-Agent — Execution Engine, 사용 사례: Applying Skills source: sibling skills (../). Runtime artifacts: .orchestrate/, 사용 사례: Applying Runner scripts (relative to this skill directory):.

Which IDEs are compatible with run-agent?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for run-agent?

제한 사항: Requires repository-specific context from the skill documentation. 제한 사항: Works best when the underlying tools and dependencies are already configured.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add haowjy/orchestrate/run-agent. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use run-agent immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

run-agent

skills to orchestrate multiple harnesses together # Run-Agent — Execution Engine Single entry point for agent execution. This AI agent skill supports Claude

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Run-Agent — Execution Engine

Single entry point for agent execution. A run is model + agent (opt) + skills (opt) + prompt. Routes to the correct CLI (claude, codex, opencode) based on the model, logs everything, and writes structured index entries.

Skills source: sibling skills (../). Runtime artifacts: .orchestrate/.

Runner scripts (relative to this skill directory):

  • scripts/run-agent.sh — launch a subagent run
  • scripts/run-index.sh — inspect and manage runs

Run Composition

Compose runs dynamically by specifying model, skills, and prompt:

bash
1# Model + skills + prompt 2scripts/run-agent.sh --model MODEL --skills SKILL1,SKILL2 -p "PROMPT" 3 4# Model + prompt (no skills) 5scripts/run-agent.sh --model MODEL -p "PROMPT" 6 7# With labels and session grouping 8scripts/run-agent.sh --model MODEL --skills SKILLS \ 9 --session SESSION_ID --label KEY=VALUE -p "PROMPT" 10 11# With template variables 12scripts/run-agent.sh --model MODEL \ 13 -v KEY1=path/to/file1 -v KEY2=path/to/file2 \ 14 -p "Task using {{KEY1}} and {{KEY2}}" 15 16# Dry run — see composed prompt + CLI command without executing 17scripts/run-agent.sh --model MODEL --skills SKILLS --dry-run -p "PROMPT"

Key Flags

FlagDescription
--model MODEL / -mModel to use (auto-routes to correct CLI)
--agent NAMEAgent profile for defaults + permissions
--skills a,b,cSkills to compose into the prompt
--strict-skillsFail fast when any listed skill is unknown
-p "prompt"Task prompt
-f path/to/fileReference file appended to prompt
-v KEY=VALUETemplate variable substitution (repeatable)
--session IDSession ID for grouping related runs
--label KEY=VALUERun metadata label (repeatable)
-D brief|standard|detailedReport detail level (default: standard)
--continue-run REFContinue a previous run's harness session
--forkFork the session on continuation (default where supported)
--in-placeResume without forking (always for Codex)
--dry-runShow composed prompt without executing
-C DIRWorking directory for subprocess

Runtime Config (.orchestrate/config.toml)

On first run in a workspace, run-agent.sh auto-creates .orchestrate/config.toml with commented examples.

Use this file to pin skills that should be auto-added on every run:

toml
1[skills] 2pinned = ["orchestrate", "run-agent", "mermaid"]

Notes:

  • Pinned skills are merged with agent-profile skills and CLI --skills (deduplicated by name).
  • Default template is fully commented; uncomment/edit to enable.

Output Artifacts

Each run writes to .orchestrate/runs/agent-runs/<run-id>/:

  • params.json — run parameters and metadata
  • input.md — composed prompt
  • prompt.raw.md — composed prompt before runtime-generated output/report sections
  • output.jsonl — raw CLI output (stream-json or JSONL)
  • stderr.log — CLI diagnostics (also streamed to terminal)
  • report.md — written by the subagent (or extracted as fallback)
  • files-touched.nul — NUL-delimited file paths (canonical machine format)
  • files-touched.txt — newline-delimited file paths (human-readable)

Run Index

Two-row append-only index at .orchestrate/index/runs.jsonl:

  • Start row (written before execution): status: "running" — provides crash visibility.
  • Finalize row (written after execution): status: "completed"|"failed" with exit code, duration, token usage, git metadata.

A start row with no matching finalize row means the run crashed or is still in progress.

Structured Exit Codes

CodeMeaning
0Success
1Agent/model error (bad output, task failure)
2Infrastructure error (CLI not found, harness crash)
3Timeout
130Interrupted (SIGINT / user cancel)
143Terminated (SIGTERM)

Model Routing

PatternCLI
claude-*, opus*, sonnet*, haiku*Claude (claude -p)
gpt-*, o1*, o3*, o4*, codex*Codex (codex exec)
opencode-*, provider/modelOpenCode (opencode run)

Routing is automatic from the selected model.

Run Explorer CLI

scripts/run-index.sh provides index-based run inspection:

bash
1scripts/run-index.sh list # List recent runs 2scripts/run-index.sh list --failed --json # Failed runs as JSON 3scripts/run-index.sh show @latest # Show last run details 4scripts/run-index.sh report @latest # Read last run's report 5scripts/run-index.sh logs @latest --tools # Tool call summary 6scripts/run-index.sh files @latest # Files touched 7scripts/run-index.sh stats # Aggregate statistics 8scripts/run-index.sh continue @latest -p "PROMPT" # Continue a run's session 9scripts/run-index.sh retry @last-failed # Retry a failed run 10scripts/run-index.sh maintain --compact # Archive old index entries

Run references: full ID, unique prefix (8+ chars), @latest, @last-failed, @last-completed.

Helper Scripts

ScriptPurpose
run-index.shRun explorer CLI (list, show, report, logs, files, stats, continue, retry, maintain)
log-inspect.shInspect run logs (summary, tools, errors, files, search)
extract-files-touched.shExtract file paths from run output
extract-harness-session-id.shExtract harness session/thread ID from output
extract-report-fallback.shExtract last assistant message as report fallback
load-model-guidance.shLoad model guidance with override precedence

관련 스킬

Looking for an alternative to run-agent or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자