ワンクリックでManusで任意のスキルを実行

始める

conveyor-check-status

スター0

フォーク0

更新日2026年6月21日 00:50

Check Agent Conveyor manager/worker or worker-set status from the current project's per-project ledger.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

neonwatty

neonwatty/agent-conveyor

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Conveyor Check Status

Use this skill when the operator asks for the status of an Agent Conveyor pair or worker set from any project.

Rules

Operator-facing only.
Codex app native sessions only.
Use .codex-workers/workerctl.db under the current project unless the operator explicitly provides another path.
Do not inspect product code or private content.
Treat ledger claims as claims unless backed by durable receipts.
Prefer compact status receipts with exact next action.
If a role is stale and app thread metadata is present, recommend the conveyor-app-wake-relay skill rather than an ad hoc direct prompt.

Commands

For a known task:

TASK="example-task"
conveyor app-loop-status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json
conveyor app-autopilot status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json

For an unknown task, list candidate records first:

conveyor tasks --path "$PWD/.codex-workers/workerctl.db" --json

Report manager and worker thread ids/titles, stale roles, inbox backlog, heartbeat/autopilot state, dispatch health, and the exact next action.

このリポジトリの他の Skills

同じリポジトリ

conveyor-setup-bundle

neonwatty/agent-conveyor

Draft, preflight, apply, and inspect Agent Conveyor setup bundles for manager-worker operating cells through a conversational Codex setup flow.

2026-06-290

conveyor-create-pair

neonwatty/agent-conveyor

Create one visible Codex app manager and one visible Codex app worker for the current project using the globally installed Agent Conveyor CLI.

2026-06-220

conveyor-create-worker-set

neonwatty/agent-conveyor

Create one visible Codex app manager and multiple visible Codex app workers for the current project using Agent Conveyor.

2026-06-220

conveyor-smoke-app-connections

neonwatty/agent-conveyor

Run the blocking Agent Conveyor Codex app connection smoke gate for a manager/worker pair or worker set before real work starts.

2026-06-220

conveyor-app-wake-relay

neonwatty/agent-conveyor

Wake stale Agent Conveyor Codex app manager or worker threads through native app thread tools and record delivery receipts.

2026-06-210

conveyor-whats-next-nudger

neonwatty/agent-conveyor

Run a bounded Agent Conveyor "what's next?" nudger loop for an existing Codex app manager/worker pair or worker set.

2026-06-210

name	conveyor-check-status
description	Check Agent Conveyor manager/worker or worker-set status from the current project's per-project ledger.

Conveyor Check Status

Use this skill when the operator asks for the status of an Agent Conveyor pair or worker set from any project.

Rules

Operator-facing only.
Codex app native sessions only.
Use .codex-workers/workerctl.db under the current project unless the operator explicitly provides another path.
Do not inspect product code or private content.
Treat ledger claims as claims unless backed by durable receipts.
Prefer compact status receipts with exact next action.
If a role is stale and app thread metadata is present, recommend the conveyor-app-wake-relay skill rather than an ad hoc direct prompt.

Commands

For a known task:

TASK="example-task"
conveyor app-loop-status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json
conveyor app-autopilot status "$TASK" --path "$PWD/.codex-workers/workerctl.db" --json

For an unknown task, list candidate records first:

conveyor tasks --path "$PWD/.codex-workers/workerctl.db" --json

Report manager and worker thread ids/titles, stale roles, inbox backlog, heartbeat/autopilot state, dispatch health, and the exact next action.