SkillAgentSearch skills...

Clade

Turn Claude Code and Codex from chat assistants into autonomous coding systems

Install / Use

claude mcp add shenxingy -- npx -y github:shenxingy/Clade

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

81/100

Category

Automation

Supported Platforms

Claude Code
Claude Desktop
OpenAI Codex

Our assessment of Clade

Clade scores 81/100 on our quality scale, 2052nd of 2,864 Automation skills we index.

Its MCP Server is 15 KB long, well organised into 25 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 2 days ago, so Clade is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Clade compared with similar skills

All 4 of these similar skills score higher than Clade; compare them before choosing.

SkillScoreStarsUpdatedFormat
Clade (this skill)by shenxingy81102d agoMCP Server
Agent-Reachby Panniantong10087.5k16d agoCLAUDE.md
headroomby headroomlabs-ai10074.2ktodayCLAUDE.md
rufloby ruvnet10073.7ktodayCLAUDE.md
CowAgentby zhayujie10047.2ktodayCLAUDE.md

Frequently asked questions

How do I install Clade?
Run claude mcp add shenxingy -- npx -y github:shenxingy/Clade. The install tabs above show the steps for each supported agent.
Which AI agents does Clade work with?
It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is Clade safe to use?
It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is Clade still maintained?
The repository was last updated 2 days ago, so Clade is actively maintained.

English | 中文

<p align="center"> <img src="assets/banner.svg" alt="Clade" width="800" /> </p> <p align="center"> <a href="https://pypi.org/project/clade-mcp/"><img src="https://img.shields.io/pypi/v/clade-mcp?label=MCP%20Server&color=blue" alt="PyPI" /></a> <a href="https://github.com/shenxingy/clade/blob/main/CONTRIBUTING.md"><img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs Welcome" /></a> <a href="https://github.com/shenxingy/clade/labels/good%20first%20issue"><img src="https://img.shields.io/github/issues/shenxingy/clade/good%20first%20issue" alt="good first issue" /></a> </p>

Clade

A provider-neutral delivery control plane for coding agents.

Clade turns agent work into reviewable delivery: resolved execution identity, immutable evidence, calibrated verification, correction learning, and truthful Git history. It ships native Claude Code and Codex surfaces plus an MCP bridge for other clients.

Use the full Claude Code framework, the native Codex plugin, or the provider-neutral MCP bridge. The optional Orchestrator adds a provider/model registry, evidence and eval control plane, verifier-aware routing, delivery state, and multi-project fleet truth.

If this saves you time, a star helps others find it. Something broken? Open an issue.

Blog post: Building Clade — motivation, design decisions, and lessons learned.

Table of Contents

  1. Install
  2. MCP Server
  3. The Trust Loop
  4. What It Does
  5. Self-Learning Mechanisms
  6. Skills
  7. Supported Languages
  8. Documentation
  9. Dotfile Sync
  10. Architecture
  11. OpenClaw Integration
  12. Contributing
  13. License

Install

Claude Code — Full Framework

git clone https://github.com/shenxingy/clade.git
cd clade && ./install.sh

Installs skills, hooks, agents, scripts, and safety guardian. Start a new Claude Code session to activate.

The same run also wires the other runtimes it detects: a managed policy block in ~/.codex/AGENTS.md (Codex), bridge agents/hooks for Kimi Code (~/.kimi-code/), and the vendor-neutral ground rules from configs/AGENTS.md at ~/.agents/AGENTS.md and ~/.kimi-code/AGENTS.md — the same don't-block policy text for every AGENTS.md-aware runtime. See docs/codex.md for the per-vendor contract.

Requires: jq. Platform: Linux, macOS, and Windows via Git Bash (native CMD/PowerShell without bash is out of scope).

Codex — Native Plugin

codex plugin marketplace add shenxingy/Clade
codex plugin add clade@clade

Start a new Codex thread, then invoke a workflow naturally or explicitly with the plugin-qualified names $clade:review, $clade:verify, $clade:investigate, $clade:green, and the other bundled skills. Open /hooks once to review and trust Clade's session-context and command-safety hooks.

Run $clade:codex-usage setup minimal for a compact native footer. $clade:codex-usage defaults to the equally compact project(branch)-9% (6d) pace view; icon and detail styles are optional. It never reads or exposes Codex credentials.

The native plugin runs directly in Codex and does not require Claude Code. It currently ships 27 provider-native core workflows; Claude-specific overnight orchestration remains in the full framework. See Native Codex Support.

MCP Server Only

If you want Clade tools in another MCP client:

pip install --upgrade clade-mcp

The Codex execution runtime arrived in 0.2.0 and keeps Claude as the backwards-compatible default; the package is now at 0.3.1. See MCP Server below for configuration and the MCP package guide for all runtime and sandbox options.

MCP Server — Use Skills in Any AI Editor

The MCP package exposes 34 bundled Clade skills, plus compatible user-installed skills, as callable tools via the Model Context Protocol. It can execute them with either Claude or Codex.

Claude Desktop or another client using Claude as its runtime:

{
  "mcpServers": {
    "clade": { "command": "uvx", "args": ["clade-mcp"] }
  }
}

Cursor / Windsurf:

{
  "mcpServers": {
    "clade": {
      "command": "clade-mcp",
      "env": { "CLADE_RUNTIME": "codex" }
    }
  }
}

CLADE_RUNTIME accepts claude (the backwards-compatible default), codex, or auto. Prefer the native Codex plugin inside Codex itself; adding the MCP server there would duplicate skills and spawn nested agent sessions. The same applies inside the full Claude Code framework, where Clade skills are already native.

The Trust Loop

Clade keeps six concerns separate so a green-looking run cannot silently change runtime, account, history, or evidence semantics:

| Layer | Contract | |---|---| | Execution identity | Agent runtime, native connection, inference provider, wire protocol, and opaque model are resolved independently | | Evidence | Every attempt can carry append-only task, timing, Git SHA, test, oracle, cost, artifact, and delivery evidence with digest-linked revisions | | Verifier calibration | Cheap→strong routing is default-off and requires deterministic verifier evidence; observational reports never mutate policy | | Correction learning | Explicit corrections pair rejected work with human context and create reviewable eval candidates; no automatic ground-truth path | | Delivery | Exact reviewed SHA, live PR topology, CI, and repository policy determine merge semantics; squash is never the universal default | | Fleet truth | Provider catalogs, task state, usage, evidence health, and delivery status remain provenance- and freshness-aware across projects |

Evidence and oracle approval are gates and audit material, not authorization to publish or merge. Repository policy and explicit authority still control external side effects.

What It Does

| When | What fires | Effect | |------|-----------|--------| | Session opens in a git repo | session-context.sh | Loads git context, handoff state, correction rules, model guidance | | Session opens in a git repo | commit-archeology.sh | Mines git log for recurring fix patterns (wiring/deploy/compat gaps, Claude-overridden) — injects top 4 | | Claude runs a bash command | pre-tool-guardian.sh | Blocks dangerous ops: migrations, rm -rf, force push, DROP TABLE | | Claude edits code | post-edit-check.sh | Async type-check (tsc, pyright, cargo check, go vet, etc.) | | You correct Claude | correction-detector.sh | Logs correction, prompts Claude to save a reusable rule | | Claude marks task done | verify-task-completed.sh | Adaptive quality gate: compile + lint, build + test in strict mode |

See How It Works for the hook reference. 32 hooks ship; the guide documents the ones you are likely to tune — ls configs/hooks/ is the complete list.

Self-Learning Mechanisms

Three mechanisms keep Clade aligned with reality:

  • Commit Lessons (reactive) — commit-archeology.sh mines git log for recurring fix patterns (wiring-gap, deploy-gap, compat-gap, claude-overridden) and injects the top 4 at every session start.
  • Doc Align (preventive) — doc-align.py declares shared facts in docs/facts.json (auto-derived from filesystem); checks/auto-fixes drift across every *.md. A PostToolUse hook flags drift the moment you edit a doc, so stale counts never reach commit.
  • Correction Pairing (human-grounded) — explicit corrections pair rejected work with the replacement context. Orchestrator corrections enter quarantine as eval candidates; only explicit human review can promote corpus truth.

Commit Lessons and Doc Align run locally in the full Claude distribution and silently no-op in repos that have not opted in. Correction evidence never turns an inferred revert or async signal into an automatic rule.

See Self-Learning Mechanisms for full details, detectors, schemas, and tunable env vars.

Skills (144)

Core Workflow

| Skill | What it does | |-------|-------------| | /commit | Create repository-adaptive checkpoint commits; publish when authorized | | /sync | Check off completed TODOs, append session summary to PROGRESS.md | | /review | Walks every VERIFY.md checkpoint, fixing failures in-session until all pass | | /green | Runs the repo's real CI gates locally and drives them green — never weakens a gate |

Autonomous Operation

| Skill | What it does | |-------|-------------| | /start | Autonomous session launcher — morning brief, overnight runs, cross-project patrol | | /loop GOAL | Goal-driven improvement loop — supervisor plans, workers execute in parallel | | /iloop TASK | In-session iterative loop — Stop hook re-prompts until done (no background workers) | | /batch-tasks | Execute TODO steps via unattended sessions (serial or parallel) | | /orchestrate | Decompose goals into tasks for worker execution | | /handoff | Save session state for context relay between agents | | /pickup | Resume from previous handoff — zero-friction restart | | /worktree | Create git worktrees for parallel sessions | | /poke | Heartbeat after esc — 3-line status, auto-continues if still progressing | | /status | Session dashboard — background agents, loops, worktrees, unpushed commits | | /go | Execute the recommendation from your most recent A/B/C option set |

Code Quality

| Skill | What it does | |-------|-------------| | /review-pr N | AI code review on a PR diff — Critical / Warning / Suggestion | | /merge-pr N | Merge an exact reviewed PR with topology- and history-aware semantics, then clean up | | /investigate | Root cause analysis — no fix without confirmed hypothesis | | /incident DESC | Incident response — diagnose, postmortem, follow-up tasks | | /cso | Security audit (OWASP + STRIDE) | | /artifact | One report page a PhD, a PM and an engineer can read at a glance — section spine per page type (why the numbers, what was done, next step), publication-quality figures, both themes, linted by artifact-lint.py before it is published | | /landscape | Whole-system report — every part, surface, owner, gap, and abandoned attempt, as a published artifact (the /artifact architecture spine at whole-system scale) | | /map | Generate ARCHITECTURE.md with a Mermaid module graph (tree only, no git history) |

Research & Planning

| Skill | What it does | |-------|-------------| | /research TOPIC | Deep web research, synthesize to docs/research/ | | /model-research | Latest Claude model data + auto-update configs | | /next | "What's next?" — fast 1-shot recommendation (default); /next deep for multi-round interview | | /brief | Morning briefing — overnight commits, costs, next steps | | /retro | Engineering retrospective from git history | | /frontend-design | Create production-grade frontend interfaces |

System

| Skill | What it does | |-------|-------------| | /audit | Clean up correction rules — promote, deduplicate, remove stale | | /document-release | Post-ship doc sync (README, CHANGELOG, CLAUDE.md) | | /pipeline | Health check for background pipelines | | /provider | Switch LLM provider | | slt | Toggle statusline quota pace indicator |

Content families

Blog & Content (30) · SEO (25) · Paid Ads (23) · Email (6) — per-skill tables live in When to Use What, which also carries the per-skill usage guidance for the core workflow commands above.

Supported La

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryAutomation
Updated2d ago
Forks6

Languages

Python

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low1 info