cd-pipeline-generator

Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies. Includes templates for environment-specific deployments with approval gates, secrets management, and rollback capabilities.

1.14x

Quality

74%

Does it follow best practices?

Impact

100%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cd-pipeline-generator/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

A well-structured, actionable skill body that externalizes templates appropriately, but it lacks explicit validation/verification checkpoints for destructive production deployments and carries some over-explanation in the security and tips sections.

Suggestions

Add an explicit validation/verification checkpoint to the workflow (e.g., a mandatory 'Verify deployment: run health check and confirm rollback readiness before declaring success' step) to lift workflow_clarity above the destructive-operation cap.

Replace the placeholder rollback example with a concrete, executable per-platform rollback snippet, or link to platform-specific rollback details in the asset files.

Trim the Security Best Practices and Tips sections to non-obvious items only, removing advice Claude already knows (e.g., 'never commit credentials') to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and actionable, but the Security Best Practices and Tips sections include guidance Claude already knows ('Never commit credentials or API keys to the repository', 'Add deployment metrics and monitoring'), and these could be trimmed.	3 / 5
Actionability	Provides many concrete, copy-pasteable YAML snippets and explicit secret lists, but the rollback example is a placeholder ('# Platform-specific rollback commands') rather than executable code, leaving a minor gap.	4 / 5
Workflow Clarity	The 7-step sequence is clearly ordered, but production deployment is a destructive operation and validation checkpoints are only implicit — the health check appears as an optional customization rather than a mandatory verify step — so the workflow is capped at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	References real bundle files (assets/deploy-aws.yml, deploy-gcp.yml, deploy-azure.yml) one level deep with clear signaling, but the body inlines customization examples and tips that could be split into separate reference files.	4 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

A strong, specific description that clearly states both capability and trigger conditions with natural language. Minor room to add common synonyms and enumerate a few more distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Generate GitHub Actions deployment workflows', 'automated deployment to staging and production') and specific features ('approval gates, secrets management, and rollback capabilities'), but centers on one core action with a feature list rather than multiple distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms') and when ('Use when setting up continuous deployment pipelines...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('setting up continuous deployment pipelines', 'creating deployment automation', 'configuring multi-environment deployment strategies') that users would say, but a few common synonyms (e.g., 'CD', 'release pipeline', 'deploy') are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (GitHub Actions CD to AWS/GCP/Azure with environment gates) with distinct triggers and minimal overlap risk against general CI or cloud-deploy skills.	5 / 5
	Total	18 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/cd-pipeline-generator/SKILL.md
Commit: 4f38503

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