ccb-github

Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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.

The body is highly actionable with concrete commands and well-sequenced, validation-gated workflows appropriate for risky release work. Its main weakness is conciseness: several requirements are repeated across sections and could be consolidated.

Suggestions

Consolidate the npm/prepare/published requirements that are restated across Core Rule, Decision Tree, Release Preparation Checklist, and Publish Sequence into a single canonical section referenced elsewhere, to reduce repetition.

Move the detailed per-file README requirements and npm Trusted Publisher configuration specifics into a separate reference file in references/ and link to it, improving both conciseness and progressive disclosure.

Trim the Recovery Runbook to the truly common cases and point to the checker's per-FAIL suggested fixes for the long tail, since the checker already emits fix hints.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but at ~280 lines it restates npm/prepare/published requirements across multiple sections (Core Rule, Decision Tree, Release Preparation Checklist, Publish Sequence, Recovery Runbook), so it could be tightened rather than being lean throughout.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (checker invocations with exact flags, git/gh/npm commands, `git show HEAD:` verification), with specific file lists and a real referenced script path, matching fully executable guidance.	5 / 5
Workflow Clarity	Numbered sequences (Execution Contract, Publish Sequence, Homepage Maintenance) include explicit validation checkpoints (run --phase prepare and fix every FAIL before tagging, verify package.json/npm-publish.yml before tag, wait for Actions, run published checker) plus a Recovery Runbook and Stop Conditions, giving clear feedback loops for this batch/release work.	5 / 5
Progressive Disclosure	Structure is good with clear section headers and a real one-level-deep reference to the bundled checker script in scripts/, but the bulk of requirements/checklists are inlined rather than split into separate reference files, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

The description is strong: it clearly states what the skill does and when to use it, with a comprehensive list of concrete artifacts and natural trigger phrasing. The only minor gap is a few missing synonym/variations in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("preparing, publishing, auditing, or fixing") and a comprehensive set of concrete artifacts (README.md, README/zh.md, CHANGELOG.md, VERSION, package.json, release notes/assets, repository description/topics, npm registry state, Actions status), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both "what" (Maintain the GitHub-facing release and npm publication surface) and "when" (Use when preparing, publishing, auditing, or fixing CCB releases; updating the listed files), with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Natural trigger phrasing ("Use when preparing, publishing, auditing, or fixing CCB releases; updating...") covers most user-sayable terms, but is missing a few common synonyms/variations, fitting good-but-not-comprehensive coverage rather than the score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific niche ("this CCB project's GitHub-facing release and npm publication surface") with distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: SeemSeam/claude_codex_bridge
Path: dev_tools/skills/ccb-github/SKILL.md
Commit: e9b1970

Reviewed: 4 days 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.