ao-actions

GitHub

用于直接操作 Orchestrator 会话或 PR,包括停止、恢复、合并 PR、截图及文件发送等。支持通过自然语言指令执行具体的管理动作。

integrations/grok-bot/skills/ao-actions/SKILL.md OrchestratorInc/agent-orchestrator

Trigger Scenarios

停止或中断正在进行的任务 合并代码请求 获取会话截图或文件

Install

npx skills add OrchestratorInc/agent-orchestrator --skill ao-actions -g -y
More Options

Non-standard path

npx skills add https://github.com/OrchestratorInc/agent-orchestrator/tree/main/integrations/grok-bot/skills/ao-actions -g -y

Use without installing

npx skills use OrchestratorInc/agent-orchestrator@ao-actions

指定 Agent (Claude Code)

npx skills add OrchestratorInc/agent-orchestrator --skill ao-actions -a claude-code -g -y

安装 repo 全部 skill

npx skills add OrchestratorInc/agent-orchestrator --all -g -y

预览 repo 内 skill

npx skills add OrchestratorInc/agent-orchestrator --list

SKILL.md

Frontmatter
{
    "name": "ao-actions",
    "description": "Direct actions on one Orchestrator session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's browser, send a session's files, keep a host awake, and recurring Orchestrator automations. Use for \"stop <session>\", \"merge <PR>\", \"review <session>'s PR\", \"show me what <session> built\", \"keep the Mac awake tonight\", \"every night, ...\"."
}

Follow the ao-rules skill. Find the session first (ao-rules "AO hosts": <host>/<session id>). Run each action on the owner host from its via computer. "Yes" means the user's yes for that exact action in this chat.

Ask Do Yes needed Hosts
Stop what it's doing now aoapi POST "sessions/<id>/conversation/interrupt" No All
End the session aoapi POST "sessions/<id>/kill" '{}' Yes All
Resume an exited agent aoapi POST "sessions/<id>/resume-agent" '{}' No All
Restore an ended session aoapi POST "sessions/<id>/restore" '{}' (an ended orchestrator can't come back while its project has another live one) Yes All
Merge a PR see "Merge" Yes, per PR All
Start Orchestrator's reviewer on a session's PR ao review trigger <id> Yes Local
Screenshot a session's browser see "Screenshot" No Local
A session's files see "Files" No Local
Keep the host awake see "Keep awake" Yes Local
Recurring agent work see "Automations" Yes Local
Start one worker directly aoapi POST sessions '<json>' with projectId, displayName, prompt Yes All

For an action marked Local on a remote host, ask that host's orchestrator to do it (ao-orchestrator).

Start a worker directly only when the project has no orchestrator and the user doesn't want one (ao-rules "orchestrator first").

Merge

First show the PR and ask:

f(){ <aoapi helper>; aoapi GET "sessions/<session id>/pr" | python3 -c '
import json,sys
for p in json.load(sys.stdin).get("prs") or []:
    if str(p.get("number"))==sys.argv[1]: print(json.dumps({"url":p.get("url"),"headSha":p.get("headSha"),"state":p.get("state"),
        "ci":(p.get("ci") or {}).get("state"),"review":(p.get("review") or {}).get("decision"),"mergeability":(p.get("mergeability") or {}).get("state")}))' '<pr number>'; }; f

Tell the user the link, checks (ci), review decision and whether it can merge (mergeability). Never merge on failing checks or conflicting without the user saying so for that PR. On yes, merge exactly the commit you showed:

f(){ <aoapi helper>; aoapi POST "prs/<pr number>/merge" "$(python3 -c 'import json,sys; print(json.dumps({"prUrl":sys.argv[1],"expectedHeadSha":sys.argv[2]}))' '<url>' '<headSha>')"; }; f

If the PR got new commits since you showed it, Orchestrator refuses the merge. Show it again and ask again.

Screenshot

The session must have a browser page open. BROWSER_CAPABILITY_INVALID means it has none: say so.

f(){ mkdir -p ~/.ao-grok/out && AO_SESSION_ID='<id>' ao browser screenshot ~/.ao-grok/out/<id>-$(date +%H%M%S).png; }; f

Then CopyToBox and SendToUser.

Files

A session's deliverables are in its artifact folder:

f(){ ls -la "${AO_DATA_DIR:-$HOME/.ao/data}/artifacts/<id>/"; }; f

Send the file the user asks for with CopyToBox and SendToUser. HTML reports render best opened on the phone as a file.

Keep awake

For a run that must last overnight, after a yes:

f(){ <aoapi helper>; aoapi POST awake/sessions "$(python3 -c 'import json,sys; print(json.dumps({"mode":"duration","durationSeconds":int(sys.argv[1]),"scope":"ao"}))' '<seconds>')"; }; f

Say when it ends. The user can stop it in Orchestrator. An AWAKE error that mentions a safety stop means Orchestrator stopped keep-awake on purpose (for example on battery): tell the user to resume it in Orchestrator. Don't resume it yourself.

Automations

For recurring agent work that should run on the host even when the bot is off (for example "every night, update dependencies in "), create an Orchestrator automation after a yes:

ao automation create --project '<project>' --name '<name>' --cron '<m h dom mon dow>' --timezone '<IANA zone>' --prompt '<task>'

ao automation list shows them. To remove one after a yes: ao automation delete --yes <id>. Use a Grok routine instead when the job is to tell the user something (ao-status "Digest", ao-answer waiting check).

Version History

  • aa6e65d Current 2026-11-16 19:56

Same Skill Collection

.agents/skills/ao-desktop-dev/SKILL.md
.agents/skills/bug-triage/SKILL.md
.agents/skills/pr-description/SKILL.md
.claude/skills/ao-desktop-dev/SKILL.md
.claude/skills/bug-triage/SKILL.md
backend/internal/skillassets/bug-triage/SKILL.md
backend/internal/skillassets/using-ao/SKILL.md
integrations/grok-bot/skills/ao-answer/SKILL.md
integrations/grok-bot/skills/ao-orchestrator/SKILL.md
integrations/grok-bot/skills/ao-rules/SKILL.md
integrations/grok-bot/skills/ao-setup/SKILL.md
integrations/grok-bot/skills/ao-status/SKILL.md
integrations/grok-bot/skills/ao-update/SKILL.md

Metadata

Files
0
Version
2d1c4c3
Hash
6eb69f70
Indexed
2026-11-16 19:56

ホーム - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-17 05:52
浙ICP备14020137号-1