azuredevops-pipelines-template
Azure DevOps Repos-first template architecture for reusable CI pipelines. Use when designing or debugging Azure Pipelines YAML templates, splitting PR validation from post-merge main workflows while reusing one core CI template, enforcing strict compile-time/runtime variable rules, building typed template APIs (`stepList`, `jobList`, `stageList`, `templateContext`), or creating self-contained dependency-management templates for TypeScript/Python/R using bun, npm, and pixi—e.g., "one CI template for PR and main", "fix expression timing bug", "design jobList template contract".
93
92%
Does it follow best practices?
Impact
93%
1.14xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 excels across all dimensions. It provides highly specific capabilities, comprehensive trigger terms including concrete example phrases, explicit 'Use when...' guidance, and a distinctive technical niche that clearly differentiates it from generic CI/CD skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'designing or debugging Azure Pipelines YAML templates', 'splitting PR validation from post-merge main workflows', 'building typed template APIs', 'creating self-contained dependency-management templates'. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both what (Repos-first template architecture for reusable CI pipelines) and when with explicit 'Use when...' clause covering multiple trigger scenarios, plus concrete example phrases at the end. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Azure Pipelines', 'YAML templates', 'PR validation', 'CI template', 'stepList', 'jobList', 'stageList', 'templateContext', 'TypeScript/Python/R', 'bun', 'npm', 'pixi', plus concrete example phrases like 'fix expression timing bug'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focusing specifically on Azure DevOps Repos template architecture with very specific technical terms (stepList, jobList, templateContext, pixi) that would not conflict with generic CI/CD or other pipeline 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 skill with excellent progressive disclosure and workflow clarity. The content is concise and respects Claude's intelligence. The main weakness is the lack of concrete, executable YAML examples—the skill describes patterns but doesn't provide copy-paste ready snippets for the core three-file topology it recommends.
Suggestions
Add a minimal but complete YAML example showing the three-file topology (azure-pipelines-pr.yml, azure-pipelines-main.yml, templates/ci-core.yml) with actual trigger configurations and template references.
Include a concrete parameter contract table example showing name, type, default, and allowed values rather than just describing what one should contain.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Azure DevOps concepts. No unnecessary explanations of what pipelines are or how YAML works—every section delivers actionable guidance without padding. | 3 / 3 |
Actionability | Provides clear conceptual guidance and specific patterns (e.g., trigger settings, expression syntax), but lacks concrete copy-paste YAML snippets. The 'Output Contract' promises YAML snippets but the skill itself doesn't include executable examples of the three-file topology. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit phases (topology → parameters → compile-time → runtime → validation). The validation step at the end provides a checkpoint, and the separation of concerns between skills is explicit. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references. The 'References (Load on Demand)' section provides specific guidance on when to load each reference file, enabling efficient navigation. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jjjermiah/dotagents
- Commit
b74de5e
- 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.