Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bilal140202/ccb-github
Maintain this CCB project's GitHub-facing release and npm publication surface.
Passed 17 of 20 test cases with the skill, and 8 of 20 without it.
and 10 more in the full report
11 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which executable CLI binary names must be defined in package.json under the 'bin' field for @seemseam/ccb?
| Checked | Without skill | With skill |
|---|---|---|
| Lists ccb as a CLI binary entry. | Passed | Passed |
| Lists ask as a CLI binary entry. | Missed | Passed |
The instructions your model reads when the skill loads.
Treat GitHub as the user-facing product page. A release is not done until local version files, npm package metadata, both READMEs, changelog, GitHub Release, release assets, npm registry state, and Actions status all agree.
GitHub's repository homepage renders README from the default branch, not from the latest release tag. If release documentation is prepared on a feature or hotfix branch, merge that branch to the default branch before calling the homepage updated.
Use repository SeemSeam/claude_codex_bridge unless the user explicitly gives a different repo.
For CCB releases, npm publishing is part of the release surface by default. If package.json, npm wrapper scripts, README npm install snippets, or .github/workflows/npm-publish.yml are missing or stale during release preparation, create or repair them before the release commit and before creating or pushing the release tag. Do not create a tag first and add npm publish support in a later branch commit.
When the user asks for a final release or homepage result, do the git/GitHub work instead of only describing it:
Keep the checker read-only. Git writes, GitHub Release writes, workflow reruns, and tag operations are explicit agent actions done in the sequence above, not hidden inside the checker.
From the CCB repo root, run the bundled checker before and after release work:
CHECKER="dev_tools/skills/ccb-github/scripts/check_release_state.py"
python "$CHECKER" --phase prepare --repo SeemSeam/claude_codex_bridge
python "$CHECKER" --phase published --repo SeemSeam/claude_codex_bridge --wait-seconds 1800
test cases passed, vs 8 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.