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

77%

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 ./plugins/devops/ci-cd-pipeline-builder/skills/building-cicd-pipelines/SKILL.md

Quality

Content

65%

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

The body is concise and well-sectioned with a useful error-handling table, but it stays at the directive level rather than providing executable templates, lacks a deploy validation feedback loop, and fails to navigate to its own bundled scripts and templates.

Suggestions

Reference the bundled assets and scripts from the body — e.g. 'See assets/github_actions_template.yml' and 'Run scripts/pipeline_generator.py' / 'scripts/validator.py' — so the existing bundle is actually discoverable from SKILL.md.

Add an executable YAML snippet (or a pointer to a template) so pipeline generation is copy-paste ready rather than the abstract 'Generate the pipeline configuration file with appropriate triggers' directive.

Insert an explicit validate→fix→retry feedback loop around the production deploy step (e.g. validate with actionlint, on failure fix and re-validate, only then deploy) since deployment is destructive.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — it does not teach concepts Claude already knows, the Overview packs concrete stage coverage into one sentence, and every section earns its tokens. The Current State probe is a tight, useful executable check.	3 / 3
Actionability	It names concrete tools (actionlint, gitlab-ci-lint) and includes an executable probe, but the core generation guidance is directive ('Generate the pipeline configuration file with appropriate triggers') with no inline executable YAML/template, and the bundled template assets are never referenced.	2 / 3
Workflow Clarity	The 10 numbered steps give a clear sequence and a final validation step, but there is no explicit validate→fix→retry feedback loop; since production deployment is destructive, the missing checkpoint caps this at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but the body never links the existing bundle (assets templates, scripts/pipeline_generator.py, scripts/validator.py) — content that should be split out stays inline and the bundle is unreachable from SKILL.md.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 well-structured with explicit trigger guidance and natural trigger phrases, scoring strongly across the board. Its only weakness is mild fluff ('comprehensive guidance and automation') and slightly abstract capability language.

Dimension	Reasoning	Score
Specificity	Names the domain ('deployment and CI/CD') and a couple of action areas ('deployment automation and pipeline orchestration'), but the actions are abstract and padded with fluff ('comprehensive guidance and automation') rather than listing multiple concrete capabilities.	2 / 3
Completeness	Explicitly answers both what ('deployment automation and pipeline orchestration') and when ('Execute use when you need to work with deployment and CI/CD' and 'Trigger with phrases like ...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Provides natural phrases a user would actually say — 'deploy application', 'create pipeline', 'automate deployment', plus 'deployment and CI/CD' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	CI/CD pipeline generation is a clear niche with distinct deploy/pipeline triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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
Path: plugins/devops/ci-cd-pipeline-builder/skills/building-cicd-pipelines/SKILL.md
Commit: 15940c5

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.