azure-pipelines-generator

Generates production-ready Azure DevOps Pipelines (azure-pipelines.yml) following current best practices, security standards, and naming conventions. Use when creating or updating ADO YAML pipelines, configuring build triggers, defining multi-stage deployments, setting up template references, creating variable groups, writing release pipelines, or structuring CI/CD workflows for Azure DevOps Services or Azure DevOps Server. Handles build pipelines, YAML pipelines, Docker container builds, Kubernetes/AKS deployments, language-specific pipelines (.NET, Node.js, Python, Go, Java), and reusable step/job/stage templates. All generated configurations are validated using the devops-skills:azure-pipelines-validator skill before delivery.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

A strong, highly actionable skill body: complete executable examples with pinned versions, explicit validation and re-validation loops, and excellent progressive disclosure into verified bundle files. The main improvement opportunities are trimming the duplicated inline examples that also exist as assets and surfacing the end-to-end workflow inline instead of only via reference.

Suggestions

Replace the full inline basic-CI and multi-stage YAML examples with short excerpts and point to the matching assets/examples/*.yml files, removing duplication between the body and the bundle.

Inline the six-step workflow sequence (Understanding → Reading → Lookup → Generate → Validate → Present) as a brief ordered list in the Workflow Process section rather than deferring it entirely to references/typical-workflow.md.

Drop the Overview paragraph's restatement of the description and keep only the validation mandate, which is the new information.

Dimension	Reasoning	Score
Conciseness	The body is dense and example-driven with no explanation of concepts Claude already knows, but the Overview restates the description and inline YAML examples (basic CI, multi-stage CI/CD) duplicate content that also lives in assets/examples/, so some tokens could be trimmed.	4 / 5
Actionability	Fully executable copy-paste YAML for every pipeline type with pinned task versions (Docker@2, KubernetesManifest@0, GoTool@0), specific inputs, service-connection usage, and precise Go-specific flags (CGO_ENABLED=0, -race -coverprofile) covering the common cases.	5 / 5
Workflow Clarity	An explicit validation feedback loop is mandated ('always validate it using the devops-skills:azure-pipelines-validator skill, fix any reported issues, and re-validate') with an error-recovery troubleshooting table, but the main end-to-end sequence (Understanding → Reading → Lookup → Generate → Validate → Present) is deferred to a reference file rather than stated inline.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references: each capability section names the exact files to read, and two organized tables map every reference and example file (all verified to exist on disk) to its purpose and 'when to read' trigger.	5 / 5
	Total	18 / 20 Passed

Description

100%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.

The description is exemplary: it states concrete capabilities in third-person voice, provides an explicit 'Use when...' clause with natural trigger phrases including the file extension and product variants, and occupies a distinct niche with minimal overlap risk. Only nit is the trailing validation-process sentence, which adds mild length without improving triggering.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person ('Generates production-ready Azure DevOps Pipelines', 'configuring build triggers', 'defining multi-stage deployments', 'creating variable groups', 'writing release pipelines') with comprehensive coverage across build, Docker, Kubernetes/AKS, language-specific, and template pipelines.	5 / 5
Completeness	Explicitly answers both what ('Generates production-ready Azure DevOps Pipelines... following current best practices, security standards, and naming conventions') and when ('Use when creating or updating ADO YAML pipelines, configuring build triggers...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including the file extension ('azure-pipelines.yml'), product names ('Azure DevOps Services or Azure DevOps Server', 'ADO YAML pipelines'), and technology synonyms ('Kubernetes/AKS deployments', '.NET, Node.js, Python, Go, Java', 'CI/CD workflows').	5 / 5
Distinctiveness Conflict Risk	Clear niche scoped to Azure DevOps YAML pipelines with distinct triggers (azure-pipelines.yml, variable groups, service connections context); the slightly broad 'CI/CD workflows' term is explicitly anchored to Azure DevOps, keeping conflict risk minimal.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 18 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: pantheon-org/tekhne
Path: skills/ci-cd/azure-pipelines/generator/SKILL.md
Commit: a1083f4

Reviewed: 2 hours ago

Table of Contents

Discovery Implementation Validation

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.