ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
62
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ci-cd-and-automation/SKILL.mdQuality
Discovery
67%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 structurally sound with explicit 'Use when' clauses that clearly communicate both purpose and trigger conditions. However, it stays at a moderately high level of abstraction—naming the domain well but lacking specific concrete actions (e.g., generating workflow YAML, configuring specific CI platforms) and missing common user-facing trigger terms like 'GitHub Actions', 'Jenkins', or 'workflow file'.
Suggestions
Add specific concrete actions such as 'generate GitHub Actions workflows', 'configure Jenkins pipelines', or 'create .yml workflow files' to improve specificity.
Include more natural trigger terms users would say, such as 'GitHub Actions', 'Jenkins', 'continuous integration', 'continuous deployment', 'workflow', or '.yml files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD pipelines) and mentions some actions like 'automate quality gates', 'configure test runners', and 'establish deployment strategies', but these are somewhat high-level rather than listing multiple concrete, specific actions (e.g., no mention of specific tools like GitHub Actions, Jenkins, YAML config generation, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (automates CI/CD pipeline setup) and 'when' with explicit 'Use when' clauses covering setup, modification, quality gates, test runners, and deployment strategies. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'CI/CD', 'pipeline', 'build', 'deployment', 'quality gates', 'test runners', and 'CI', but misses common user variations like 'GitHub Actions', 'Jenkins', 'continuous integration', 'continuous deployment', 'workflow', '.yml', or 'pipeline configuration'. | 2 / 3 |
Distinctiveness Conflict Risk | The CI/CD focus provides reasonable distinctiveness, but terms like 'deployment strategies' and 'build' could overlap with infrastructure-as-code, Docker, or general DevOps skills. More specific tooling or file type references would reduce conflict risk. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and complete, executable GitHub Actions examples covering multiple CI/CD scenarios. Its main weaknesses are moderate verbosity (philosophical explanations, rationalizations table, and red flags that Claude doesn't need) and a monolithic structure that could benefit from splitting detailed topics into referenced files. Overall it serves as a solid, practical guide for CI/CD pipeline setup.
Suggestions
Remove or significantly trim the 'Common Rationalizations' table and 'Red Flags' section — these are cultural guidance Claude doesn't need to follow instructions.
Trim the 'Shift Left' and 'Faster is Safer' philosophy paragraphs to single-line principles or remove them entirely.
Consider extracting detailed sections (deployment strategies, E2E setup, CI optimization) into separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary explanatory content Claude already knows (e.g., 'Shift Left' philosophy explanation, 'Faster is Safer' rationale, the 'Common Rationalizations' table, and the 'Red Flags' section). The feature flags explanation is also somewhat verbose for an audience that understands the concept. However, the YAML examples and pipeline diagrams are efficient and earn their tokens. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready GitHub Actions YAML configurations for multiple scenarios (basic CI, database integration, E2E, rollback, dependabot, parallel jobs). Code examples are complete and specific with real tool names, versions, and commands. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with ASCII diagrams showing the quality gate pipeline, CI failure feedback loop, and staged rollout process. The verification checklist at the end serves as an explicit validation checkpoint. The pipeline ordering is explicit (lint → type check → tests → build → integration → e2e → audit) with clear 'no gate can be skipped' enforcement. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, but it's a monolithic document (~300 lines) with no references to external files for detailed topics like deployment strategies, E2E testing setup, or optimization techniques. Topics like feature flags and environment management could be split into separate reference files. The mention of 'debugging-and-error-recovery skill' is a good cross-reference but is the only one. | 2 / 3 |
Total | 10 / 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
- addyosmani/agent-skills
- Commit
f17c6e8
- 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.