building-cicd-pipelines

Execute use when you need to work with deployment and CI/CD. This skill provides deployment automation and pipeline orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is concise, well-sequenced, and includes validation plus error-recovery guidance, making it a solid instruction-style skill. Its main gaps are the lack of executable/copy-paste pipeline examples and no use of the provided bundle files for progressive disclosure.

Suggestions

Add at least one concrete, copy-paste-ready example pipeline config (e.g. a minimal GitHub Actions workflow YAML) inline or via a referenced template file.

Reference the bundle assets/scripts from the body (e.g. 'See assets/github_actions_template.yml' and 'Run scripts/validator.py') so the provided bundle is actually discoverable, and ensure those files exist rather than just README placeholders.

Turn step 10's validation into an explicit checkpoint ('if validation fails, fix and re-run') to make the feedback loop unmistakable.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-structured — it does not explain CI/CD concepts Claude already knows, and each section (Instructions, Error Handling table, Examples, Resources) earns its place without padding.	3 / 3
Actionability	Guidance is concrete — naming specific files (`.github/workflows/`, `.gitlab-ci.yml`), tools (`actionlint`, `gitlab-ci-lint`), and stages — but there are no actual copy-paste-ready pipeline configs or code snippets, and the template/script bundle files it implies are not provided or referenced.	2 / 3
Workflow Clarity	The 10-step Instructions give a clear sequence that ends with an explicit validation step (step 10: 'Validate the pipeline syntax using platform-specific tools'), and the Error Handling table plus step 8's manual-approval and automated-rollback gates provide feedback loops for recovery.	3 / 3
Progressive Disclosure	The body is organized into clear sections but is a single monolithic file with no references to the bundle directories; the templates and scripts listed in assets/scripts READMEs are neither linked nor split out, so content that should live one level deep is missing or inline.	2 / 3
	Total	10 / 12 Passed

Description

80%

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 clearly conveys what the skill does and when to use it with natural trigger phrases, but it is grammatically awkward ('Execute use when'), uses second-person voice, and pads with vague phrasing like 'comprehensive guidance and automation'. Tightening the wording and switching to third-person concrete actions would raise the specificity dimension.

Suggestions

Rewrite in third person and fix the broken opener, e.g. 'Generates CI/CD pipeline configurations for GitHub Actions, GitLab CI, Jenkins, CircleCI, and Azure DevOps. Use when the user asks to create a pipeline, automate deployment, or set up CI/CD.'

Replace the vague phrase 'comprehensive guidance and automation' with concrete actions such as 'lint, test, build, scan, and deploy with gating and rollback'.

Add a few more natural trigger variations users might say (e.g. 'set up CI/CD', 'GitHub Actions workflow', 'configure deployment pipeline') to broaden coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of abstract actions ('deployment automation and pipeline orchestration with comprehensive guidance and automation'), which would base at 2, but it uses second-person voice ('when you need to work with') so specificity is reduced by 1 per the rubric; 'comprehensive guidance and automation' is also vague padding rather than a concrete action.	1 / 3
Completeness	It explicitly answers both what ('deployment automation and pipeline orchestration') and when ('Execute use when you need to work with deployment and CI/CD' plus 'Trigger with phrases like...'), satisfying the explicit-trigger requirement that would otherwise cap this at 2.	3 / 3
Trigger Term Quality	It lists natural phrases a user would actually say — 'deploy application', 'create pipeline', 'automate deployment' — alongside 'deployment and CI/CD', giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	CI/CD pipeline generation is a clear niche with distinct triggers ('create pipeline', 'automate deployment'), making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 1 day 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.