feat(adapter/amazon-q): Amazon Q Developer CLI skill runtime
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Read docs/rfcs/RFC-AI-0004.md and inspect the existing .claude/skills/ shape first. Consult the Amazon Q CLI and Q agents references, then verify how skills, tools/* bridges, allow-lists, trust prompts, and interactive confirmations map to Q. Done means the mapping and invocation pattern work and the sandbox and HITL behavior are documented.
Written by the indexing model from the issue text.
Description
Goal: Bring Amazon Q Developer CLI (q) to feature parity with Claude Code as a skill runtime. Grounds: RFC-AI-0004 Principle 3 — Vendor neutrality.
Why Amazon Q: Default agentic CLI in many AWS-shop environments — corporate adopters, federal / regulated environments where Amazon Q is the only sanctioned LLM tool. Several ASF projects with AWS-aligned committer bases have asked about Q compatibility. Coverage matters less for individual maintainers, more for organisational adoption.
What "parity" means:
- Skills under
.claude/skills/<name>/SKILL.mdare invokable fromq(Q Developer CLI) - The
tools/*bridges are reachable —qsupports custom tools via its agent configuration - Sandbox parity:
qhas its own command-permission model (allow-lists, "trust" prompts) — document the mapping - HITL primitives:
qsupports interactive confirmation for tool use — verify and document
Suggested approach:
- Map
SKILL.md→ Q's agent configuration format (~/.aws/amazonq/agents/<name>.json+ system prompts) - Document skill-invocation pattern
- Map sandbox parity —
qallowlists are the native fit for the framework's command-permission discipline
Reference:
- RFC-AI-0004:
docs/rfcs/RFC-AI-0004.md - Amazon Q Developer CLI: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line.html
- Q agents: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/cli-agents.html
- Existing skill shape:
.claude/skills/
- Dominant language
- Python
- Stars
- 113
- Forks
- 95
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 348
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/magpie
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Explore Claude Code mods across the skill familiesPossibly taken @Kaap10 claimed this 5 days ago. Opencapability:platform enhancement family:ci family:docs family:issue family:pairing family:pr-management family:release-management family:security family:setup family:tools family:utilities substrate:framework-dev
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/magpie#1497 · 3 comments ·
Maintainers usually reply within 1 day
-
feat(adapter/grok): xAI Grok agent harness and adversarial-review backendPossibly taken A pull request linked to this issue is open or already merged. Opencapability:platform enhancement family:tools
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/magpie#1416 · 1 comment ·
Maintainers usually reply within 1 day
-
capability:authoring enhancement kind:perf
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
esphome/esphome.io#7657 ·
Maintainers usually reply within 1 day
-
comp/gateway comp/plugins duplicate P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NousResearch/hermes-agent#137019 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Kumo-Tabular weights unreachable behind restrictive egress proxies (Xet + plain HTTP both fail)Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
NVIDIA/structured-data-models#1091 ·
Maintainers usually reply within 1 day
-
[work-item] adam-adae-worsening-emergence: conform spec.yaml to the specification style contract (REQ-1280)Possibly taken @muse-yamaa-bot claimed this today. Openwork-item
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day