Azure Pipelines Log Downloader
ansible/ansible
Downloads Azure Pipelines CI logs for an Ansible pull request or build so the agent can analyze test failures, after asking you first.
Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices.
Install Azure Pipelines Validator
$ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install akin-ozer/cc-devops-skills azure-pipelines-validator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/devops-skills-plugin/skills/azure-pipelines-validator .claude/skills/azure-pipelines-validator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azure-pipelines-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validator into .claude/skills/azure-pipelines-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-pipelines-validator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validatorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install akin-ozer/cc-devops-skills azure-pipelines-validator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/devops-skills-plugin/skills/azure-pipelines-validator .agents/skills/azure-pipelines-validator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-pipelines-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validator into .agents/skills/azure-pipelines-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-pipelines-validator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install akin-ozer/cc-devops-skills azure-pipelines-validator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/devops-skills-plugin/skills/azure-pipelines-validator .cursor/skills/azure-pipelines-validator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azure-pipelines-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validator into .cursor/skills/azure-pipelines-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-pipelines-validator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/akin-ozer/cc-devops-skills.git --path devops-skills-plugin/skills/azure-pipelines-validator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install akin-ozer/cc-devops-skills azure-pipelines-validator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/devops-skills-plugin/skills/azure-pipelines-validator .gemini/skills/azure-pipelines-validator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azure-pipelines-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validator into .gemini/skills/azure-pipelines-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-pipelines-validator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install akin-ozer/cc-devops-skills azure-pipelines-validatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/devops-skills-plugin/skills/azure-pipelines-validator .github/skills/azure-pipelines-validator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azure-pipelines-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validator into .github/skills/azure-pipelines-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-pipelines-validator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install akin-ozer/cc-devops-skills azure-pipelines-validator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/devops-skills-plugin/skills/azure-pipelines-validator .opencode/skills/azure-pipelines-validator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azure-pipelines-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/azure-pipelines-validator into .opencode/skills/azure-pipelines-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-pipelines-validator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azure-pipelines-validator- GitHub stars
- 320
- Token cost
- ~1.5k tokens
- SKILL.md length
- 521 words
- Files
- 22 (incl. scripts, assets)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices.
- Works in 3 steps: Context7 docs tooling first. → Official docs second… → General web search only if the first two…
- DevOps & Cloud work in your project
- SKILL.md covers Trigger Phrases, Deterministic Path Setup (No…, Local-First Execution Model and Expected Report Format…, plus 5 more sections
- Runs Python and Shell scripts from its folder; calls bash and git
What it does
Azure Pipelines Validator is an agent skill from akin-ozer/cc-devops-skills. Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 25 other files, including scripts and assets (for example `docs/azure-pipelines-reference.md`, `examples/basic-pipeline.yml` and `examples/deployment-pipeline.yml`).
It sits in DevOps & Cloud. It works with Azure DevOps. The repository describes itself as: DevOps skills for Claude Code and Codex. The licence is Apache-2.0.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “/azure-pipelines-validator”
Requirements
- Python 3
- A Bash shell
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Context7 docs tooling first.
- Official docs second (learn.microsoft.com / Microsoft Azure DevOps docs).
- General web search only if the first two are insufficient.
What it can do on your machine
Read from SKILL.md and the folder at commit 276af75. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python and Shell, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
bashgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Azure Pipelines Validator loads about 1.5k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 521 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from akin-ozer/cc-devops-skills at commit 276af75, republished under its Apache-2.0 licence (© akin-ozer). 521 words, ~1,547 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-pipelines-validator/SKILL.md (or your agent's skills folder). This skill also uses 21 other files; get the full folder from GitHub.- name
- azure-pipelines-validator
- description
- Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices.
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
- Preflight
- Confirm
bashandpython3are available. - Confirm target file exists.
- 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- Interpret exit behavior
0: pass (or non-blocking checks only)1: validation failed (blocking issues)2: invalid invocation (missing/ambiguous file or bad args)
- 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:
- Context7 docs tooling first.
mcp__context7__resolve-library-id(...)
mcp__context7__query-docs(...)- Official docs second (
learn.microsoft.com/ Microsoft Azure DevOps docs). - General web search only if the first two are insufficient.
When escalating, cite the source URL and state what local check could not answer.
Show full SKILL.md (217 more words)Show less
Fallback Behavior
Use this matrix when tools are unavailable:
Condition:
yamllintunavailable.Action: Continue with syntax/best-practice/security checks.
Report note: "YAML lint skipped because yamllint is unavailable."
Condition:
python3unavailable 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-syntaxyaml-invalid-rootinvalid-hierarchytask-invalid-formatpool-invaliddeployment-missing-strategy
Best-practice examples:
missing-displaynametask-version-zerotask-missing-versionpool-latest-imagemissing-cachemissing-deployment-condition
Security examples:
hardcoded-passwordhardcoded-secretcurl-pipe-shelleval-commandinsecure-sslcontainer-latest-tagvariable-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.
© akin-ozer, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 21 other files (scripts, assets) in devops-skills-plugin/skills/azure-pipelines-validator of akin-ozer/cc-devops-skills.
- SKILL.md
- .gitignore
- assets/.yamllint
- docs/azure-pipelines-reference.md
- examples/basic-pipeline.yml
- examples/deployment-pipeline.yml
- examples/docker-build.yml
- examples/multi-platform.yml
- examples/regression-conditional-danger.yml
- examples/regression-runonce-on-failure.yml
- examples/template-conditional-stages.yml
- examples/template-conditional-steps.yml
- examples/template-example.yml
- examples/test-with-issues.yml
- scripts/check_best_practices.py
- scripts/check_security.py
- scripts/python_wrapper.sh
- … and 5 more
Open the folder on GitHubat commit 276af75
Compare with similar skills
Azure Pipelines Validator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azure Pipelines Validator this skillakin-ozer/cc-devops-skills | 320 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Azure Pipelines Log Downloaderansible/ansible | 71k | — | ~825 | Automated safety check: Pass | GPL-3.0 | |
| ONNX Runtime CI Managementmicrosoft/onnxruntime | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Megalinter Checknvuillam/npm-groovy-lint | 248 | 1 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Operate Pi Dispatchedgehero/pi-dispatch | 179 | — | ~7.8k | Automated safety check: Notes | MIT | |
| Tirith PoliciesStackGuardian/tirith | 170 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
ONNX Runtime CI Management
microsoft/onnxruntime
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
Megalinter Check
nvuillam/npm-groovy-lint
Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.
Operate Pi Dispatch
edgehero/pi-dispatch
How to operate a pi-dispatch deployment through its tools, and how to use the operator-confirm gates on the write tools (changing limits, adding/editing/deleting triggers).
Tirith Policies
StackGuardian/tirith
Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…
- Official
Sdaf Orientation And Surface
Azure/sap-automation
Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate/remove), summarise the three…
More from akin-ozer/cc-devops-skills
All 30 skills in this repoGitHub Actions Generator
akin-ozer/cc-devops-skills
Create, generate, or scaffold GitHub Actions workflows, action.yml, or .github/workflows CI/CD pipelines.
Helm Generator
akin-ozer/cc-devops-skills
Create, scaffold, or generate Helm charts, Chart.yaml, values.yaml, templates, helpers.
Jenkinsfile Generator
akin-ozer/cc-devops-skills
Generate/create/scaffold Jenkinsfile — declarative, scripted, shared library, CI/CD pipelines.
Dockerfile Validator
akin-ozer/cc-devops-skills
Validate, lint, audit, or scan a Dockerfile for security and best practices.
GitHub Actions Validator
akin-ozer/cc-devops-skills
Validate, lint, audit, fix GitHub Actions workflows (.github/workflows).
Jenkinsfile Validator
akin-ozer/cc-devops-skills
Validate, lint, audit, or check Jenkinsfiles and shared libraries.
Related
Works with
Categories
Questions about Azure Pipelines Validator
What does Azure Pipelines Validator do?
Validate, lint, audit, or review azure-pipelines.yml — syntax, security, best practices. Azure Pipelines Validator is an agent skill from akin-ozer/cc-devops-skills.yml — syntax, security, best practices.
When should I use Azure Pipelines Validator?
Azure Pipelines Validator fits situations like: devOps & Cloud work in your project.
How do I install Azure Pipelines Validator in Claude Code?
Run `npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a claude-code`. Or copy the skill folder (devops-skills-plugin/skills/azure-pipelines-validator in akin-ozer/cc-devops-skills) into .claude/skills/azure-pipelines-validator in your project. Claude Code loads it when a task matches its description.
How do I install Azure Pipelines Validator in Codex?
Run `npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a codex`. Or copy the skill folder (devops-skills-plugin/skills/azure-pipelines-validator in akin-ozer/cc-devops-skills) into .agents/skills/azure-pipelines-validator in your project. Codex loads it when a task matches its description.
Can I use Azure Pipelines Validator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-pipelines-validator, .gemini/skills/azure-pipelines-validator, .github/skills/azure-pipelines-validator and .opencode/skills/azure-pipelines-validator in your project.
What does Azure Pipelines Validator need to run?
Going by SKILL.md and its folder, Azure Pipelines Validator needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (bash and git). Our summary lists: Python 3; A Bash shell.
Does Azure Pipelines Validator access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Azure Pipelines Validator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Azure Pipelines Validator use?
Azure Pipelines Validator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Pipelines Validator use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Azure Pipelines Validator?
Skills that share tags, products or a category with Azure Pipelines Validator: Azure Pipelines Log Downloader (ansible/ansible, 71k stars), ONNX Runtime CI Management (microsoft/onnxruntime, 22k stars), Megalinter Check (nvuillam/npm-groovy-lint, 248 stars) and Operate Pi Dispatch (edgehero/pi-dispatch, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Pipelines Validator?
akin-ozer (a GitHub user) maintains it in akin-ozer/cc-devops-skills, which has 320 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on July 26, 2026.
Source: akin-ozer/cc-devops-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.