ado-evidence-search

Gathers Azure DevOps work items, pull requests, reviews, and pipeline evidence mapped to role priorities.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/EirikHaughom/msconnect-agent --skill ado-evidence-search-eirikhaughom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ado-evidence-search
Source: https://github.com/EirikHaughom/msconnect-agent/tree/main/.github/skills/ado-evidence-search
Command: npx skills add https://github.com/EirikHaughom/msconnect-agent --skill ado-evidence-search-eirikhaughom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing a performance review requires concrete evidence of delivered work, but Azure DevOps contributions are scattered across work items, pull requests, code reviews, commits, and pipelines, making manual collection slow and incomplete. ## Core Features & Use Cases - Multi-Pass Evidence Gathering: Searches work items, merged PRs, code reviews given, commits, pipeline runs, and sprint delivery month-by-month using ADO MCP tools with Azure CLI (az devops) as fallback. - Priority Mapping and Impact Framing: Deduplicates evidence, maps each item to core priorities and role accountabilities, and rewrites raw activity into outcome-focused impact statements. - Use Case: An engineer preparing a Microsoft Connect review confirms their ADO organization and projects, then receives a month-by-month evidence pack of shipped features, resolved critical bugs, and cross-team code reviews with source links and confidence ratings. ## Quick Start Ask the agent to search my Azure DevOps organization and confirmed projects for work items, pull requests, and code reviews from the last review period and map them to my core priorities.

Frequently Asked Questions about ado-evidence-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather Azure DevOps evidence for a performance review?

Confirm your ADO organization, projects, and identity, then run month-by-month passes over work items, pull requests, code reviews, commits, and pipelines. Each item is deduplicated, mapped to your core priorities, and framed as an impact statement with a source link.

What Azure DevOps data can be searched for work contributions?

The search covers completed work items, merged pull requests, code reviews given to others, commits, pipeline runs and deployments, and sprint delivery data. Work items are treated as the primary record with related PRs and commits linked to them.

What happens if ADO MCP tools are unavailable?

The workflow falls back to Azure CLI commands such as az boards work-item list, az repos pr list, and az pipelines runs list. If the CLI is also unavailable or unauthenticated, the gap is noted and you are asked to provide evidence manually.

Does it count lines of code or raw work item counts as impact?

No. Raw activity counts are explicitly avoided. Evidence is framed as outcomes, such as features shipped or critical bugs resolved, and automated commits, merge commits, and bot-created work items are excluded from contributions.

Why does the search run month-by-month instead of one query?

Monthly windows ensure consistent coverage across the lookback period and avoid incomplete results from large single queries. This matches the approach used in M365 evidence searches and improves reliability against API throttling.