Agent skill

Ccmanager Config

Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

MITAuto-check passedDevelopment

Install Ccmanager Config

skills CLI

$ npx skills add kbwo/ccmanager --skill ccmanager-config -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install kbwo/ccmanager ccmanager-config --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/kbwo/ccmanager.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ccmanager-config/skills/ccmanager-config .claude/skills/ccmanager-config && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ccmanager-config" agent skill from https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config into .claude/skills/ccmanager-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccmanager-config", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add kbwo/ccmanager --skill ccmanager-config -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install kbwo/ccmanager ccmanager-config --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kbwo/ccmanager.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ccmanager-config/skills/ccmanager-config .agents/skills/ccmanager-config && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ccmanager-config" agent skill from https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config into .agents/skills/ccmanager-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccmanager-config", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add kbwo/ccmanager --skill ccmanager-config -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install kbwo/ccmanager ccmanager-config --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kbwo/ccmanager.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ccmanager-config/skills/ccmanager-config .cursor/skills/ccmanager-config && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ccmanager-config" agent skill from https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config into .cursor/skills/ccmanager-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccmanager-config", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/kbwo/ccmanager.git --path plugins/ccmanager-config/skills/ccmanager-config

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add kbwo/ccmanager --skill ccmanager-config -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install kbwo/ccmanager ccmanager-config --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kbwo/ccmanager.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ccmanager-config/skills/ccmanager-config .gemini/skills/ccmanager-config && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ccmanager-config" agent skill from https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config into .gemini/skills/ccmanager-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccmanager-config", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install kbwo/ccmanager ccmanager-config

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add kbwo/ccmanager --skill ccmanager-config -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/kbwo/ccmanager.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ccmanager-config/skills/ccmanager-config .github/skills/ccmanager-config && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ccmanager-config" agent skill from https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config into .github/skills/ccmanager-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccmanager-config", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add kbwo/ccmanager --skill ccmanager-config -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install kbwo/ccmanager ccmanager-config --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kbwo/ccmanager.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ccmanager-config/skills/ccmanager-config .opencode/skills/ccmanager-config && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ccmanager-config" agent skill from https://github.com/kbwo/ccmanager/tree/main/plugins/ccmanager-config/skills/ccmanager-config into .opencode/skills/ccmanager-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccmanager-config", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ccmanager-config
GitHub stars: 1.3k
Token cost: ~1.5k tokens
SKILL.md length: 812 words
Files: 5 (incl. scripts, references)
Skills in repo: 1
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

Works in 5 steps: Decide which file to edit → Read what is already there → Write the config → …
Someone wants ccmanager to launch a different agent CLI (codex
SKILL.md covers Procedure, Reviewing an existing config… and Files in this skill
Runs JavaScript scripts from its folder; calls node

What it does

Ccmanager Config is an agent skill from kbwo/ccmanager. Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree creation, auto-generate worktree directory paths, change merge/rebase arguments, rebind the return-to-menu key, turn on auto-approval — or when a ccmanager setting "does not seem to do anything".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/config-reference.md`, `references/recipes.md` and `schema/ccmanager.schema.json`).

It sits in Development, covering Git worktrees, Session handoff and Git workflow. It works with Git, Kimi and Google Gemini. The repository describes itself as: Coding Agent Session Manager for Claude Code / Gemini CLI / Codex CLI / Cursor Agent / Copilot CLI / Cline CLI / OpenCode / Kimi CLI. The licence is MIT.

When your agent uses it

Someone wants ccmanager to launch a different agent CLI (codex
Add command presets
Run a command on session state changes
Worktree creation

Example prompts

“does not seem to do anything”
“/ccmanager-config”

Requirements

Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Decide which file to edit
Read what is already there
Write the config
Validate — always
Tell the user how to pick it up

What it can do on your machine

Read from SKILL.md and the folder at commit ee0af83. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ccmanager Config loads about 1.5k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 133 tokens; SKILL.md has 812 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~133
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from kbwo/ccmanager at commit ee0af83, republished under its MIT licence (© kbwo). 812 words, ~1,543 tokens.

Download SKILL.mdSave it as .claude/skills/ccmanager-config/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: ccmanager-config
description: Set up, review, or repair a CCManager config — `.ccmanager.json` at a git repository root, or the global `~/.config/ccmanager/config.json`. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree creation, auto-generate worktree directory paths, change merge/rebase arguments, rebind the return-to-menu key, turn on auto-approval — or when a ccmanager setting "does not seem to do anything".

Configuring CCManager

CCManager (ccmanager) is a terminal UI that runs one AI coding agent per git worktree. Its behaviour comes from two JSON files with identical shape:

File	Scope	Notes
`<git repository root>/.ccmanager.json`	one repository	commit it to share with the team
`~/.config/ccmanager/config.json` (`%APPDATA%\ccmanager\config.json` on Windows)	the user, all repositories	also written by ccmanager's own Global Configuration menu

Per key, the project file wins over the global file. Both are optional.

The reason this skill exists: CCManager reports nothing when a config is wrong. A file that is not valid JSON is discarded whole, and unknown keys are ignored without a message, so a typo is indistinguishable from a feature that does not work. Every change made through this skill therefore ends with the validator run in step 4.

Procedure

1. Decide which file to edit

Ask yourself, and the user if it is genuinely ambiguous:

Does the setting describe the repository (which agent CLI to run, what to do after a worktree is created, where worktrees live)? → .ccmanager.json, committed.
Does it describe this person's machine or taste (notification commands, key bindings, personal API/model flags)? → the global config.json.

Two traps before you write anything:

Put .ccmanager.json at the main repository root, not inside a linked worktree. CCManager resolves any worktree back to the main checkout, so a config file inside a worktree is never read.
If ccmanager is started in multi-project mode (the CCMANAGER_MULTI_PROJECT_ROOT environment variable is set, or --multi-project is passed), project files are skipped entirely and only the global config applies. Say so rather than writing a file that will be ignored.

2. Read what is already there

cat the target file if it exists, plus the other file in the pair when the user's request depends on the merged result. Never rewrite a config from scratch when one exists — you would silently drop settings you were not asked about.

3. Write the config

Look every key up in references/config-reference.md (in this skill directory) before writing it: it lists each key with its type, its default, and what it actually does. Do not invent keys — anything not listed there is dropped by CCManager without a word.

For the common goals — running codex/gemini/another CLI, several presets, desktop notifications, per-worktree setup commands, worktree path patterns, merge arguments, auto-approval — start from a worked example in references/recipes.md and adapt it.

Three rules that cause most of the breakage:

Merging happens one key deep. For each top-level key present in the project file, that key's fields override the global ones; anything nested below a field is replaced wholesale, not merged. In particular a project commandPresets.presets array replaces the global preset list entirely — so list every preset the repository needs, and give defaultPresetId the id of one of those presets.
args is argv, one array element per token. ["--model", "opus"], never ["--model opus"].
A hook without "enabled": true never runs. Both command and enabled are required.

Show full SKILL.md (327 more words)Show less

4. Validate — always

bash

node <skill-dir>/scripts/validate-ccmanager-config.mjs path/to/.ccmanager.json

It parses the file the way CCManager does, checks the shape against schema/ccmanager.schema.json, flags unknown keys (with a "did you mean"), and catches the mistakes JSON alone cannot express: a defaultPresetId matching no preset, duplicate preset ids, an args entry with spaces in it, a detection strategy that does not match the command, a shortcut that can never fire, a disabled hook, a worktree pattern without {branch}, a config file sitting in a linked worktree. It exits non-zero on errors; warnings are advisory.

Report what it printed. If you cannot run it (no Node available), say so explicitly instead of claiming the config is fine.

5. Tell the user how to pick it up

CCManager reads config at start-up and when it reloads. After editing a file by hand, they should return to the ccmanager menu or restart it; sessions already running keep the command and detection strategy they were started with.

Reviewing an existing config ("this setting does nothing")

Work down this list — these are the silent failures, in the order they bite:

Run the validator (step 4). Invalid JSON and unknown/misspelled keys are the two most common causes and both are invisible in the TUI.
Check the file location: main repository root, not a worktree; and multi-project mode disabled.
Check the other file. The project file only overrides keys it actually contains; everything else still comes from the global config.
For presets: a defaultPresetId pointing at a preset that lives in the other file silently falls back to the first preset in the list.
For a session that reports the wrong status: detectionStrategy must match the CLI being run — see the table in references/config-reference.md.

Files in this skill

references/config-reference.md — every key: type, default, behaviour, and the hook environment variables.
references/recipes.md — copy-and-adapt configurations for the usual goals.
schema/ccmanager.schema.json — JSON Schema for both config files; usable as $schema in an editor for completion.
scripts/validate-ccmanager-config.mjs — the validator from step 4.

Files

SKILL.md and 4 other files (scripts, references) in plugins/ccmanager-config/skills/ccmanager-config of kbwo/ccmanager.

SKILL.md
references/config-reference.md
references/recipes.md
schema/ccmanager.schema.json
scripts/validate-ccmanager-config.mjs

Open the folder on GitHubat commit ee0af83

Compare with similar skills

Ccmanager Config next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ccmanager Config compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ccmanager Config this skillkbwo/ccmanager	1.3k	—	~1.5k	Automated safety check: Pass	MIT	yesterday
Polyphonyalinaqi/maggy	707	—	~980	Automated safety check: Pass	MIT	14 days ago
Finishing a Development Branchobra/superpowers	296k	5 repos	~1.9k	Automated safety check: Pass	MIT	today
Git Worktree Cleanuplobehub/lobehub	83k	—	~2.8k	Automated safety check: Pass	Custom licence	today
Git Worktree Managermicrosoft/WindowsAppSDK	4.7k	—	~2k	Automated safety check: Pass	MIT	yesterday
Roo Conflict Resolutionzgsm-ai/costrict	4.4k	—	~2.3k	Automated safety check: Pass	Apache-2.0	8 days ago

Similar skills

Polyphony
alinaqi/maggy
Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches
707 GitHub stars~980 tokensUpdated 14 days ago
DevelopmentAuto-check passed
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
296k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Git Worktree Cleanup
lobehub/lobehub
Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.
83k GitHub stars~2.8k tokensUpdated today
DevelopmentAuto-check passed
Git Worktree Manager
microsoft/WindowsAppSDK
Official
Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.
4.7k GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Roo Conflict Resolution
zgsm-ai/costrict
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.
4.4k GitHub stars~2.3k tokensUpdated 8 days ago
DevelopmentAuto-check passed
Git Commit
tisfeng/Easydict
起草、创建或汇报 Angular-style 本地 Git 提交。用于明确的提交交付；分支集成使用 worktree-rebase-merge，不 push。
15k GitHub stars~535 tokensUpdated 2 days ago
DevelopmentAuto-check passed

Works with

Questions about Ccmanager Config

What does Ccmanager Config do?

Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json. Ccmanager Config is an agent skill from kbwo/ccmanager.json.

When should I use Ccmanager Config?

Ccmanager Config fits situations like: someone wants ccmanager to launch a different agent CLI (codex; add command presets; run a command on session state changes; worktree creation.

How do I install Ccmanager Config in Claude Code?

Run `npx skills add kbwo/ccmanager --skill ccmanager-config -a claude-code`. Or copy the skill folder (plugins/ccmanager-config/skills/ccmanager-config in kbwo/ccmanager) into .claude/skills/ccmanager-config in your project. Claude Code loads it when a task matches its description.

How do I install Ccmanager Config in Codex?

Run `npx skills add kbwo/ccmanager --skill ccmanager-config -a codex`. Or copy the skill folder (plugins/ccmanager-config/skills/ccmanager-config in kbwo/ccmanager) into .agents/skills/ccmanager-config in your project. Codex loads it when a task matches its description.

Can I use Ccmanager Config in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kbwo/ccmanager --skill ccmanager-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccmanager-config, .gemini/skills/ccmanager-config, .github/skills/ccmanager-config and .opencode/skills/ccmanager-config in your project.

What does Ccmanager Config need to run?

Going by SKILL.md and its folder, Ccmanager Config needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Ccmanager Config access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ccmanager Config safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Ccmanager Config use?

Ccmanager Config is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ccmanager Config use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.

What are the alternatives to Ccmanager Config?

Skills that share tags, products or a category with Ccmanager Config: Polyphony (alinaqi/maggy, 707 stars), Finishing a Development Branch (obra/superpowers, 296k stars), Git Worktree Cleanup (lobehub/lobehub, 83k stars) and Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ccmanager Config?

kbwo (a GitHub user) maintains it in kbwo/ccmanager, which has 1,260 GitHub stars. The repository was last updated on October 7, 2026.

Source: kbwo/ccmanager on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ccmanager Config

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Configuring CCManager

Procedure

1. Decide which file to edit

2. Read what is already there

3. Write the config

4. Validate — always

5. Tell the user how to pick it up

Reviewing an existing config ("this setting does nothing")

Files in this skill

Files

Compare with similar skills

Similar skills

Polyphony

Finishing a Development Branch

Git Worktree Cleanup

Git Worktree Manager

Roo Conflict Resolution

Git Commit

Related

Questions about Ccmanager Config