CliqHub

The team registry for cliq

CliqHub is where agent teams become a shared resource. It’s a public registry — a browsable, searchable catalog of ready-made teams that anyone can install with a single command. No git cloning, no manual file copying, no guessing at directory structures. Find a team, install it, run it.

cliq team install hub://@cliq/feature-dev-js
cliq assemble @cliq/feature-dev-js
cliq req requirements.md
cliq run

Four commands. A seven-agent pipeline — git branching, architecture, TDD, code review, merge resolution, and PR creation — running in your project. Built by someone who already solved the workflow problem. Installed in seconds.

That’s what CliqHub makes possible.

---

Why a registry matters

A cliq team encodes real expertise. The feature-dev-js team didn’t appear overnight — it represents a refined workflow: how to set up a git branch safely, how to architect before coding, how to write tests before implementation, how to review with automated quality gates, how to handle merge conflicts, how to finalize with a clean PR. Someone figured all of that out, encoded it in roles and a workflow DAG, and now it’s yours to use.

Without a registry, that knowledge stays locked on one machine. With CliqHub, it becomes infrastructure.

The same way npm made JavaScript packages shareable, Docker Hub made container images discoverable, and Terraform Registry made infrastructure modules reusable — CliqHub makes agent teams a community resource. One expert builds the soc2-audit team. Every startup that needs SOC2 compliance uses it. One DevOps engineer builds incident-response. Every on-call team benefits.

---

Discover teams

Browse by domain, search by keyword, or explore what’s popular. Every team on CliqHub has a detail page showing:

• Description — what the team does and what problem it solves
• Workflow visualization — the full phase DAG rendered visually, with phase types (standard, gate, exec, support) color-coded and gate commands visible
• Roles — every agent’s complete role definition, expandable inline so you can read the full persona, responsibilities, boundaries, and workflow instructions before installing
• Requirements — minimum cliq version and required tools (git, npm, etc.)
• Version history — changelogs for every published version
• Install count — how many people are using this team
• Tags and domain — find teams by category

You never install blind. You read the roles. You study the workflow. You understand exactly what you’re getting.

Search from the terminal

Discovery and browsing happen on the CliqHub web UI. From the CLI, you can fetch details about a specific team:

cliq team info hub://@cliq/feature-dev-js

Shows the team’s description, workflow phases, roles, version history, install command, and tags — everything you need to decide whether it fits your use case.

---

Configuration

Add to ~/.cliqrc/settings.json:

{
  "hub": {
    "registry_url": "https://cliqhub.io"
  }
}

Field	Default	Description
registry_url	https://cliqhub.io	Registry base URL. Override for self-hosted or local development

cliq team install hub://@cliq/feature-dev-js
cliq team info hub://@cliq/feature-dev-js
cliq team install hub://@other/team

Browsing, searching, and installing are anonymous — no account required. You only need to authenticate for publishing teams.

---

Next steps

Goal	Page
Install and update teams	Installing & Using
Build your own team	Team Development Overview
Publish a team to CliqHub	Publishing