CtrlK
BlogDocsLog inGet started
Tessl Logo

ci-cd-pipeline-builder

Generate pragmatic CI/CD pipelines from detected project stack signals — fast baseline generation, repeatable checks, environment-aware deployment stages. Use when setting up CI for a new project, refactoring existing pipelines, or standardizing deployment workflows across multiple repos.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering/skills/ci-cd-pipeline-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is well-structured and action-oriented with executable commands and a sensible workflow sequence. Its main weaknesses are mild redundancy between the Overview/Script Interfaces sections and a broken README.md reference.

Suggestions

Remove the near-verbatim restatement of the description in the Overview, or fold it into a single purpose statement to reduce token redundancy.

Delete the broken [README.md](README.md) reference or add the missing file so navigation links resolve.

Consolidate the Script Interfaces section with the Key Workflows examples to avoid duplicating the same stack_detector.py and pipeline_generator.py invocations.

Add an explicit validate->fix->retry feedback loop for generated pipelines (e.g., 'if local run fails, fix the YAML and re-run') to lift workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient, but the Overview nearly restates the frontmatter description verbatim and the Script Interfaces section duplicates the workflow commands already shown, which is more than minor padding and could be tightened.

3 / 5

Actionability

Provides concrete, copy-paste-ready bash commands with real flags (--repo, --input, --platform, --output, --format) covering detection and generation paths, with only minor gaps such as missing example output.

4 / 5

Workflow Clarity

Key Workflows are clearly sequenced and include a Validate Before Merge checklist plus production gating, but there is no explicit validate->fix->retry feedback loop, leaving a minor validation gap below the 5 anchor.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to real bundle files (pipeline-design-notes.md, github-actions-templates.md, gitlab-ci-templates.md, deployment-gates.md) and separate scripts, but the referenced README.md does not exist in the bundle, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

83%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.

The description is strong: third-person voice, explicit what-and-when, and good natural trigger phrases. It scores well on completeness and trigger quality, with only mild abstraction in the capability list keeping specificity below maximum.

DimensionReasoningScore

Specificity

Names the domain and several specific capabilities ("fast baseline generation, repeatable checks, environment-aware deployment stages"), but the actions are somewhat abstract gerund phrases rather than crisp concrete operations, so it falls below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Generate pragmatic CI/CD pipelines from detected project stack signals") and when ("Use when setting up CI for a new project, refactoring existing pipelines, or standardizing deployment workflows across multiple repos") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("setting up CI for a new project", "refactoring existing pipelines", "standardizing deployment workflows", "multiple repos"), but platform synonyms users say ("GitHub Actions", "GitLab CI", "continuous integration") are absent.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (stack-signal-driven CI/CD pipeline generation) with distinct triggers and minimal conflict risk, but minor overlap remains with general DevOps/deployment skills rather than being a totally isolated niche.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.