How do I install the Fetch Vcpkg CI Logs skill?

Run npx skillmds@latest add microsoft/fetch-vcpkg-ci-logs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fetch Vcpkg CI Logs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fetch Vcpkg CI Logs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fetch Vcpkg CI Logs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fetch Vcpkg CI Logs?

Microsoft (@microsoft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fetch Vcpkg CI Logs by microsoft — Agent Skill

Name: Fetch Vcpkg CI Logs
Rating: 4.5 (4 reviews)
Author: Microsoft

Fetch Vcpkg CI Logs

Fetch vcpkg Azure DevOps metadata, failed-step logs, and selected artifacts. Use for acquiring CI evidence, not diagnosing or reporting regressions; use analyze-ci-failures for those tasks. Skip when supplied logs are sufficient.

Microsoft Updated Sep 10, 2026 2.7k repo stars

File contents

Fetch vcpkg CI Logs

First read and follow .\.github\skills\shared\azure-vcpkg-ci-notes.md. For endpoint shapes, artifact naming, and ZIP layout, see references/azure-devops-api.md.

Prerequisites

PowerShell with network access. The vcpkg/public Azure DevOps project is anonymously readable, so no Azure credentials are needed.
GitHub access (gh CLI or the GitHub MCP server) — required only to resolve a PR number to its head SHA and check runs.

Inputs

An Azure build URL/ID or microsoft/vcpkg PR URL/number, optionally narrowed by job ID, triplet, port, or artifact.

Workflow

Resolve the build ID from the Azure URL or the PR head SHA's check runs. Preserve jobId or j.
Fetch metadata, timeline, and artifacts in parallel.
Fetch failed-step logs first by directly invoking:
```
& '.\.github\skills\shared\Get-VcpkgAzureFailureLogs.ps1' -BuildId <id>
& '.\.github\skills\shared\Get-VcpkgAzureFailureLogs.ps1' -PrNumber <pr> [-JobId <job>]
```
Save its raw output as failed-step-logs.txt. Ensure every failed Validate version files timeline record is included; if the helper omits one, fetch its exact log.url and append the raw body.
Unless only step logs were requested, download relevant failure logs for {triplet} ZIPs from each artifact's resource.downloadUrl. Narrow by the requested job, triplet, or port; fetch other artifacts only when requested. Skip file lists for {triplet} unless asked.
Extract each ZIP into artifacts/{triplet}/. Keep only the ZIPs that were requested, and record any download or extraction failure with the artifact name and URL instead of retrying indefinitely.
Return the save location, build ID/status, Azure and PR URLs, PR title/author for PR builds, failed jobs/triplets, and errors.

Downloading Rules

Download ZIPs with Invoke-WebRequest -UseBasicParsing or curl. web_fetch cannot download binary content.
Artifacts are PipelineArtifact, not Container; use resource.downloadUrl directly. The Container API does not work for them.
Each ZIP contains one top-level folder named exactly failure logs for {triplet}, with one subdirectory per failing port.

Storage

Store evidence under the session folder provided in the environment context, never relative to the repository working directory:

{session-folder}/files/ci-failure-logs/build-{buildId}/
├── metadata.json
├── timeline.json
├── artifacts.json
├── failed-step-logs.txt
└── artifacts/{triplet}/

Prefer the narrowest sufficient scope. Record artifact names and download errors. Do not diagnose failures.

---name: fetch-vcpkg-ci-logsdescription: Fetch vcpkg Azure DevOps metadata, failed-step logs, and selected artifacts. Use for acquiring CI evidence, not diagnosing or reporting regressions; use analyze-ci-failures for those tasks. Skip when supplied logs are sufficient.---# Fetch vcpkg CI LogsFirst read and follow `.\.github\skills\shared\azure-vcpkg-ci-notes.md`. For endpoint shapes, artifactnaming, and ZIP layout, see [references/azure-devops-api.md](references/azure-devops-api.md).## Prerequisites- PowerShell with network access. The `vcpkg/public` Azure DevOps project is anonymously readable, so no Azure credentials are needed.- GitHub access (`gh` CLI or the GitHub MCP server) — required only to resolve a PR number to its head SHA and check runs.## InputsAn Azure build URL/ID or microsoft/vcpkg PR URL/number, optionally narrowed by job ID, triplet,port, or artifact.## Workflow1. Resolve the build ID from the Azure URL or the PR head SHA's check runs. Preserve `jobId` or `j`.2. Fetch metadata, timeline, and artifacts in parallel.3. Fetch failed-step logs first by directly invoking: ```powershell & '.\.github\skills\shared\Get-VcpkgAzureFailureLogs.ps1' -BuildId <id> & '.\.github\skills\shared\Get-VcpkgAzureFailureLogs.ps1' -PrNumber <pr> [-JobId <job>] ``` Save its raw output as `failed-step-logs.txt`. Ensure every failed `Validate version files` timeline record is included; if the helper omits one, fetch its exact `log.url` and append the raw body.4. Unless only step logs were requested, download relevant `failure logs for {triplet}` ZIPs from each artifact's `resource.downloadUrl`. Narrow by the requested job, triplet, or port; fetch other artifacts only when requested. Skip `file lists for {triplet}` unless asked.5. Extract each ZIP into `artifacts/{triplet}/`. Keep only the ZIPs that were requested, and record any download or extraction failure with the artifact name and URL instead of retrying indefinitely.6. Return the save location, build ID/status, Azure and PR URLs, PR title/author for PR builds, failed jobs/triplets, and errors.## Downloading Rules- Download ZIPs with `Invoke-WebRequest -UseBasicParsing` or curl. `web_fetch` **cannot** download binary content.- Artifacts are `PipelineArtifact`, not `Container`; use `resource.downloadUrl` directly. The Container API does not work for them.- Each ZIP contains one top-level folder named exactly `failure logs for {triplet}`, with one subdirectory per failing port.## StorageStore evidence under the session folder provided in the environment context, never relative to therepository working directory:```text{session-folder}/files/ci-failure-logs/build-{buildId}/├── metadata.json├── timeline.json├── artifacts.json├── failed-step-logs.txt└── artifacts/{triplet}/```Prefer the narrowest sufficient scope. Record artifact names and download errors. Do not diagnosefailures.

Frequently asked questions