Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/hashgraph-online/awesome-codex-plugins --skill domain명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
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.
| name | domain |
| description | Load the AgentOps language and |
Use this read-only library when an AgentOps term or bounded-context boundary needs precise meaning.
Returning the exact contract definition works because two contexts that read the same source line cannot drift apart on a term; a paraphrase reintroduces the ambiguity the lookup exists to remove.
Named failure mode — synonym smuggling: answering with a near-synonym ("close" for "verdict") that quietly imports lifecycle authority the term does not carry.
Anti-pattern: defining a term from memory because the contract file is one read away. Corrective: always cite the definition and its source path from the live contract, even for terms you are sure about.
docs/contracts/ubiquitous-language.md for the term.docs/contracts/bounded-contexts.yaml only when ownership or a port
boundary matters.Do not invent synonyms that imply lifecycle authority. In particular, Plan, Candidate, manifest, verdict, revision, strategy, and adapter are semantic terms; queue, claim, lease, close, land, release, and delivery belong to caller systems rather than AgentOps core state.
Vocabulary changes are normal source edits to the two contracts above. This skill does not promote terms, mutate a knowledge index, or create continuation.