CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudflare-workers-ci-cd

Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.

65

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 ./plugins/cloudflare-workers/skills/cloudflare-workers-ci-cd/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.

Highly actionable and well-structured CI/CD guidance with strong verification emphasis, weakened by length/redundancy and by references to template files that are absent from the bundle.

Suggestions

Create the four missing template files referenced under 'When to Load References' (github-actions-full.yml, gitlab-ci-full.yml, preview-deployment.yml, rollback-workflow.yml), or remove those load prompts to avoid dead references.

De-duplicate the nearly identical deploy workflows in Quick Start and Use Case 1, and consolidate overlapping items between Critical Rules and Best Practices to reduce token weight.

Strengthen the Quick Start's verification step with an explicit command (e.g., the curl health check used in Critical Rule 4 or scripts/verify-deployment.sh) instead of 'Check Actions tab'.

DimensionReasoningScore

Conciseness

At ~680 lines the body is mostly useful and not padded with concepts Claude already knows, but it repeats near-identical deploy workflows (Quick Start vs Use Case 1) and overlaps Best Practices with Critical Rules, so it could be tightened.

3 / 5

Actionability

Provides copy-paste-ready YAML and bash covering the common cases (deploy-on-push, PR preview, test-on-commit, manual approval, canary), with the only partial example explicitly deferring to a reference file.

5 / 5

Workflow Clarity

A numbered Quick Start, verification as a Critical Rule, a verify-deployment script, and an error-recovery section give clear sequencing and validation; the Quick Start's own verify step is weak ('Check Actions tab') but broader validation guidance is strong.

4 / 5

Progressive Disclosure

Has a TOC and a dedicated 'When to Load References' section with one-level-deep refs, but four referenced templates/*.yml files do not exist in the bundle and much workflow content is inlined that could be split out.

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 strong, specific description with explicit what-and-when guidance and clear niche triggers. Slightly held back by nominalized capability phrasing and minor coverage gaps versus the body content.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities ('automated testing, deployment pipelines, preview environments, secrets management'), but they are nominalized rather than verb phrases and rollback/canary strategies from the body are omitted, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI') and when via a concrete 'Use for ... or encountering deployment failures, workflow errors, environment configuration issues' trigger clause.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('CI/CD', 'GitHub Actions', 'GitLab CI', 'deployment failures', 'workflow errors', 'environment configuration issues') with good error-situation coverage, though a few natural variations are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a tight Cloudflare Workers CI/CD niche with platform-specific triggers, making overlap with generic CI/CD skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (682 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
secondsky/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.