[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEF6D9NV29C6R0NA8GETPT":3,"skill-same:01M6MEF6D9NV29C6R0NA8GETPT":111},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6MEF6D9NV29C6R0NA8GETPT","amq-cli",null,"Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"cli","amq cli","queues","agent messaging","do","receipts","coding","diagnostics","delivery","message","work","wake","code","message queues","design","managed","messages","project","messaging","coordinate","2026-11-10 10:12:30",false,"---\nname: amq-cli\nversion: 0.143.0 # x-release-please-version\ndescription: Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.\nmetadata:\n  short-description: Inter-agent messaging via AMQ CLI\n  compatibility: claude-code, codex-cli, grok-cli, antigravity-cli\n---\n\n# AMQ CLI\n\nUse the `amq` CLI for all queue operations. Never edit Maildir files directly.\nAMQ transports coordination; the caller or orchestrator still owns task planning,\nworktrees, approvals, and delivery.\n\n## Start in the correct context\n\nUse the first case that applies:\n\n1. `AM_ME` is set (`amq coop exec` or `amq launch` started the session): run\n   bare `amq` commands. Do not override `--me` or reconstruct the root.\n2. A Claude Code session with no `AM_ME`, such as a chat of the desktop app:\n   run `amq coop join` once; add `--me \"\u003Chandle>\"` when the user named a\n   handle or the output says the default is taken. Later bare `amq` commands\n   in that session use the handle. Follow what the output says about the wake: when\n   the wait hook is not installed, tell the user that `amq coop install-hooks`\n   installs it once per machine and that it takes effect in a new session.\n   When a later command says the session has no handle (a terminal session\n   after `\u002Fclear`), join again. Do not use the `amq env` export here; a shell\n   variable does not last between the shell calls of a Claude Code session.\n   A Codex chat with no `AM_ME` (`CODEX_THREAD_ID` is set) joins the same\n   way; its default handle is `codex`. When the output says the wait hook is\n   not installed, tell the user that `amq coop install-hooks --harness codex`\n   installs it, that they approve it in Codex, and that it takes effect in a\n   new chat.\n3. Any other shell: resolve and export the complete context before reading or\n   sending:\n\n   ```bash\n   amq_context=\"$(amq env --me \"\u003Chandle>\" --export)\" && eval \"$amq_context\" &&\n     amq drain --include-body\n   ```\n\nFor a named session, add `--session \u003Cname>` to `amq env`. Treat the evaluated\ncontext as one terminal bound to one session. Use `--session` or `--project` for\ndeliberate routing; do not point a participating command at another queue with a\nraw `--root`.\n\n## Receive under a live wake\n\nIf session-start context says that a wake rings this terminal or that a hook\nwakes this session, or `amq wake check --me \u003Chandle> --json` reports\n`live_wake: true` with an injection mode other than `none`, a doorbell is\ndelivered for you.\nRun `amq drain --include-body` when it fires, then act on the messages.\n\nThe default drain reads at most 20 messages in filename order, including held\nmail. After a full batch, check `amq list --new --limit 1` and continue with bounded drains\nas needed; do not assume the inbox is empty. Use `--limit 0` only for a known,\nmanageable batch. Urgent hold bypass does not change drain order.\n\nDo not run `amq watch`, `amq monitor`, sleep-poll, or start another inbox\nwatcher under that live wake or wait hook. A blocking wait holds your turn while the\ndoorbell queues behind it. When your work is done, finish the turn; do not\nkeep a tool running or send idle check-ins just to wait for mail.\n\nA wake can hold its first doorbell for routine mail with the `hold_normal` and\n`hold_low` settings; `5m` \u002F `30m` is an opt-in example. The configured retry\npolicy applies after the first attempt.\nUrgent priority skips the hold. Ordinary urgent mail still passes through\ndebounce and input deferral; urgent mail with the configured interrupt label\nfollows the interrupt path.\nUse `--priority urgent` on `send` or `reply` for time-critical verdicts and\nunblocking requests. Other review responses remain normal by default.\n\nBy default the wake rings a plain doorbell (text and Enter, never held for a\ndialog); `amq coop exec` prints `dialog guard: plain` or\n`dialog guard: proper (\u003Charness>)`. In Claude Code,\n`amq wake install-dialog-hook` makes the wake hold its doorbell while\nAskUserQuestion, ExitPlanMode, or a permission dialog is open; the held\ndoorbell arrives after you answer, or when that turn ends. Codex needs\n`--harness codex` and the entries trusted in `\u002Fhooks`.\n\nWake settings (hold, debounce, preview, bell, input deferral, interrupt notice)\napply to a running wake without a restart: `amq wake config --me \u003Chandle>`\nshows them, `--hold-normal 5m --wait` sets one and waits for the wake to apply\nit, `--unset \u003Ckey>` falls back, and `--machine` sets this user's default.\nInjection flags are fixed for a running wake. Exit codes and recovery are in\n[wake operations](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fdocs\u002Fwake-operations.md#live-settings).\n\nWithout an injecting wake or a wait hook, use the receive methods in the\noperations guide.\nA notify-only wake (`--inject-mode none`) paired with a supervisor `monitor`\nservice is a separate supported setup.\n\n## Send useful handoffs\n\nFor one related batch, send one completion handoff with artifact paths, the\nrelevant source or digest, checks, failed or pending parts, and the next action\nor actor. Send independent blockers promptly; send a partial result when the\nreceiver can act on it before the rest finishes.\n\nSend status when work starts, a state, decision, or result changes, or an agreed\nescalation is due. Avoid file-by-file completion notices and unchanged check-ins.\nAutomated callers own duplicate suppression by item, revision, and event;\nAMQ threads correlate messages, but do not deduplicate repeated sends.\n\nA reply to a `todo` defaults to `--kind status`; an explicit `--kind todo`\nopens another request. Progress uses `--kind status`;\ncompletion uses `--kind status --labels done`; cancellation uses\n`--kind decision --labels withdrawn`. State the result or cancellation\nhonestly: withdrawing a request does not mean its feature shipped.\nThe last `--refs` entry is the direct reply target; a list of refs is lineage,\nnot a batch-close operation. Close independent requests separately.\n\nAn unanswered message is a reply obligation, not evidence that work started.\nUse the host harness's task and turn records when activity matters. Keep\ndeclared task state, actual execution, approval waits, and delivery presence\nseparate. A live wake, a recent message, or an assigned tracker item does not\nprove a task is running. Do not create work items from old coordination\nmessages without confirming an actual requested outcome and remaining gap.\n\n## Route the task\n\n| Need | Read or run |\n|---|---|\n| Send, reply, drain, inspect receipts, or diagnose | Use [the operations guide](references\u002Foperations.md). |\n| Two-agent research and design, or a received message labeled `workflow:spec` | Use the `amq-spec` skill: do your own research before you read the partner's, then follow the `spec\u002F\u003Ctopic>` thread. |\n| Co-op roles and phased collaboration | Read [co-op mode](references\u002Fcoop-mode.md). |\n| Claude Code Agent Teams | Read [swarm mode](references\u002Fswarm-mode.md). |\n| Cross-project delivery or decision threads | Read [cross-project routing](references\u002Fcross-project.md). |\n| Grok Bot on a registered Mac | Read [registered-machine execution](references\u002Fregistered-machine.md). Select the machine before you resolve the project or session. |\n| Two separate host queues or `amq-bridge` | Use companion `amq-bridge`, never a foreign `--root`. Read [two-host fleets](references\u002Foperations.md#two-host-fleets). |\n| Symphony or Kanban adapters | Read [integrations](references\u002Fintegrations.md). |\n| Message schema and kinds | Read [message format](references\u002Fmessage-format.md). |\n| Multi-round background review | Read [review loop](references\u002Freview-loop.md). |\n| Buzz, ACP, or `amq-acp` | Companion `amq-acp` queues to `AMQ_ACP_TO`; pool workers must not drain. Chat must not pass `--root`, recipients, or argv, and `[Context]` is not routing. Read [amq-acp](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fcmd\u002Famq-acp\u002FREADME.md). |\n| Attach to a running harness session (`amq-remote up`, `submit`, `share`) | Read the [amq-remote reference](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fcmd\u002Famq-remote\u002FREADME.md). |\n| Reach this session from Buzz (`\u002Famq-remote`) | Use the `amq-remote` skill. |\n\nUse `amq \u003Ccommand> --help` for current flags. The repository README is the\ncanonical setup path.\n\n## Safety and delivery rules\n\n- A wake notification is attention, not consumption proof. Use receipts or\n  `--wait-for drained` when delivery proof matters. A `drained` receipt proves\n  ingestion, not that the requested work is complete.\n- Preserve the existing thread when replying. Drain again after a doorbell;\n  the newest complete message body is authoritative.\n- Cleanup is explicit through `amq cleanup`. Do not add automatic deletion.\n- Before any wake mutation, run `amq wake check --me \"\u003Chandle>\" --json`. Act only\n  when `restart_capability=agent_safe`; otherwise preserve state and report the\n  required operator action.\n- Keep cross-host payloads outside privileged inboxes until the configured\n  bridge has authenticated and applied them. Never copy or remote-drain a\n  foreign Maildir as a substitute for routing.\n- Do not translate native Windows injection into Unix `wake` or `coop exec`.\n  Read the platform section in the operations guide when Windows is involved.\n- Dangerous provider bypass flags belong only on an operator-controlled direct\n  `coop exec` command. Do not place them in committed launch configuration.\n\nThe full command catalog, environment precedence, setup flow, platform notes,\noperator gates, and examples are in [the operations guide](references\u002Foperations.md).\n","# AMQ CLI\n\nUse the `amq` CLI for all queue operations. Never edit Maildir files directly.\nAMQ transports coordination; the caller or orchestrator still owns task planning,\nworktrees, approvals, and delivery.\n\n## Start in the correct context\n\nUse the first case that applies:\n\n1. `AM_ME` is set (`amq coop exec` or `amq launch` started the session): run\n   bare `amq` commands. Do not override `--me` or reconstruct the root.\n2. A Claude Code session with no `AM_ME`, such as a chat of the desktop app:\n   run `amq coop join` once; add `--me \"\u003Chandle>\"` when the user named a\n   handle or the output says the default is taken. Later bare `amq` commands\n   in that session use the handle. Follow what the output says about the wake: when\n   the wait hook is not installed, tell the user that `amq coop install-hooks`\n   installs it once per machine and that it takes effect in a new session.\n   When a later command says the session has no handle (a terminal session\n   after `\u002Fclear`), join again. Do not use the `amq env` export here; a shell\n   variable does not last between the shell calls of a Claude Code session.\n   A Codex chat with no `AM_ME` (`CODEX_THREAD_ID` is set) joins the same\n   way; its default handle is `codex`. When the output says the wait hook is\n   not installed, tell the user that `amq coop install-hooks --harness codex`\n   installs it, that they approve it in Codex, and that it takes effect in a\n   new chat.\n3. Any other shell: resolve and export the complete context before reading or\n   sending:\n\n   ```bash\n   amq_context=\"$(amq env --me \"\u003Chandle>\" --export)\" && eval \"$amq_context\" &&\n     amq drain --include-body\n   ```\n\nFor a named session, add `--session \u003Cname>` to `amq env`. Treat the evaluated\ncontext as one terminal bound to one session. Use `--session` or `--project` for\ndeliberate routing; do not point a participating command at another queue with a\nraw `--root`.\n\n## Receive under a live wake\n\nIf session-start context says that a wake rings this terminal or that a hook\nwakes this session, or `amq wake check --me \u003Chandle> --json` reports\n`live_wake: true` with an injection mode other than `none`, a doorbell is\ndelivered for you.\nRun `amq drain --include-body` when it fires, then act on the messages.\n\nThe default drain reads at most 20 messages in filename order, including held\nmail. After a full batch, check `amq list --new --limit 1` and continue with bounded drains\nas needed; do not assume the inbox is empty. Use `--limit 0` only for a known,\nmanageable batch. Urgent hold bypass does not change drain order.\n\nDo not run `amq watch`, `amq monitor`, sleep-poll, or start another inbox\nwatcher under that live wake or wait hook. A blocking wait holds your turn while the\ndoorbell queues behind it. When your work is done, finish the turn; do not\nkeep a tool running or send idle check-ins just to wait for mail.\n\nA wake can hold its first doorbell for routine mail with the `hold_normal` and\n`hold_low` settings; `5m` \u002F `30m` is an opt-in example. The configured retry\npolicy applies after the first attempt.\nUrgent priority skips the hold. Ordinary urgent mail still passes through\ndebounce and input deferral; urgent mail with the configured interrupt label\nfollows the interrupt path.\nUse `--priority urgent` on `send` or `reply` for time-critical verdicts and\nunblocking requests. Other review responses remain normal by default.\n\nBy default the wake rings a plain doorbell (text and Enter, never held for a\ndialog); `amq coop exec` prints `dialog guard: plain` or\n`dialog guard: proper (\u003Charness>)`. In Claude Code,\n`amq wake install-dialog-hook` makes the wake hold its doorbell while\nAskUserQuestion, ExitPlanMode, or a permission dialog is open; the held\ndoorbell arrives after you answer, or when that turn ends. Codex needs\n`--harness codex` and the entries trusted in `\u002Fhooks`.\n\nWake settings (hold, debounce, preview, bell, input deferral, interrupt notice)\napply to a running wake without a restart: `amq wake config --me \u003Chandle>`\nshows them, `--hold-normal 5m --wait` sets one and waits for the wake to apply\nit, `--unset \u003Ckey>` falls back, and `--machine` sets this user's default.\nInjection flags are fixed for a running wake. Exit codes and recovery are in\n[wake operations](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fdocs\u002Fwake-operations.md#live-settings).\n\nWithout an injecting wake or a wait hook, use the receive methods in the\noperations guide.\nA notify-only wake (`--inject-mode none`) paired with a supervisor `monitor`\nservice is a separate supported setup.\n\n## Send useful handoffs\n\nFor one related batch, send one completion handoff with artifact paths, the\nrelevant source or digest, checks, failed or pending parts, and the next action\nor actor. Send independent blockers promptly; send a partial result when the\nreceiver can act on it before the rest finishes.\n\nSend status when work starts, a state, decision, or result changes, or an agreed\nescalation is due. Avoid file-by-file completion notices and unchanged check-ins.\nAutomated callers own duplicate suppression by item, revision, and event;\nAMQ threads correlate messages, but do not deduplicate repeated sends.\n\nA reply to a `todo` defaults to `--kind status`; an explicit `--kind todo`\nopens another request. Progress uses `--kind status`;\ncompletion uses `--kind status --labels done`; cancellation uses\n`--kind decision --labels withdrawn`. State the result or cancellation\nhonestly: withdrawing a request does not mean its feature shipped.\nThe last `--refs` entry is the direct reply target; a list of refs is lineage,\nnot a batch-close operation. Close independent requests separately.\n\nAn unanswered message is a reply obligation, not evidence that work started.\nUse the host harness's task and turn records when activity matters. Keep\ndeclared task state, actual execution, approval waits, and delivery presence\nseparate. A live wake, a recent message, or an assigned tracker item does not\nprove a task is running. Do not create work items from old coordination\nmessages without confirming an actual requested outcome and remaining gap.\n\n## Route the task\n\n| Need | Read or run |\n|---|---|\n| Send, reply, drain, inspect receipts, or diagnose | Use [the operations guide](references\u002Foperations.md). |\n| Two-agent research and design, or a received message labeled `workflow:spec` | Use the `amq-spec` skill: do your own research before you read the partner's, then follow the `spec\u002F\u003Ctopic>` thread. |\n| Co-op roles and phased collaboration | Read [co-op mode](references\u002Fcoop-mode.md). |\n| Claude Code Agent Teams | Read [swarm mode](references\u002Fswarm-mode.md). |\n| Cross-project delivery or decision threads | Read [cross-project routing](references\u002Fcross-project.md). |\n| Grok Bot on a registered Mac | Read [registered-machine execution](references\u002Fregistered-machine.md). Select the machine before you resolve the project or session. |\n| Two separate host queues or `amq-bridge` | Use companion `amq-bridge`, never a foreign `--root`. Read [two-host fleets](references\u002Foperations.md#two-host-fleets). |\n| Symphony or Kanban adapters | Read [integrations](references\u002Fintegrations.md). |\n| Message schema and kinds | Read [message format](references\u002Fmessage-format.md). |\n| Multi-round background review | Read [review loop](references\u002Freview-loop.md). |\n| Buzz, ACP, or `amq-acp` | Companion `amq-acp` queues to `AMQ_ACP_TO`; pool workers must not drain. Chat must not pass `--root`, recipients, or argv, and `[Context]` is not routing. Read [amq-acp](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fcmd\u002Famq-acp\u002FREADME.md). |\n| Attach to a running harness session (`amq-remote up`, `submit`, `share`) | Read the [amq-remote reference](https:\u002F\u002Fgithub.com\u002Favivsinai\u002Fagent-message-queue\u002Fblob\u002Fmain\u002Fcmd\u002Famq-remote\u002FREADME.md). |\n| Reach this session from Buzz (`\u002Famq-remote`) | Use the `amq-remote` skill. |\n\nUse `amq \u003Ccommand> --help` for current flags. The repository README is the\ncanonical setup path.\n\n## Safety and delivery rules\n\n- A wake notification is attention, not consumption proof. Use receipts or\n  `--wait-for drained` when delivery proof matters. A `drained` receipt proves\n  ingestion, not that the requested work is complete.\n- Preserve the existing thread when replying. Drain again after a doorbell;\n  the newest complete message body is authoritative.\n- Cleanup is explicit through `amq cleanup`. Do not add automatic deletion.\n- Before any wake mutation, run `amq wake check --me \"\u003Chandle>\" --json`. Act only\n  when `restart_capability=agent_safe`; otherwise preserve state and report the\n  required operator action.\n- Keep cross-host payloads outside privileged inboxes until the configured\n  bridge has authenticated and applied them. Never copy or remote-drain a\n  foreign Maildir as a substitute for routing.\n- Do not translate native Windows injection into Unix `wake` or `coop exec`.\n  Read the platform section in the operations guide when Windows is involved.\n- Dangerous provider bypass flags belong only on an operator-controlled direct\n  `coop exec` command. Do not place them in committed launch configuration.\n\nThe full command catalog, environment precedence, setup flow, platform notes,\noperator gates, and examples are in [the operations guide](references\u002Foperations.md).\n",{"name":5,"version":49,"metadata":50,"description":7},"0.143.0",{"compatibility":51,"short-description":52},"claude-code, codex-cli, grok-cli, antigravity-cli","Inter-agent messaging via AMQ CLI","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill amq-cli",{"tool":69,"command":70},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill amq-cli",{"tool":72,"command":73},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill amq-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002FSKILL.md",true,[77,83,87,91,95,99,103,107],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcoop-mode.md","REFERENCE","参考文档",5833,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Fcoop-mode.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fcross-project.md",6999,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Fcross-project.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fintegrations.md",2680,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Fintegrations.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fmessage-format.md",4363,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Fmessage-format.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Foperations.md",33424,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Foperations.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fregistered-machine.md",6144,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Fregistered-machine.md",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Freview-loop.md",1701,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Freview-loop.md",{"path":108,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fswarm-mode.md",2367,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Favivsinai\u002Fagent-message-queue\u002Fskills\u002Famq-cli\u002Freferences\u002Fswarm-mode.md",[112,122,130,138,146,154],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":121},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":121},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":121},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":121},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":121},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":121},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]