azure-pipelines-validator SKILL.md skillB
azure-pipelines-validator from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/azure-pipelines-validator@git:20261005.434cb39Pins git:20261005.434cb39 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pantheon-org/tekhne
- Path
skills/ci-cd/azure-pipelines/validator/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261005.434cb39, committed Oct 5, 2026
- First version recorded
- Mar 3, 2026
- Size
- 12,931 bytes
- Repository stars
- 10
- License
- MIT
Validates, lints, and security-scans Azure DevOps Pipeline configurations (azure-pipelines.yml / azure-pipelines.yaml). Use when working with ADO pipelines, YAML pipeline files, or CI/CD configurations in Azure DevOps: including validating YAML syntax and schema, detecting hardcoded secrets or credentials, checking for deprecated or unpinned task versions, enforcing best practices (caching, timeouts, display names), performing pipeline security audits, or reviewing azure-pipelines.yml before…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Azure Pipelines Validator Validates, lints, and security-scans Azure DevOps Pipeline configurations (`azure-pipelines.yml`, `azure-pipelines.yaml`). Runs four validation layers via a single orchestrator script. ## Philosophy - Static analysis is cheap and runs before the pipeline does, so catch problems at review time, not at queue time. - Fix findings in layer order (lint, syntax, best practices, security): a syntax error can hide later findings. - Treat security findings as merge blockers and best-practice findings as guidance that hardens over time. - Re-run only the layer you just fixed, then run the full validation once before merging. ## When to Use - Reviewing `azure-pipelines.yml` or `azure-pipelines.yaml` before merging a change. - Auditing a pipeline for hardcoded secrets, `:latest` container tags or `curl | bash` patterns. - Checking task version pinning, `displayName`, caching and timeouts on an existing pipeline. - Adding a validation gate to an Azure Pipelines CI job. ## When Not to Use - Executing or testing a pipeline run: this skill does static analysis only. - Looking up current task inputs or versions: use the live documentation sources listed below. …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/azure-pipelines-validator@sha256:17fca339617e0065The line at the top of this page pins the label git:20261005.434cb39, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mh42e57q4rahloz4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 3, 2026 and Oct 5, 2026, about one every 72 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.434cb39 latest | 2026-10-05 | 434cb39 | 12,931 B | B | view · diff |
| git:20261001.6ed2a6a | 2026-10-01 | 6ed2a6a | 12,930 B | B | view · diff |
| git:20260316.2d4c8cf | 2026-03-16 | 2d4c8cf | 9,476 B | A | view · diff |
| git:20260303.39eba09 | 2026-03-03 | 39eba09 | 7,334 B | A | view |
Audit of the latest version
- fail: No curl or wget piped into a shell (matched: curl | bash)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12931 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mh42e57q4rahloz4 GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/azure-pipelines-validator GET https://markdownregistry.com/api/v1/blob/17fca339617e0065aff1b00252148450734183ff9dddd0a3159b270857e782ce
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.