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%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 content is lean, highly actionable, and well-structured with appropriate external references, but two issues hold it back: the release workflow lacks explicit validation/feedback checkpoints for an outward-facing batch operation, and it links to a nonexistent troubleshooting.md reference. Fixing the dead link and adding a verify-release step would lift both capped dimensions.

Suggestions

Add an explicit validation/verification checkpoint to the release workflow (e.g., 'Verify the GitHub Release and appcast were published; if notarization or signing failed, re-run with debug: true') to lift the workflow_clarity cap.

Create references/troubleshooting.md or remove/repoint the two broken links to it in the Debugging Failures section, since the referenced file does not exist in the bundle.

Consider adding a brief 'if release fails' feedback loop (detect failure → enable debug → inspect cert/identity output → re-run) to turn the debug section into an actionable recovery workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean — a glance table, a copy-paste bash snippet, a secrets table, an ASCII pipeline diagram, and short debug/beta sections — with no padding explaining concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides copy-paste-ready bash commands for tag-based releases, explicit manual-dispatch steps, an enumerated list of supported version formats, and specific secret names with links, fully covering the common cases.	5 / 5
Workflow Clarity	The release pipeline is laid out as a clear 12-step sequence, but this is an outward-facing batch operation (publishing a GitHub Release and deploying an appcast to GitHub Pages) with no explicit validation checkpoints or failure feedback loops, so per the rubric cap workflow clarity is held at 3.	3 / 5
Progressive Disclosure	Structure is well-organized with one-level-deep references to real files (secrets-setup.md, release-workflow.md), but the body twice references references/troubleshooting.md, which does not exist in the bundle — a broken navigation link that undermines otherwise good disclosure.	3 / 5
	Total	16 / 20 Passed

Description

100%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 exemplary: it concisely states what the skill manages, enumerates six concrete capability areas, and includes verbatim natural-language trigger phrases users would actually say. It is well-scoped to ClaudeBar's specific CI/CD context with minimal overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain ('Manage ClaudeBar's GitHub Actions CI/CD pipelines') and lists multiple concrete capability areas across six numbered items (secrets setup, release creation, triggering workflows, debugging failures, beta/stable channels), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' ('Manage ... CI/CD pipelines: build, test, and release workflows') and 'when' ('Use this skill when:' with six concrete trigger conditions), matching the anchor for clearly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Item (6) directly quotes natural user phrases ('release a new version', 'push a tag', 'set up CI secrets', 'why did the release fail') alongside technical workflow filenames, giving comprehensive coverage of terms users would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped to 'ClaudeBar's GitHub Actions CI/CD pipelines' with named workflow files (build.yml, tests.yml, release.yml) and specific tooling (Sparkle, Codecov), establishing a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 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: e9862db

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.