MCPInstall

azure-pipelines-validator

by akin-ozerDevOps & Cloud

Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices.

Installs
639
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/akin-ozer/cc-devops-skills --skill azure-pipelines-validator
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads azure-pipelines-validator automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Azure Pipelines Validator

Use this skill to validate Azure DevOps pipeline YAML (azure-pipelines.yml / azure-pipelines.yaml) with local scripts first, then escalate to docs only when local output is not enough.

Trigger Phrases

Use this skill when the user asks things like:

  • "Validate my azure-pipelines.yml."
  • "Why is this Azure pipeline YAML failing?"
  • "Run a security scan on this Azure DevOps pipeline."
  • "Check this pipeline for best-practice issues."
  • "Review this pipeline in CI before merge."

Do not use this skill for pipeline generation from scratch. Use azure-pipelines-generator for that.

Deterministic Path Setup (No Ambiguity)

Run from any directory using explicit absolute paths:

REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null)"
SKILL_DIR="$REPO_ROOT/devops-skills-plugin/skills/azure-pipelines-validator"
PIPELINE_FILE="$REPO_ROOT/azure-pipelines.yml"

If REPO_ROOT is empty, stop and ask for the repository root path. Do not guess paths.

Validate one file:

bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE"

Auto-detect from current directory (up to depth 3):

bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh"

If auto-detect returns multiple files, rerun with one explicit file path.

Local-First Execution Model

  1. Preflight
  • Confirm bash and python3 are available.
  • Confirm target file exists.
  1. Run local validator
  • Default full pass:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE"
  • Syntax only:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --syntax-only
  • Best practices only:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --best-practices
  • Security only:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --security-only
  • Strict mode (warnings fail):
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --strict
  1. Interpret exit behavior
  • 0: pass (or non-blocking checks only)
  • 1: validation failed (blocking issues)
  • 2: invalid invocation (missing/ambiguous file or bad args)
  1. Return findings in the report format below.

Expected Report Format (Severity Buckets)

Always return results in this structure:

Validation Report: <path>

Summary:
- Blocking: <count>        # Syntax errors + Security critical/high
- Warning: <count>         # Security medium/low + best-practice warnings
- Info: <count>            # Suggestions
- Skipped: <count>         # Explicitly name skipped checks

Findings:
- [Blocking][syntax][<rule-id>] line <n> - <message>
- [Blocking][security-high][<rule-id>] line <n> - <message>
- [Warning][security-medium][<rule-id>] line <n> - <message>
- [Warning][best-practice][<rule-id>] line <n> - <message>
- [Info][best-practice][<rule-id>] line <n> - <message>

Remediation:
- <short, concrete fix per finding>

Execution Notes:
- Commands run: <exact commands>
- Environment/fallback notes: <tool missing, skipped checks, offline constraints>

Escalation Policy (Docs Only When Needed)

Run local checks first. Escalate only when at least one condition is true:

  • Local finding depends on current upstream behavior (task versions, deprecations, new inputs).
  • User asks for "latest/current/recent" Azure Pipelines task or schema details.
  • Local scripts cannot determine validity for a specific task/resource syntax.

Escalation order:

  1. Context7 docs tooling first.
mcp__context7__resolve-library-id(...)
mcp__context7__query-docs(...)
  1. Official docs second (learn.microsoft.com / Microsoft Azure DevOps docs).
  2. General web search only if the first two are insufficient.

When escalating, cite the source URL and state what local check could not answer.

Fallback Behavior

Use this matrix when tools are unavailable:

  • Condition: yamllint unavailable.

  • Action: Continue with syntax/best-practice/security checks.

  • Report note: "YAML lint skipped because yamllint is unavailable."

  • Condition: python3 unavailable or venv/dependency setup fails.

  • Action: Mark scripted validation blocked; perform manual YAML review only if requested.

  • Report note: "Local scripted validation blocked by missing Python runtime/dependencies."

  • Condition: No network while dependencies/docs are needed.

  • Action: Run whatever local checks are still possible; defer doc/version verification.

  • Report note: "External verification deferred due offline environment."

  • Condition: Multiple auto-detected pipeline files.

  • Action: Do not pick arbitrarily; require explicit target file path.

  • Report note: "Validation paused until a single target file is specified."

Rule Buckets (What the Scripts Check)

Syntax examples:

  • yaml-syntax
  • yaml-invalid-root
  • invalid-hierarchy
  • task-invalid-format
  • pool-invalid
  • deployment-missing-strategy

Best-practice examples:

  • missing-displayname
  • task-version-zero
  • task-missing-version
  • pool-latest-image
  • missing-cache
  • missing-deployment-condition

Security examples:

  • hardcoded-password
  • hardcoded-secret
  • curl-pipe-shell
  • eval-command
  • insecure-ssl
  • container-latest-tag
  • variable-not-secret

Use script output rule IDs directly in the report.

References and Examples

  • Syntax reference: docs/azure-pipelines-reference.md
  • Example pipelines: examples/

Quick local test:

bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$SKILL_DIR/examples/basic-pipeline.yml"

Done Criteria

This skill execution is done when all conditions are true:

  • Trigger match is explicit and plain-language examples are provided near the top.
  • Validation command(s) were run with unambiguous paths.
  • Report uses severity buckets (Blocking, Warning, Info, Skipped).
  • Fallback behavior is explicitly reported for unavailable tools/environment constraints.
  • External docs were consulted only when local checks were insufficient.

FAQ

What does the azure-pipelines-validator skill do?

Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices.

How do I install azure-pipelines-validator?

Run npx skills add https://github.com/akin-ozer/cc-devops-skills --skill azure-pipelines-validator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/azure-pipelines-validator/ (personal) or .claude/skills/azure-pipelines-validator/ (project).

Which AI agents can use azure-pipelines-validator?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is azure-pipelines-validator safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains azure-pipelines-validator?

It is published by akin-ozer in akin-ozer/cc-devops-skills. It has 639 recorded installs.

More from akin-ozer/cc-devops-skills

View all →

ansible-validator

akin-ozer/cc-devops-skills

Validate, lint, audit, or debug Ansible playbooks, roles, inventories, FQCN, tasks.

Code Quality & Workflow1.3K installs

terragrunt-generator

akin-ozer/cc-devops-skills

Generate/create/scaffold Terragrunt HCL files — root.hcl, terragrunt.hcl, child modules, stacks, multi-env layouts.

DevOps & Cloud1.2K installs

k8s-debug

akin-ozer/cc-devops-skills

Diagnose and fix Kubernetes pods, CrashLoopBackOff, Pending, DNS, networking, storage, and rollout failures with kubectl.

DevOps & Cloud825 installs

ansible-generator

akin-ozer/cc-devops-skills

Generate, create, or scaffold Ansible playbooks, roles, tasks, handlers, inventory, vars.

DevOps & Cloud817 installs

jenkinsfile-generator

akin-ozer/cc-devops-skills

Generate/create/scaffold Jenkinsfile — declarative, scripted, shared library, CI/CD pipelines.

DevOps & Cloud809 installs

dockerfile-validator

akin-ozer/cc-devops-skills

Validate, lint, audit, or scan a Dockerfile for security and best practices.

Code Quality & Workflow744 installs

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs