Agent skill

Amq Spec

by hashgraph-online in hashgraph-online/awesome-codex-plugins

Use two agents to research a design independently and converge on one specification through AMQ.

Apache-2.0Auto-check passed

Install Amq Spec

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins amq-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/avivsinai/agent-message-queue/skills/amq-spec .claude/skills/amq-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "amq-spec" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec into .claude/skills/amq-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amq-spec", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins amq-spec --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/avivsinai/agent-message-queue/skills/amq-spec .agents/skills/amq-spec && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "amq-spec" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec into .agents/skills/amq-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amq-spec", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins amq-spec --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/avivsinai/agent-message-queue/skills/amq-spec .cursor/skills/amq-spec && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "amq-spec" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec into .cursor/skills/amq-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amq-spec", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/avivsinai/agent-message-queue/skills/amq-spec

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins amq-spec --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/avivsinai/agent-message-queue/skills/amq-spec .gemini/skills/amq-spec && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "amq-spec" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec into .gemini/skills/amq-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amq-spec", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins amq-spec

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/avivsinai/agent-message-queue/skills/amq-spec .github/skills/amq-spec && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "amq-spec" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec into .github/skills/amq-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amq-spec", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins amq-spec --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/avivsinai/agent-message-queue/skills/amq-spec .opencode/skills/amq-spec && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "amq-spec" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/avivsinai/agent-message-queue/skills/amq-spec into .opencode/skills/amq-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amq-spec", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: amq-spec
GitHub stars: 1.3k
Token cost: ~2.1k tokens
SKILL.md length: 868 words
Files: 2 (incl. references)
Skills in repo: 714
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Use two agents to research a design independently and converge on one specification through AMQ.

Works in 3 steps: Verify AMQ is available: which amq → Verify the AMQ root is discoverable… → Use thread name: spec/
Collaborative design
SKILL.md covers Parse Input, Pre-flight, First Action: Send problem to… and Label Convention, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Amq Spec is an agent skill from hashgraph-online/awesome-codex-plugins. Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/spec-workflow.md`).

The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

Collaborative design
Messages labeled workflow:spec
Use amq-cli for ordinary coordination

Example prompts

“/amq-spec”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Verify AMQ is available: which amq
Verify the AMQ root is discoverable (.amqrc, AMQ env vars, or the default .agent-mail layout); otherwise run: amq coop init
Use thread name: spec/

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Amq Spec loads about 2.1k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 868 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its Apache-2.0 licence (© hashgraph-online). 868 words, ~2,072 tokens.

Download SKILL.mdSave it as .claude/skills/amq-spec/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: amq-spec
description: Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.
version: 0.92.0
argument-hint: <description of what to design> [with <partner>]
metadata.short-description: Multi-agent collaborative spec workflow
metadata.compatibility: claude-code, codex-cli

AMQ collaborative specification

Invoke the amq-spec skill through your host's skill interface. It defines a structured two-agent specification flow; invocation syntax depends on the host.

Use canonical phases in order: Research -> Discuss -> Draft -> Review -> Present -> Execute

Detailed step-by-step protocol lives in references/spec-workflow.md. This file is the concise operational entrypoint.

Parse Input

From the user prompt, extract:

topic: short kebab-case spec name (e.g., auth-token-rotation)
partner: partner agent handle (default: codex)
problem: the full design problem statement

If topic/problem are unclear, ask for clarification.

Pre-flight

Verify AMQ is available: which amq
Verify the AMQ root is discoverable (.amqrc, AMQ env vars, or the default .agent-mail layout); otherwise run: amq coop init
Use thread name: spec/<topic>

First Action: Send problem to partner IMMEDIATELY

The entire point of the spec workflow is parallel research — both agents exploring the problem independently, then comparing notes. Every second you spend researching before sending is a second your partner sits idle waiting for the problem statement. That's why the send comes first, even though your instinct might be to "research first to give better context."

bash

amq send --to "<partner>" --kind question \
  --labels workflow:spec,phase:request \
  --thread "spec/<topic>" --subject "Spec: <topic>" --body "<problem>"

Send the user's problem description verbatim — your own analysis goes in the research phase, not the kickoff. If you pre-analyze, you bias the partner's independent research, which defeats the purpose of having two perspectives.

Label Convention

Labels are how both agents and the receiver-side protocol table know which phase the conversation is in. Use existing AMQ kinds plus labels to express spec workflow semantics:

Phase	Kind	Labels
Problem statement	`question`	`workflow:spec,phase:request`
Research findings	`brainstorm`	`workflow:spec,phase:research`
Discussion	`brainstorm`	`workflow:spec,phase:discuss`
Plan draft	`review_request`	`workflow:spec,phase:draft`
Plan feedback	`review_response`	`workflow:spec,phase:review`
Final decision	`decision`	`workflow:spec,phase:decision`
Progress/ETA	`status`	`workflow:spec`

Quick Command Skeleton

bash

# Initiate spec with problem statement
amq send --to "<partner>" --kind question \
  --labels workflow:spec,phase:request \
  --thread "spec/<topic>" --subject "Spec: <topic>" --body "<problem>"

# Submit independent research
amq send --to "<partner>" --kind brainstorm \
  --labels workflow:spec,phase:research \
  --thread "spec/<topic>" --subject "Research: <topic>" --body "<findings>"

# Discuss and align
amq send --to "<partner>" --kind brainstorm \
  --labels workflow:spec,phase:discuss \
  --thread "spec/<topic>" --subject "Discussion: <topic>" --body "<analysis>"

# Draft plan
amq send --to "<partner>" --kind review_request \
  --labels workflow:spec,phase:draft \
  --thread "spec/<topic>" --subject "Plan: <topic>" --body "<plan>"

# Review plan
amq send --to "<partner>" --kind review_response \
  --labels workflow:spec,phase:review \
  --thread "spec/<topic>" --subject "Review: <topic>" --body "<feedback>"

# Optional final decision message
amq send --to "<partner>" --kind decision \
  --labels workflow:spec,phase:decision \
  --thread "spec/<topic>" --subject "Final: <topic>" --body "<final plan>"

When You RECEIVE a Spec Message

If you receive a message labeled workflow:spec, your action depends on the phase:

Label	Your action
`phase:request`	Read the problem statement, do your own independent research first, then submit findings as `brainstorm` + `phase:research`
`phase:research`	Before reading: check if you've already submitted your own research on this thread. If not, do your own research and submit it first. This preserves research independence — reading the partner's findings before forming your own view contaminates your perspective. Once your research is submitted, read the thread and start discussion as `brainstorm` + `phase:discuss`.
`phase:discuss`	Reply with your analysis, continue discussion until aligned
`phase:draft`	Review the plan and send feedback as `review_response` + `phase:review`. Your job here is review, not implementation — the plan needs to survive scrutiny before anyone builds it.
`phase:review`	Revise plan if needed, or confirm alignment
`phase:decision`	Stop. A `phase:decision` message is agent-to-agent alignment, not user approval, so do not implement from a spec decision alone. Only the human authorizes implementation, recorded as a structural gate to the initialized human handle (conventionally `user`; see the Operator Gates section in the amq-cli operations guide). Wait until the initiator confirms the human approved on the gate thread and assigns you work.

Why the partner doesn't implement: The spec workflow is a design process. The initiator owns the relationship with the user and presents the final plan. If the partner implements without approval, the user loses control over what gets built. The agent-to-agent phase:decision message is alignment, not authorization: human approval is a structural gate to the initialized human handle, and partner agents must not implement from a spec decision alone. Implementation starts only after the initiator explicitly tells you the human approved and assigns work.

Show full SKILL.md (308 more words)Show less

Protocol Discipline

Use the existing wake while waiting — if a live injecting wake notifies this terminal, finish independent work and yield. On its doorbell, run amq drain --include-body. Do not start amq watch, amq monitor, or a background polling loop for peer replies. Check amq wake check --me <handle> --json when the capability is unknown. A bounded watch is a fallback only without an injecting wake; notify-only supervisor consumers remain valid.

These rules exist because violations silently break the workflow's value proposition:

Send before researching — parallel research is the whole point. Pre-researching wastes your partner's time and biases the outcome toward your initial framing.
Submit your own research before reading partner's — reading first contaminates your independent perspective. Two agents who read the same code and reach the same conclusion is less valuable than two agents who explore independently and then compare notes.
Don't skip phases — each phase builds on the previous. Collapsing directly to a finished spec skips the discussion where misunderstandings surface.
Use spec/<topic> threads and the label convention — this is how both agents (and the tooling) know which phase the conversation is in. Without consistent labels, the receiver-side protocol table above breaks.
Don't enter plan mode during research if it blocks tool usage — you need tools to explore the codebase.
Present the final plan to the user before executing, and raise a structural gate. The initiator owns the user relationship. After the decision phase, present the plan in chat AND raise a structural human gate using the initialized human handle (conventionally user) on a stable gate/<topic> thread, then wait for explicit approval on that thread. The agent-to-agent phase:decision message is alignment only; partner agents must not implement from it. See the Operator Gates section in the amq-cli operations guide for canonical mechanics, seeding, and guardrails.

Reference

For full protocol details, templates, and phase gates, see:

references/spec-workflow.md

Files

SKILL.md and 1 other file (references) in plugins/avivsinai/agent-message-queue/skills/amq-spec of hashgraph-online/awesome-codex-plugins.

SKILL.md
references/spec-workflow.md

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Amq Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Amq Spec compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Amq Spec this skillhashgraph-online/awesome-codex-plugins	1.3k	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
Convergenceparcadei/Continuous-Claude-v3	3.9k	1 repos	~316	Automated safety check: Notes	MIT	8 mo ago
Convergence StudyFreedomIntelligence/OpenClaw-Medical-Skills	3.1k	1 repos	~1.1k	Automated safety check: Notes	None	2 mo ago
Gsd Plan Review Convergenceopen-gsd/gsd-core	10k	1 repos	~1k	Automated safety check: Notes	MIT	yesterday
Narrative Convergenceaeonfun/aeon	767	—	~2.2k	Automated safety check: Pass	MIT	2 days ago
Financial Independence Roadmapmohitagw15856/pm-claude-skills	1.4k	—	~1.2k	Automated safety check: Pass	MIT	yesterday

Similar skills

Convergence
parcadei/Continuous-Claude-v3
Problem-solving strategies for convergence in real analysis. An agent skill from parcadei/Continuous-Claude-v3.
3.9k GitHub starsUsed in 1 repo~316 tokens
Research & ScienceAuto-check: notes
Convergence Study
FreedomIntelligence/OpenClaw-Medical-Skills
Spatial and temporal convergence analysis with Richardson extrapolation and Grid Convergence Index (GCI) for solution verification
3.1k GitHub starsUsed in 1 repo~1.1k tokens
Auto-check: notes
Gsd Plan Review Convergence
open-gsd/gsd-core
Cross-AI plan convergence - replan until review concerns are resolved.
10k GitHub starsUsed in 1 repo~1k tokens
Auto-check: notes
Narrative Convergence
aeonfun/aeon
Cross-skill signal detector - finds entities or themes surfaced independently by 3+ different skill categories within 48h and surfaces them as high-confidence write opportunities
767 GitHub stars~2.2k tokensUpdated 2 days ago
Auto-check passed
Financial Independence Roadmap
mohitagw15856/pm-claude-skills
Map a realistic path toward financial independence — the number you'd actually need, your savings rate's massive effect on the timeline, and the honest tradeoffs.
1.4k GitHub stars~1.2k tokensUpdated yesterday
Product & Project ManagementAuto-check passed
Ap Independent Checker
Spielewoy/autoprompt-skill
Independently review the exact result and run its real checks in one context, using isolated resources and without changing the deliverable.
1.3k GitHub stars~777 tokensUpdated 5 days ago
Agent WorkflowsAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo

Anime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
1.3k GitHub stars~922 tokensUpdated today
Auto-check passed
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
1.3k GitHub stars~1k tokensUpdated today
Auto-check passed
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
1.3k GitHub stars~1.7k tokensUpdated today
Auto-check passed
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
1.3k GitHub stars~2.4k tokensUpdated today
Auto-check passed
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
1.3k GitHub stars~2.9k tokensUpdated today
Auto-check passed
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
1.3k GitHub stars~618 tokensUpdated today
Auto-check passed

Questions about Amq Spec

What does Amq Spec do?

Use two agents to research a design independently and converge on one specification through AMQ. Amq Spec is an agent skill from hashgraph-online/awesome-codex-plugins. Use two agents to research a design independently and converge on one specification through AMQ.

When should I use Amq Spec?

Amq Spec fits situations like: collaborative design; messages labeled workflow:spec; use amq-cli for ordinary coordination.

How do I install Amq Spec in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a claude-code`. Or copy the skill folder (plugins/avivsinai/agent-message-queue/skills/amq-spec in hashgraph-online/awesome-codex-plugins) into .claude/skills/amq-spec in your project. Claude Code loads it when a task matches its description.

How do I install Amq Spec in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a codex`. Or copy the skill folder (plugins/avivsinai/agent-message-queue/skills/amq-spec in hashgraph-online/awesome-codex-plugins) into .agents/skills/amq-spec in your project. Codex loads it when a task matches its description.

Can I use Amq Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill amq-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amq-spec, .gemini/skills/amq-spec, .github/skills/amq-spec and .opencode/skills/amq-spec in your project.

What does Amq Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Amq Spec is instructions for the agent only.

Does Amq Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Amq Spec safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Amq Spec use?

Amq Spec is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Amq Spec use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Amq Spec?

Skills that share tags, products or a category with Amq Spec: Convergence (parcadei/Continuous-Claude-v3, 3.9k stars), Convergence Study (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k stars), Gsd Plan Review Convergence (open-gsd/gsd-core, 10k stars) and Narrative Convergence (aeonfun/aeon, 767 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Amq Spec?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Amq Spec

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

AMQ collaborative specification

Parse Input

Pre-flight

First Action: Send problem to partner IMMEDIATELY

Label Convention

Quick Command Skeleton

When You RECEIVE a Spec Message

Protocol Discipline

Reference

Files

Compare with similar skills

Similar skills

More from hashgraph-online/awesome-codex-plugins

Questions about Amq Spec