CtrlK
BlogDocsLog inGet started
Tessl Logo

ci-cd-and-automation

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ci-cd-and-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, copy-paste-ready CI/CD skill with complete workflows and a clear pipeline sequence. It is somewhat verbose and entirely monolithic, which limits conciseness and progressive disclosure.

Suggestions

Trim motivational prose and the 'Common Rationalizations' table to reduce tokens; keep only guidance Claude cannot infer.

Move the detailed workflow examples (integration, E2E, deployment strategies) into reference files under references/ and link to them from a lean overview.

Make the 'Feeding CI Failures Back to Agents' feedback loop concrete with per-failure commands instead of an ASCII diagram.

DimensionReasoningScore

Conciseness

Mostly efficient with abundant copy-paste YAML, but includes motivational prose ('CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss') and a 'Common Rationalizations' table that pad the token budget without adding executable guidance.

3 / 5

Actionability

Fully executable, copy-paste-ready GitHub Actions workflows (basic CI, postgres integration, Playwright E2E, preview deploy, rollback, dependabot, parallel jobs) plus a concrete TypeScript feature-flag pattern cover the common cases.

5 / 5

Workflow Clarity

The quality-gate pipeline and staged rollout are clearly sequenced with a monitor→rollback checkpoint and a final Verification checklist; the agent feedback loop is depicted abstractly in ASCII rather than as concrete per-failure commands, leaving minor validation gaps.

4 / 5

Progressive Disclosure

The body is well-organized into clear section headers, but at ~391 lines it is monolithic — all workflow examples and deployment strategies are inlined with no bundle files and no one-level-deep references to split the material.

3 / 5

Total

15

/

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 well-crafted third-person description that concretely names capabilities and gives two explicit 'Use when' trigger clauses. Minor room to add synonyms (e.g., GitHub Actions) and tighten generic verbs.

DimensionReasoningScore

Specificity

Names the CI/CD domain and several concrete actions ('automate quality gates, configure test runners in CI, or establish deployment strategies'), but verbs like 'setup' and 'establish' stay somewhat high-level rather than fully concrete.

4 / 5

Completeness

Clearly states the 'what' (CI/CD pipeline setup, quality gates, test runners, deployment strategies) and provides two explicit 'Use when...' trigger clauses answering 'when' with concrete phrases.

5 / 5

Trigger Term Quality

Strong natural keywords ('build and deployment pipelines', 'quality gates', 'test runners in CI', 'deployment strategies') that users would say, but misses common synonyms/extensions like GitHub Actions or .yml.

4 / 5

Distinctiveness Conflict Risk

CI/CD automation is a clear niche with distinct triggers ('build and deployment pipelines', 'test runners in CI') unlikely to fire for unrelated skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
addyosmani/agent-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.