菜单
Preserve unresolved Captain choices discovered by investigations or reviews and route their answers durably. Use before completing a Scout or structured review, when linking dependent Tasks to a Captain choice, and when recording or resolving the Captain's exact answer.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Resolve, inspect, apply, verify, review or improve an AgentOS Agent composition. Use when selecting instructions, Skills, harness-native settings or capability requirements for a persistent Mate or bounded Assignment; loading an external composer or origin; reconciling desired and observed setup; collecting a composition debrief; or routing evidence into a separate improvement.
Select, configure, launch, inspect, resume, or change a verified AgentOS coding harness. Use before a First or Second Mate chooses a Crewmate harness, model or reasoning effort; before launching Pi or Codex through Herdr; or when harness authentication, flags, defaults, quota or recovery affect dispatch.
Inspect, create, and operate AgentOS runtime pods, Kustomize overlays, Herdr sessions, Mise toolchains, agent worktrees, terminals, PVCs, Kubernetes health, attach paths and runtime recovery. Use for normal First- or Second-Mate Kubernetes operations, child-Agent workload creation, tool resolution, stuck-agent debugging, remote terminal access, pod or session recovery, and readiness diagnosis.
Reconcile and supervise an AgentOS Mate's direct reports across PostgreSQL, Kubernetes, Herdr, PVCs, and Git. Use at every First- or Second-Mate session start, after restart or compaction, while delegated work is active, when Inbox or runtime state changes, and for blocked, stale, stuck, failed, interrupted, or recovering agents.
Inspect an environment and interactively establish or reconcile a persistent AgentOS First Mate in Kubernetes. Use only for first installation, a partial bootstrap, local-clone onboarding, cluster selection, or handoff from a temporary local agent to the cluster First Mate.
Charter, provision, route to, recover, change, and retire persistent AgentOS Second Mates. Use only from First Mate before any Second-Mate lifecycle operation, scope decision, charter handoff, runtime recovery, work transfer, configuration change, or retirement.
| name | agentos-decisions |
| description | Preserve unresolved Captain choices discovered by investigations or reviews and route their answers durably. Use before completing a Scout or structured review, when linking dependent Tasks to a Captain choice, and when recording or resolving the Captain's exact answer. |
PostgreSQL Inbox owns the decision. Do not infer choices from report prose with a script, create a fake Task for the question, or add another decisions table.
agentos.hold_captain_decision(task_id, key, subject, body, status_text).
Exact retry is idempotent; a conflicting reuse fails closed.agentos.link_task_decision(task_id, key, status_text). The dependency lives
in the Task's existing dependencies array.scout or review Assignment as completed, call
agentos.attest_assignment_decisions(assignment_id, keys). Pass the complete
unresolved set, including an explicit empty array. PostgreSQL rejects an
omitted or partial inventory.The originating Assignment may finish after attestation while its decision remains open. Completion, report archival, Pod loss or Agent retirement never resolve the Captain choice.
agentos.resolve_captain_decision(decision_id, exact_answer, status_text) in
the same short transaction as any coupled local state changes.Fleet-wide status reads structured Inbox and Task state. Never reconstruct open choices by scraping old reports, terminal output, visual artifacts or chat.