ccb-config

Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, operational skill body with executable commands, a gated validation/dry-run workflow, and a well-signaled one-level reference. The only notable weakness is redundancy between the body and the reference file, which inflates token cost.

Suggestions

Defer shared rules that already live in references/config-contracts.md (validation/reload gates, [windows] overlay non-repeat rules, provider fallback handling) to the reference and link to them instead of restating, to reduce duplication.

Consider moving the Role Binding TOML examples or Affected-Agent Rules detail into the reference if they grow, keeping the body as the procedural overview.

Dimension	Reasoning	Score
Conciseness	The body is operational and avoids explaining concepts Claude already knows, but validation gates, the [windows] overlay non-repeat rules, and provider fallback handling are duplicated between the body and references/config-contracts.md and could be tightened by deferring to the reference.	2 / 3
Actionability	It provides copy-paste-ready commands ("ccb config validate", "ccb reload --dry-run", "cp .ccb/ccb.config .ccb/ccb.config.bak.$(date +%s)", "ccb roles install agentroles.ccb_self") plus concrete TOML binding examples and a handoff template, matching the fully executable level-3 anchor.	3 / 3
Workflow Clarity	The 12-step Required Workflow sequences resolve → classify → edit → validate → dry-run → reload with explicit gates and an error-recovery feedback loop (restore from backup or stop and ask on validation failure), so it is not the checkpoint-missing level 2.	3 / 3
Progressive Disclosure	"Read references/config-contracts.md before complex edits" signals a real, one-level-deep reference (verified to exist), and the body is organized into clear overview sections (Scope, Required Workflow, Affected-Agent Rules, Role Binding, Reporting).	3 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-scoped description with strong action enumeration and clear distinctiveness. Its main weakness is trigger-term naturalness: it leans on internal CCB jargon rather than the phrasings a user would naturally say.

Suggestions

Add a user-facing trigger clause such as "Use when the user wants to change CCB config topology, providers, role bindings, or reload behavior" to complement the internal scope guardrail.

Soften jargon-heavy phrases (e.g., "provider startup inputs") with more natural synonyms users would actually say when requesting these changes.

Dimension	Reasoning	Score
Specificity	"Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs" lists multiple specific concrete actions across named config surfaces, matching the level-3 anchor rather than the partial level-2 list.	3 / 3
Completeness	The "what" is explicit and comprehensive, and "Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self" provides equivalent explicit trigger/usage guidance, satisfying both halves; it is not level 2 because the when is stated, not merely implied.	3 / 3
Trigger Term Quality	Terms like "ccb.config", "reload", "providers", and "windows" are relevant to the niche, but the phrasing is internal jargon ("provider startup inputs", "role bindings") and lacks common natural user-need variations, so it sits at level 2 rather than the broad natural coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	"Private built-in CCB configuration skill for agentroles.ccb_self" with an explicit non-self delegation guardrail carves a clear, narrow niche that is unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SeemSeam/claude_codex_bridge
Path: docs/plantree/plans/ccb-self-role/drafts/agentroles.ccb_self/skills/codex/ccb-config/SKILL.md
Commit: ec3de76

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.