メニュー
Warm the task graph and vector store by synchronizing a configured task board through the reviewer MCP server. Use when the user asks to sync or index board tasks.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hashgraph-online/awesome-codex-plugins --skill sync-tasksコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use this skill whenever you need to send messages to another agent (codex, claude, or any named handle), check your inbox, drain queued messages, set up co-op mode between agents, join a swarm team, route messages across projects, or diagnose delivery issues. Also use it when you receive a message and need to know how to reply, inspect receipts, or handle priority. Covers any multi-agent coordination task where agents need to talk to each other — review requests, questions, status updates, decision threads, wake notifications, and orchestrator integration (Symphony, Kanban). For collaborative spec/design workflows specifically, prefer the /amq-spec skill which provides structured phase-by-phase guidance. Not intended for distributed systems design (RabbitMQ, Kafka), CI/CD pipelines, or single-agent tasks with no partner.
Parallel-research-then-converge design workflow between two agents. Use this skill when the user wants two agents to independently think through a design problem before aligning on a solution — "spec X with codex", "design X together", "both agents think through X", "brainstorm architecture together", "parallel research then joint proposal", "think through separately then align", "careful thought from both sides before coding", or any variation where the user wants collaborative design rather than just splitting implementation work. Also use this when you receive a message labeled workflow:spec and need to know the correct receiver-side protocol. Not for sending simple messages or reviews (use /amq-cli), implementing completed designs, or creating document templates.
Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation, or when the user asks to grill or pressure-test a plan or design.
SKILL.md を表示中
| name | sync-tasks |
| description | Warm the task graph and vector store by synchronizing a configured task board through the reviewer MCP server. Use when the user asks to sync or index board tasks. |
Reply in Russian. This is a thin, server-side trigger: the server enumerates, normalizes, and indexes the board. Do not enumerate tasks in the client and do not send credentials.
task_board from .review.yml; if absent, call get_board_config(). If neither resolves
a board, report a board-less no-op.type, project, create_target, done_target, and options.
Do not infer provider-specific fields.get_board_targets(board_type=<type>, project=<project>, provider_options=<task_board.options or {}>).
Its response contains targets and option entries with required_for and choices. Ask the
user to configure missing required options instead of inventing values; discovery is read-only.sync_board(board=<project or null>, board_type=<type>,
provider_options=<task_board.options or {}>, limit=<limit or null>,
purge_orphaned=<explicit request or false>)
by_board breakdown in Russian. Warnings and an error
response are fail-open: explain the reason and leave the local repository unchanged.sync_board is idempotent: rerunning is safe and inexpensive when the watermark is warm. It reads
the board; it never writes back.