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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill workers-ci-cdOverall
score
87%
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
89%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-constructed skill description with strong trigger term coverage and clear completeness. The explicit 'Use for' clause with multiple trigger scenarios (including error conditions) makes it easy for Claude to identify when to select this skill. The main weakness is that the capabilities could be more concrete and specific rather than listing general categories.
Suggestions
Add more concrete specific actions like 'configure wrangler.toml', 'set up branch-based preview URLs', 'debug failed GitHub Actions workflows' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD for Cloudflare Workers) and mentions several actions (automated testing, deployment pipelines, preview environments, secrets management), but these are somewhat high-level categories rather than concrete specific actions like 'configure wrangler.toml' or 'set up branch-based preview deployments'. | 2 / 3 |
Completeness | Clearly answers both what (CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI) and when (Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues). Has explicit 'Use for' clause with trigger scenarios. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'CI/CD', 'GitHub Actions', 'GitLab CI', 'Cloudflare Workers', 'deployment pipelines', 'preview environments', 'secrets management', 'deployment failures', 'workflow errors'. These are terms users would naturally use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Cloudflare Workers with GitHub Actions/GitLab CI. The combination of platform (Cloudflare Workers) and CI tools (GitHub Actions, GitLab CI) creates a distinct trigger profile unlikely to conflict with generic CI/CD or generic Cloudflare skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, production-ready skill with excellent actionability and workflow clarity. The content provides complete, executable examples with proper validation checkpoints and clear navigation to reference materials. Minor verbosity in introductory sections and some explanations of concepts Claude already knows prevent a perfect conciseness score.
Suggestions
Remove or significantly condense the 'What Is Workers CI/CD?' section - Claude understands CI/CD concepts
Trim explanatory text like 'Key capabilities' list and 'Why' explanations after each critical rule - the correct/incorrect examples are self-explanatory
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., explaining what CI/CD is, what preview deployments are). The 'What Is Workers CI/CD?' section explains concepts Claude already knows. Some sections could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable YAML workflows, specific commands, copy-paste ready code examples, and concrete step-by-step instructions for setup. All code examples are complete and runnable. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints (test before deploy, verify deployment success, approval gates). The Critical Rules section explicitly shows correct vs incorrect patterns with validation steps. Error recovery is addressed in the errors section. | 3 / 3 |
Progressive Disclosure | Well-structured with clear table of contents, concise overview sections, and explicit 'When to Load References' section pointing to one-level-deep reference files. Templates and scripts are clearly signaled for deeper content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (696 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- 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.