ci-cd-github-actions
Build comprehensive GitHub Actions workflows for CI/CD, testing, security, and deployment. Master workflows, jobs, steps, and conditional execution.
47
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ci-cd-github-actions/SKILL.mdQuality
Discovery
32%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 identifies the domain (GitHub Actions) and lists relevant topic areas but lacks concrete action verbs and a critical 'Use when...' clause. The second sentence ('Master workflows, jobs, steps, and conditional execution') reads more like a learning objective than a capability description, reducing its effectiveness for skill selection. Adding explicit trigger guidance and more specific actions would significantly improve it.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about GitHub Actions, CI/CD pipelines, .github/workflows files, or automating builds and deployments with GitHub.'
Replace 'Master workflows, jobs, steps, and conditional execution' with concrete actions like 'Configures workflow triggers, defines job matrices, sets up caching, manages secrets, and implements conditional step execution.'
Include common user-facing trigger terms and file extensions like '.yml workflow files', 'GitHub CI', 'pull request checks', 'automated pipeline', and 'deploy action'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub Actions) and lists some areas (CI/CD, testing, security, deployment, workflows, jobs, steps, conditional execution), but these are more like categories than concrete actions. 'Build comprehensive workflows' is somewhat specific, but 'Master workflows, jobs, steps' is vague. | 2 / 3 |
Completeness | Describes what it does (build GitHub Actions workflows) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'when' is not even implied clearly, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'GitHub Actions', 'CI/CD', 'workflows', 'deployment', 'testing', and 'security' which users might naturally say. However, it misses common variations like '.github/workflows', 'pipeline', 'YAML workflow', 'automated tests', 'pull request checks', or 'GitHub CI'. | 2 / 3 |
Distinctiveness Conflict Risk | GitHub Actions is a fairly specific domain, which helps distinctiveness. However, the mention of broad terms like 'CI/CD', 'testing', 'security', and 'deployment' could overlap with other skills focused on those general topics outside of GitHub Actions. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong, actionable YAML examples that are copy-paste ready, which is its primary strength. However, it suffers from moderate verbosity with sections that state obvious knowledge (When to Use, generic best practices), inconsistent numbering (1, 3, 5), and lacks validation/verification steps in its workflows. The monolithic structure with no bundle files means all content is inline, making it harder to navigate.
Suggestions
Remove the 'When to Use' section and trim the DO/DON'T lists to only non-obvious, GitHub Actions-specific guidance that Claude wouldn't already know.
Add explicit validation and verification steps to the deploy job (e.g., health check after deployment, rollback on failure) to demonstrate proper feedback loops.
Fix the inconsistent numbering (sections jump from 1 to 3 to 5) and consider splitting the large workflow examples into separate referenced files for better progressive disclosure.
Remove or condense the permissions block and secrets CLI section, which are reference material better served by a link to GitHub docs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary padding (e.g., the 'When to Use' bullet list is obvious context Claude already knows, the DO/DON'T lists contain generic advice). The examples are fairly large and could be trimmed, but they do provide concrete value. The numbered examples skip from 1 to 3 to 5, suggesting sloppy editing. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready YAML workflow files covering CI/CD, releases, and Docker builds. The CLI commands for secrets management are concrete and specific. All examples are complete and runnable. | 3 / 3 |
Workflow Clarity | The CI/CD workflow demonstrates job dependencies (needs: test) and conditional execution (if: github.ref == 'refs/heads/main'), which shows sequencing. However, there are no explicit validation checkpoints, no feedback loops for error recovery, and the deploy step is a placeholder with no verification that deployment succeeded. | 2 / 3 |
Progressive Disclosure | The content is a long monolithic file with no references to supporting files. While it has section headers providing some structure, the large inline YAML examples (200+ lines total) could benefit from being split into separate referenced files. External links to GitHub docs are provided but no bundle-level organization exists. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ucdavis/ai-skills-registry
- Commit
c0b2e4b
- Reviewed
Table of Contents
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.