ci-cd
CI/CD pipeline design, optimization, DevSecOps security scanning, and troubleshooting. Use for creating workflows, debugging pipeline failures, implementing SAST/DAST/SCA, optimizing build performance, implementing caching strategies, setting up deployments, securing pipelines with OIDC/secrets management, and troubleshooting common issues across GitHub Actions, GitLab CI, and other platforms.
Install with Tessl CLI
npx tessl i github:ahmedasmar/devops-claude-skills --skill ci-cdOverall
score
90%
Does it follow best practices?
Validation 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 an excellent skill description that comprehensively covers the CI/CD and DevSecOps domain. It provides specific concrete actions, includes natural trigger terms that developers would use, explicitly states when to use the skill, and has clear distinctiveness through platform-specific and security-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating workflows', 'debugging pipeline failures', 'implementing SAST/DAST/SCA', 'optimizing build performance', 'implementing caching strategies', 'setting up deployments', 'securing pipelines with OIDC/secrets management', and 'troubleshooting common issues'. | 3 / 3 |
Completeness | Clearly answers both what (CI/CD pipeline design, optimization, security scanning, troubleshooting) and when with explicit 'Use for...' clause that lists specific trigger scenarios like creating workflows, debugging failures, and implementing security scanning. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CI/CD', 'pipeline', 'DevSecOps', 'workflows', 'build performance', 'caching', 'deployments', 'OIDC', 'secrets management', 'GitHub Actions', 'GitLab CI'. These are terms developers naturally use when discussing these topics. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on CI/CD pipelines and DevSecOps with distinct platform mentions (GitHub Actions, GitLab CI) and specific technical terms (SAST/DAST/SCA, OIDC) that make it unlikely to conflict with general coding or security skills. | 3 / 3 |
Total | 12 / 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 well-structured, highly actionable CI/CD skill with excellent workflow clarity and progressive disclosure. The content provides concrete, executable examples across multiple platforms and includes proper validation checkpoints. The main weakness is some verbosity in introductory sections and occasional redundancy that could be trimmed to improve token efficiency.
Suggestions
Remove or significantly condense the 'When to Use This Skill' section - these use cases are self-evident from the skill title and content
Consolidate the 'Best Practices Summary' section with the detailed sections above to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the 'When to Use This Skill' section listing obvious use cases Claude could infer, and some explanatory text that could be trimmed. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples for both GitHub Actions and GitLab CI, specific CLI commands, copy-paste ready YAML configurations, and concrete checklists. The decision trees and tables provide clear guidance for choosing approaches. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The troubleshooting section has a systematic 4-step approach, deployment workflows include health checks and rollback steps, and security scanning includes gate patterns for evaluation. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-organized sections, and one-level-deep references to detailed documentation (best_practices.md, security.md, devsecops.md, optimization.md, troubleshooting.md). Templates are clearly signaled with paths and descriptions. | 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 (574 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_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | 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.