npx claudepluginhub deanh/rad-skillClaude Code plugin for Radicle - a peer-to-peer code collaboration protocol with task integration, Plan COB, and Context COB support
A Claude Code plugin for working with Radicle — a peer-to-peer code collaboration protocol.
Looking for pi? See rad-pi for the pi package.
rad CLI commands (init, clone, patch, issue, sync, etc.)me.hdh.plan)me.hdh.context) for future sessions and collaboratorsrad auth)rad node start)rad-plan CLI for Plan COB supportrad-context CLI for Context COB supportAll COB features gracefully degrade when their CLIs are not installed.
Add to your settings file (~/.claude/settings.json for global, .claude/settings.json for project):
{
"extraKnownMarketplaces": {
"rad-skill": {
"source": {
"source": "git",
"url": "https://seed.radicle.garden/zvBj4kByGeQSrSy2c4H7fyK42cS8.git"
}
}
},
"enabledPlugins": {
"radicle@rad-skill": true
}
}
Three knowledge skills following the Agent Skills standard:
| Skill | Description |
|---|---|
| radicle | Core rad CLI operations — init, clone, patch, issue, sync, node management |
| rad-plans | Plan COBs (me.hdh.plan), rad-plan CLI, and interactive plan management |
| rad-contexts | Context COBs (me.hdh.context) and rad-context CLI |
/rad-import <issue-id>Import a Radicle issue and break it down into tasks. Enters plan mode by default to explore the codebase before creating tasks. After task creation, interactively offers to save as a Plan COB.
/rad-import abc123
/rad-sync [--dry-run]Sync completed tasks back to Radicle issues and Plan COBs. Uses rollup logic — an issue is marked "solved" only when ALL linked tasks are completed. Offers context creation when closing issues.
/rad-status [issue-id]Query the repository's actual state and display a unified overview of open issues, active plans, and session tasks with actionable suggestions.
/rad-issue <description> [flags]Create Radicle issues from descriptions, tasks, or plan files. Dispatches specialist research roles for non-trivial issues.
/rad-context <action> [id]Manage Context COBs: list, show, create, link.
Multiple agents work in parallel git worktrees, using COBs as the shared coordination layer. COBs live in ~/.radicle/storage/ and are visible from all worktrees instantly — code is isolated per worktree, metadata flows freely.
The plan-manager agent handles dispatch interactively:
/rad-import <issue-id> creates tasks, optionally saves as a Plan COBclaude --worktree sessions per task — each worker claims a task, implements, produces a commit + Context COB/rad-sync closes the plan and issue| Agent | Role | Runs In |
|---|---|---|
| plan-manager | Creates plans, dispatches tasks, evaluates context feedback | Main worktree |
| worker | Executes one task: code, commit, Context COB | Isolated worktree |
Issues are feature-level ("Implement auth"), tasks are work items ("Create middleware", "Write tests"). One issue becomes multiple tasks, each sized for a single session or context window.
Sync uses conservative completion — an issue closes only when 100% of linked tasks are done:
| Tasks Completed | Sync Behavior |
|---|---|
| 4/4 (100%) | Issue closed, completion comment added |
| 3/4 (75%) | Issue stays open, progress noted |
| 0/4 (0%) | No action taken |
Context COBs (me.hdh.context) capture what an agent learned during a coding session — approach, constraints, friction, learnings, and open items. They're durable records stored in Radicle that replicate across the network, designed for future agents and collaborators rather than the current session.