github-actions

Manage ClaudeBar's GitHub Actions CI/CD pipelines: build, test, and release workflows. Use this skill when: (1) Setting up secrets for CI/CD (certificate, API key, Sparkle key, Codecov) (2) Creating a new release — tag-based or manual workflow_dispatch (3) Triggering or explaining the build.yml, tests.yml, or release.yml workflows (4) Debugging release failures (signing, notarization, appcast) (5) Managing beta vs stable channels for Sparkle auto-updates (6) User says "release a new version", "push a tag", "set up CI secrets", "why did the release fail"

Quality

90%

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

80%

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

The body is concise, highly actionable, and well-organized with a clear pipeline overview and reference links. It loses points because the release workflow omits explicit validation/verification checkpoints and references a missing troubleshooting.md file.

Suggestions

Add an explicit verification checkpoint to the Create a Release steps (e.g., confirm the Actions run is green and the GitHub Release was published before proceeding), since publishing a release is hard to reverse.

Either create references/troubleshooting.md or remove/redirect the broken [troubleshooting.md](references/troubleshooting.md) link in the Debugging Failures section.

Note in the beta/stable section how to verify the appcast was deployed to GitHub Pages so users can confirm the auto-update channel updated correctly.

Dimension	Reasoning	Score
Conciseness	The body is lean — tables, a compact release-pipeline diagram, and terse step lists — with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides copy-paste-ready git commands, explicit version formats, a secrets table with links, and concrete manual-dispatch steps rather than abstract direction.	3 / 3
Workflow Clarity	The release flow is sequenced (Option A/B, numbered pipeline steps) but lacks explicit validation or verification checkpoints for a hard-to-reverse publish operation, which the guidelines cap at 2.	2 / 3
Progressive Disclosure	Structure is otherwise well-signaled with one-level-deep references, but the body links to troubleshooting.md which does not exist in references/, breaking navigation.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, well-scoped description that clearly conveys both capability and trigger conditions using natural user language and third-person voice. It lists concrete actions rather than vague claims and is unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions including specific workflow filenames (build.yml, tests.yml, release.yml) and operations like signing, notarization, and appcast generation.	3 / 3
Completeness	Explicitly states what the skill does ('Manage ClaudeBar's GitHub Actions CI/CD pipelines') and when to use it via a numbered 'Use this skill when' clause with six triggers.	3 / 3
Trigger Term Quality	Item (6) captures natural user phrasings such as 'release a new version', 'push a tag', 'set up CI secrets', and 'why did the release fail' that a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to ClaudeBar's GitHub Actions with distinct release/CI-CD triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: tddworks/ClaudeBar
Path: .claude/skills/github-actions/SKILL.md
Commit: 92b9351

Reviewed: 3 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.