Debate Review
amElnagdy/review-skills
Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.
Diagnoses a single Azure Pipelines build. An agent skill from dotnet/docker-tools.
Install Investigating Pipeline
$ npx skills add dotnet/docker-tools --skill investigating-pipeline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dotnet/docker-tools investigating-pipeline --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/dotnet/docker-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/investigating-pipeline .claude/skills/investigating-pipeline && 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 "investigating-pipeline" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/investigating-pipeline into .claude/skills/investigating-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-pipeline", 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/dotnet/docker-tools/tree/main/.github/skills/investigating-pipelineType 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 dotnet/docker-tools --skill investigating-pipeline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dotnet/docker-tools investigating-pipeline --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/investigating-pipeline .agents/skills/investigating-pipeline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigating-pipeline" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/investigating-pipeline into .agents/skills/investigating-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-pipeline", 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 dotnet/docker-tools --skill investigating-pipeline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dotnet/docker-tools investigating-pipeline --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/investigating-pipeline .cursor/skills/investigating-pipeline && 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 "investigating-pipeline" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/investigating-pipeline into .cursor/skills/investigating-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-pipeline", 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/dotnet/docker-tools.git --path .github/skills/investigating-pipeline--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 dotnet/docker-tools --skill investigating-pipeline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dotnet/docker-tools investigating-pipeline --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/investigating-pipeline .gemini/skills/investigating-pipeline && 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 "investigating-pipeline" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/investigating-pipeline into .gemini/skills/investigating-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-pipeline", 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 dotnet/docker-tools investigating-pipelineInstalls 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 dotnet/docker-tools --skill investigating-pipeline -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/investigating-pipeline .github/skills/investigating-pipeline && 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 "investigating-pipeline" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/investigating-pipeline into .github/skills/investigating-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-pipeline", 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 dotnet/docker-tools --skill investigating-pipeline -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dotnet/docker-tools investigating-pipeline --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/docker-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/investigating-pipeline .opencode/skills/investigating-pipeline && 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 "investigating-pipeline" agent skill from https://github.com/dotnet/docker-tools/tree/main/.github/skills/investigating-pipeline into .opencode/skills/investigating-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-pipeline", 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
investigating-pipeline- GitHub stars
- 181
- Token cost
- ~259 tokens
- SKILL.md length
- 72 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnoses a single Azure Pipelines build. An agent skill from dotnet/docker-tools.
- A user provides a build ID
- SKILL.md covers How to view the build timeline and How to read pipeline logs
- Calls pwsh
- Azure DevOps build URL and wants to understand what failed and why
What it does
Investigating Pipeline is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Diagnoses a single Azure Pipelines build. Shows the build timeline tree with stages, jobs, and task results, and retrieves task logs for debugging failures. Use when a user provides a build ID or Azure DevOps build URL and wants to understand what failed and why.
Its SKILL.md is about 260 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Azure DevOps. The repository describes itself as: This is a repo to house some common tools for our various docker repos. The licence is MIT.
When your agent uses it
- A user provides a build ID
- Azure DevOps build URL and wants to understand what failed and why
Example prompts
- “Use the investigating-pipeline skill to diagnose a single Azure Pipelines build. An agent skill from dotnet/docker-tools”
- “/investigating-pipeline”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit ef7fe45. 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
Shell commands in SKILL.md call:
pwsh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Investigating Pipeline loads about 259 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 72 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from dotnet/docker-tools at commit ef7fe45, republished under its MIT licence (© dotnet). 72 words, ~259 tokens.
Download SKILL.mdSave it as
.claude/skills/investigating-pipeline/SKILL.md (or your agent's skills folder).- name
- investigating-pipeline
- description
- Diagnoses a single Azure Pipelines build. Shows the build timeline tree with stages, jobs, and task results, and retrieves task logs for debugging failures. Use when a user provides a build ID or Azure DevOps build URL and wants to understand what failed and why.
Investigating Azure Pipelines builds
This document contains useful patterns for inspecting Azure Pipelines builds.
How to view the build timeline
Use Show-BuildTimeline.ps1 to view a build's timeline.
This includes all stages, jobs, and tasks along with their results.
pwsh ./eng/docker-tools/skill-helpers/Show-BuildTimeline.ps1 <org> <project> <buildId>Each node includes a log ID (Task #42 means log ID 42).
How to read pipeline logs
First, get the log ID from the build timeline.
Then, use Get-BuildLog.ps1 to print the full log:
pwsh ./eng/docker-tools/skill-helpers/Get-BuildLog.ps1 -Organization dnceng -Project internal -BuildId $buildId -LogId $logId© dotnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/investigating-pipeline of dotnet/docker-tools.
Open the folder on GitHubat commit ef7fe45
Compare with similar skills
Investigating Pipeline 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 |
|---|---|---|---|---|---|---|
| Investigating Pipeline this skilldotnet/docker-tools | 181 | — | ~259 | Automated safety check: Pass | MIT | |
| Debate ReviewamElnagdy/review-skills | 132 | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Azdo Internalmicrosoft/aspire | 6.4k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Component Governance RemediationOfficeDev/microsoft-365-agents-toolkit | 780 | — | ~3k | Automated safety check: Pass | Custom licence | |
| Leanspeccodervisor/leanspec | 296 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Respond To PR Commentsmicrosoft/PromptKit | 111 | — | ~4.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Azdo Internal
microsoft/aspire
A skill your agent uses when asked to trigger or inspect Aspire internal Azure DevOps builds, source-index runs, or release validation on dnceng/internal; push to the internal mirror; download build…
Component Governance Remediation
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: retrieving, exporting, triaging, or remediating Azure DevOps Component Governance alerts for this repository, including CG report URLs, vulnerable pnpm dependencies…
Leanspec
codervisor/leanspec
The spec-coding methodology for AI-assisted development. An agent skill from codervisor/leanspec.
- Official
Respond To PR Comments
microsoft/PromptKit
Respond to pull request review comments on GitHub or Azure DevOps Services.
- Official
Release
microsoft/DirectXTK12
Guide for performing the DirectX Tool Kit for DirectX 12 release process.
More from dotnet/docker-tools
- Official
Investigating Pull Request
dotnet/docker-tools
Inspect GitHub pull request status, read review comments, and diagnose PR validation failures.
- Official
Reviewing Csharp
dotnet/docker-tools
Reviews C changes in the ImageBuilder codebase against the repo's modern C conventions and invariants.
- Official
Triaging Pipelines
dotnet/docker-tools
Triage recent Azure Pipelines runs and failures. An agent skill from dotnet/docker-tools.
- Official
Docs Maintenance
dotnet/docker-tools
Reviews or updates repository documentation as a dedicated task after implementation is complete.
- Official
Triaging Pull Requests
dotnet/docker-tools
Triage open pull requests into actionable categories. An agent skill from dotnet/docker-tools.
Related
Works with
Categories
Questions about Investigating Pipeline
What does Investigating Pipeline do?
Diagnoses a single Azure Pipelines build. An agent skill from dotnet/docker-tools. Investigating Pipeline is an agent skill from dotnet/docker-tools, published by the product's own GitHub organization. Diagnoses a single Azure Pipelines build.
When should I use Investigating Pipeline?
Investigating Pipeline fits situations like: A user provides a build ID; azure DevOps build URL and wants to understand what failed and why.
How do I install Investigating Pipeline in Claude Code?
Run `npx skills add dotnet/docker-tools --skill investigating-pipeline -a claude-code`. Or copy the skill folder (.github/skills/investigating-pipeline in dotnet/docker-tools) into .claude/skills/investigating-pipeline in your project. Claude Code loads it when a task matches its description.
How do I install Investigating Pipeline in Codex?
Run `npx skills add dotnet/docker-tools --skill investigating-pipeline -a codex`. Or copy the skill folder (.github/skills/investigating-pipeline in dotnet/docker-tools) into .agents/skills/investigating-pipeline in your project. Codex loads it when a task matches its description.
Can I use Investigating Pipeline 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 dotnet/docker-tools --skill investigating-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-pipeline, .gemini/skills/investigating-pipeline, .github/skills/investigating-pipeline and .opencode/skills/investigating-pipeline in your project.
What does Investigating Pipeline need to run?
Going by SKILL.md and its folder, Investigating Pipeline needs the command-line tools its instructions call (pwsh). Our summary lists: Docker.
Does Investigating Pipeline access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Investigating Pipeline 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. Review the folder before installing.
What licence does Investigating Pipeline use?
Investigating Pipeline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Investigating Pipeline use?
About 259 tokens (SKILL.md is roughly 1k 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 Investigating Pipeline?
Skills that share tags, products or a category with Investigating Pipeline: Debate Review (amElnagdy/review-skills, 132 stars), Azdo Internal (microsoft/aspire, 6.4k stars), Component Governance Remediation (OfficeDev/microsoft-365-agents-toolkit, 780 stars) and Leanspec (codervisor/leanspec, 296 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigating Pipeline?
dotnet (a GitHub organization, an official publisher) maintains it in dotnet/docker-tools, which has 181 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.
Source: dotnet/docker-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.