Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kbwo/ccmanager-config
Set up, review, or repair a CCManager config — `.ccmanager.json` at a git repository root, or the global `~/.config/ccmanager/config.json`.
Passed 12 of 17 test cases with the skill, and 6 of 17 without it.
and 10 more in the full report
10 fixed6 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to add a new shortcut key binding to my global CCManager configuration file `~/.config/ccmanager/config.json`. What is the first step before writing any changes?
| Checked | Without skill | With skill |
|---|---|---|
| States that existing file contents must be read before making modifications. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Ask yourself, and the user if it is genuinely ambiguous:
.ccmanager.json,
committed.config.json.Two traps before you write anything:
.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.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.test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.