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.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill cd-pipeline-generator89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (deployment workflows with approval gates, secrets management, rollback), includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche around GitHub Actions deployment automation for major cloud platforms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate GitHub Actions deployment workflows', 'automated deployment to staging and production environments', 'environment-specific deployments with approval gates, secrets management, and rollback capabilities'. Names specific cloud platforms (AWS, GCP, Azure). | 3 / 3 |
Completeness | Clearly answers both what ('Generate GitHub Actions deployment workflows for automated deployment...') and when ('Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies'). Explicit 'Use when...' clause present. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GitHub Actions', 'deployment workflows', 'continuous deployment', 'deployment pipelines', 'deployment automation', 'staging', 'production', 'AWS', 'GCP', 'Azure', 'approval gates', 'secrets management', 'rollback'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub Actions deployment workflows for cloud platforms. The combination of 'GitHub Actions' + 'deployment' + specific cloud platforms creates a distinct trigger profile unlikely to conflict with general CI/CD or other workflow skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid skill with excellent actionability through concrete YAML examples and good progressive disclosure. The main weaknesses are some verbosity in explaining concepts Claude already knows and missing validation checkpoints in the deployment workflow (e.g., verify staging deployment succeeded before allowing production deployment).
Suggestions
Add explicit validation steps after deployment (e.g., 'Verify staging deployment: run health check → if fails, stop and debug → only proceed to production when staging is verified')
Trim the cloud platform/service listings in section 1 - Claude knows what AWS ECS and GCP Cloud Run are
Integrate the rollback capability into the main workflow as a validation checkpoint rather than a separate customization example
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., listing all cloud platforms and services Claude already knows). The tips section and some security best practices could be trimmed as they explain concepts Claude understands. | 2 / 3 |
Actionability | Provides concrete, executable YAML snippets for each customization scenario. Code examples are copy-paste ready with clear context for when to use each pattern. References specific template files and exact GitHub settings paths. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. No feedback loop for verifying deployment success before proceeding or handling failures systematically. The rollback example is shown but not integrated into a validation workflow. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to workflow to customization. References external template files in assets/ appropriately. Content is organized for easy navigation without deep nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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.
- Reviewed
Table of Contents
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.