ccb-clear

Clear conversation context for one or more mounted CCB agents using ccb clear. Use when the user invokes /ccb-clear, $ccb-clear, or $ccb_clear, or asks Grok to clear or reset CCB agent context without restarting agents or deleting project state.

Quality

84%

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

86%Weight 40%Scale 1-5

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

Concise, actionable, and well-structured with concrete commands and clear error handling. The main improvement would be trimming the environment-specific source-validation paths and adding an explicit success check.

Suggestions

Move the hard-coded /home/bfly/yunwei/... source-validation paths into a separate reference or omit them unless they are essential to this skill's core action.

Add an explicit verification step (e.g., confirm ccb clear output indicates success before reporting completion) to strengthen the workflow's feedback loop.

Consolidate the three near-identical bash examples into one parameterized example to reduce repetition.

Dimension	Reasoning	Score
Conciseness	Mostly lean and executable, but the hard-coded source-validation paths paragraph is environment-specific padding that does not earn its place for the core action.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering bare and named-agent cases, matching the anchor for complete executable guidance.	5 / 5
Workflow Clarity	A clear single-action workflow with explicit checkpoints (ask on ambiguous scope; report and stop on permission denial; do not poll), though no explicit success-verification feedback loop.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references, organized into intro, source-validation note, command examples, and a rules list, satisfying the simple-skills exception.	5 / 5
	Total	18 / 20 Passed

Description

82%Weight 40%Scale 1-5

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 strong, specific description that clearly states both the action and explicit triggers. The main weakness is specificity, which lists a single action rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	Names the domain (CCB agents) and one concrete action ('Clear conversation context ... using ccb clear'), but only a single action rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what (clear CCB agent conversation context via ccb clear) and when (invocation strings / natural-language clear-or-reset requests) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrasings users would say ('clear or reset CCB agent context') plus explicit invocation strings, with only minor synonym gaps.	4 / 5
Distinctiveness Conflict Risk	A clear niche (mounted CCB agents, ccb clear, exact invocation strings) with minimal risk of triggering for unrelated skills.	5 / 5
	Total	17 / 20 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: inherit_skills/grok_skills/ccb-clear/SKILL.md
Commit: 01d5b1c

Reviewed: about 21 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.