Cq
Share and confirm agent-learned pitfalls, API quirks, and team knowledge so you stop rediscovering the same failures across projects.
Overview
cq is a plugin marketplace for the Operate phase that adds a shared knowledge commons so AI agents can find, share, and confirm collective pitfalls and API quirks.
What is this marketplace?
- Mozilla AI marketplace plugin for a shared knowledge commons across agents
- Find, share, and confirm collective knowledge to avoid repeated pitfalls
- Tags include MCP, agent-learning, api-quirks, and team-knowledge
- Focused on pitfall avoidance rather than generic documentation search
- Single cq plugin sourced from ./plugins/cq
- 1 plugin in marketplace
- Plugin name: cq
- Owner: Mozilla AI
Community signal: 1.2k GitHub stars.
What problem does it solve?
Agents and solo builders keep relearning the same integration failures because lessons live in chat logs instead of a confirmed, searchable commons.
Who is it for?
Builders and small teams running multiple agent projects who want Mozilla-style shared learning with confirmation, including MCP-aware setups.
Skip if: Anyone who needs proprietary knowledge locked in a single vault with no sharing, or who only wants inline linting with no knowledge base.
What do I get? / Deliverables
After adding cq, agents can pull and contribute confirmed team knowledge so repeated API and workflow pitfalls surface before you burn another debugging cycle.
- Enabled cq plugin wired to the knowledge commons
- Queryable confirmed knowledge for agents during integration and iteration work
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Collective knowledge pays off most when you iterate in production and refine how agents work, but the commons is useful whenever agents touch unfamiliar APIs. Iterate is the canonical shelf because cq’s promise is compounded learning from confirmed failures—not one-shot code generation.
How it compares
Agent knowledge commons marketplace with MCP affordances, not a code generator or DevOps deploy plugin.
Common Questions / FAQ
Who is Cq for?
Claude and agent users who want a shared, confirmable store of pitfalls, API quirks, and lessons so work does not restart from zero each sprint.
When should I use Cq?
Use it when iterating on integrations or ops workflows and whenever an agent is about to touch an API you have failed on before—query the commons first, contribute after you verify a fix.
How do I add Cq to my agent?
Install the mozilla-ai Cq marketplace in Claude Code, enable the Cq plugin from ./plugins/Cq, and connect any documented MCP or agent-commons flows per Mozilla AI setup.