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".
Install with Tessl CLI
npx tessl i github:jjjermiah/dotagents --skill azuredevops-pipelines-template94
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 excels across all dimensions. It provides highly specific capabilities around Azure DevOps template architecture, includes natural trigger terms users would actually say, explicitly states when to use it with concrete example phrases, and occupies a clear niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: designing/debugging Azure Pipelines YAML templates, splitting PR validation from post-merge workflows, enforcing variable rules, building typed template APIs with specific types (stepList, jobList, stageList, templateContext), and creating dependency-management templates for specific languages/tools. | 3 / 3 |
Completeness | Clearly answers both what (Azure DevOps Repos-first template architecture for reusable CI pipelines) and when (explicit 'Use when...' clause with multiple trigger scenarios plus concrete example phrases like 'one CI template for PR and main', 'fix expression timing bug'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Azure Pipelines', 'YAML templates', 'PR validation', 'CI template', 'expression timing bug', 'jobList template contract', plus specific tool names (bun, npm, pixi) and languages (TypeScript, Python, R). The quoted examples at the end directly mirror user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focusing specifically on Azure DevOps Repos template architecture with very specific triggers (Azure Pipelines YAML, template APIs, stepList/jobList/stageList). Unlikely to conflict with generic CI/CD or other pipeline skills due to Azure-specific terminology and template-focused scope. | 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 organization, clear workflow sequencing, and appropriate progressive disclosure through reference files. The main weakness is the lack of concrete, copy-paste ready YAML examples—the skill describes patterns and contracts but relies on reference files for actual implementation snippets, which reduces immediate actionability.
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 template parameter passing
Include at least one concrete example of compile-time vs runtime expression usage in context, showing the ${{ }} and $[ ] syntax in a real condition
| 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 (file topology, expression syntax rules, dependency commands), but lacks copy-paste ready YAML snippets. The workflow and output contract describe what to produce rather than showing executable examples. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit phases (topology → parameters → compile-time → runtime → validation). The output contract provides a validation checklist, and the skill explicitly addresses the PR/main validation paths. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references. Each reference file is clearly labeled with when to load it, enabling efficient navigation without nested indirection. | 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.
- 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.