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

79%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ci-cd-and-automation/SKILL.md

Quality

Content

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 executable examples and clear workflow sequencing. Its main weakness is length — it tries to cover too much ground in a single file (CI setup, deployment strategies, feature flags, environment management, optimization) without progressive disclosure to separate files. Some sections contain explanatory prose that Claude doesn't need, such as the philosophical framing and common rationalizations table.

Suggestions

Split deployment strategies, CI optimization, and environment management into separate referenced files to reduce the main SKILL.md to a focused overview with clear navigation links.

Remove or significantly trim the 'Common Rationalizations' table and philosophical framing paragraphs ('Shift Left,' 'Faster is Safer') — these explain concepts Claude already understands.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary philosophical framing ('Shift Left,' 'Faster is Safer' explanations) and a 'Common Rationalizations' table that teaches Claude things it already knows. The ASCII pipeline diagram is useful but the surrounding prose could be tighter. Several sections like 'Build Cop Role' and feature flag explanations add bulk without being strictly necessary for CI/CD setup.	2 / 3
Actionability	The skill provides fully executable, copy-paste-ready GitHub Actions YAML configurations for basic CI, database integration tests, E2E tests, deployment previews, rollback workflows, and 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 flow 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 'No gate can be skipped' directive and error recovery patterns (CI fails → copy output → feed to agent → fix → push) provide clear feedback loops.	3 / 3
Progressive Disclosure	The content is a long monolithic document (~300 lines) covering pipeline setup, deployment strategies, environment management, optimization, and more. There are no references to external files for detailed topics like deployment strategies or E2E testing that could be split out. The mention of 'debugging-and-error-recovery skill' is a nice cross-reference but the document itself would benefit from splitting advanced topics into separate files.	2 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger term coverage for CI/CD-related queries. Its main weakness is that the capability descriptions are somewhat high-level and could be more concrete about specific actions, tools, or file types. The domain is reasonably distinct but broad enough that overlap with adjacent skills (testing, deployment, build tools) is possible.

Suggestions

Add more specific concrete actions such as 'generate GitHub Actions workflows, configure Jenkins pipelines, create .gitlab-ci.yml files' to improve specificity.

Mention specific CI/CD platforms or file formats (e.g., GitHub Actions, GitLab CI, CircleCI, .yml pipeline files) to improve distinctiveness and reduce conflict risk with adjacent skills.

Dimension	Reasoning	Score
Specificity	The description 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 and not fully concrete (e.g., doesn't specify which CI systems, what kinds of pipelines, 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 of pipelines, automating quality gates, configuring test runners, and establishing deployment strategies.	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'CI/CD', 'pipeline', 'build', 'deployment', 'quality gates', 'test runners', 'CI', 'deployment strategies'. These are terms users would naturally use when requesting this kind of help.	3 / 3
Distinctiveness Conflict Risk	While CI/CD is a reasonably specific domain, terms like 'build', 'deployment', and 'test runners' could overlap with skills focused on testing frameworks, deployment tools, or build systems individually. It's somewhat specific but not narrowly scoped enough to avoid all conflicts.	2 / 3
	Total	10 / 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: addyosmani/agent-skills
Commit: 5e262b2

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