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.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ci-cd-and-automation/SKILL.md

The canonical home for this skill is ci-cd-and-automation in addyosmani/agent-skills

Quality

Content

77%Scale 1-3

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

This is a comprehensive, highly actionable CI/CD skill with excellent executable examples and clear workflow sequencing. Its main weakness is length — it tries to cover too many topics (CI, deployment, feature flags, environment management, optimization) in a single file without progressive disclosure, and includes some philosophical content that Claude doesn't need. Trimming the motivational content and splitting advanced topics into referenced files would significantly improve it.

Suggestions

Split deployment strategies, feature flags, and CI optimization into separate referenced files (e.g., DEPLOYMENT.md, OPTIMIZATION.md) to reduce the main file's length and improve progressive disclosure.

Remove or significantly condense the 'Common Rationalizations' table and the 'Shift Left'/'Faster is Safer' philosophical paragraphs — Claude doesn't need persuasion on why CI matters.

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary philosophical framing ('Shift Left', 'Faster is Safer' paragraphs) and a 'Common Rationalizations' table that explains things Claude already understands. The 'When to Use' section is also somewhat redundant given the description. However, the code examples themselves are lean and the overall structure is reasonable for the breadth of topics covered.	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). 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, and the pipeline diagram enforces 'no gate can be skipped' as a clear constraint.	3 / 3
Progressive Disclosure	The content is a monolithic ~300-line file covering CI setup, deployment strategies, feature flags, environment management, optimization, and more. Much of this (deployment strategies, feature flags, CI optimization) could be split into separate referenced files. There are no external file references despite the breadth warranting them.	2 / 3
	Total	10 / 12 Passed

Description

67%Scale 1-3

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 reasonably well-structured with explicit 'Use when' clauses that clearly communicate both purpose and trigger conditions. However, it stays at a moderately high level of abstraction without naming specific tools, file formats, or platforms, which limits both specificity and trigger term coverage. Adding concrete tool names and file types would strengthen distinctiveness and natural keyword matching.

Suggestions

Add specific tool and platform names as trigger terms (e.g., 'GitHub Actions', 'GitLab CI', 'Jenkins', 'CircleCI', '.yml workflow files').

List more concrete actions beyond 'automate quality gates' — e.g., 'generate workflow YAML files, configure build steps, set up automated testing stages, define deployment targets'.

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, or specific file types).	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', but misses common variations users might say such as 'GitHub Actions', 'Jenkins', 'workflow', 'continuous integration', 'continuous deployment', '.yml', 'pipeline configuration'.	2 / 3
Distinctiveness Conflict Risk	The CI/CD focus provides some distinctiveness, but terms like 'deployment strategies' and 'build' could overlap with infrastructure-as-code or general DevOps skills. More specific tool or file references would reduce conflict risk.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: finlay611/agent-skills
Path: skills/ci-cd-and-automation/SKILL.md
Commit: fea75b1

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.