boards-my-work
This skill retrieves and displays work items assigned to the user in Azure DevOps, organized by type and sorted by recently changed. It prompts for a project name or lists available projects if not provided, then fetches work item details and displays them in a formatted table with clickable links.
- Installs
- 113
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/microsoft/azure-devops-skills --skill boards-my-work- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads boards-my-work automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Get my work items
Before getting work items, you need to know which project to use.
- If the user provides a project name in their request (for example, "for Contoso"), use that project directly and do not call the
core_list_projectstool. - If a project name is not provided, first return a prompt asking the user for the project name.
- If the project name is still not provided after prompting the user, then call the MCP Server tool
core_list_projectsto get the list of projects the user can choose from. - Do not continue if the user has not provided a project name or selected one from the list.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
core_list_projects: Get the list of projects the user can choose from.wit_work_item(action:my): Get work items from Azure DevOps that are assigned to the userwit_work_item(action:get_batch): Get work item details in batch by their IDs. Use this tool to get detailed information about the work items retrieved bywit_work_itemwith actionmy.
Fields
When using the tool wit_work_item with action get_batch, if the user does not provide a list of fields to retrieve, use the following default fields:
- System.Id
- System.Title
- System.State
- System.AssignedTo
- System.WorkItemType
- System.CreatedDate
- System.ChangedDate
- System.Tags
- Microsoft.VSTS.Common.Priority
Display results
When displaying the results...
- show the work item ID (make this clickable hyperlink to open the work item in a web browser. Format should be like this: {ID}),
- title
- state,
- priority
in a table format. Show the most recently changed work items first and group the work items by thier work item type (System.WorkItemType). For example, group the work items into the following categories based on their work item type:
Epics Features Stories Bugs Tasks Test Cases other work item types
Steps
- Check if the user has provided a project name in their request. If not, prompt the user to provide a project name.
- If the user still does not provide a project name, call the
core_list_projectstool to get the list of projects and prompt the user to select one. - Once a project name is obtained, call the
wit_work_itemtool with actionmyto retrieve the work items assigned to the user for that project. Useassigned to meas the filter criteria to get the relevant work items. - Extract the IDs of the retrieved work items and call the
wit_work_itemtool with actionget_batchto get detailed information about those work items, including the default fields if the user did not specify any. - Organize the retrieved work items by their work item type (System.WorkItemType) and sort them by the most recently changed date (System.ChangedDate).
- Display the work items in a table format, showing the ID (as a clickable hyperlink), title, state, and priority for each work item, grouped by their work item type.
FAQ
What does the boards-my-work skill do?
This skill retrieves and displays work items assigned to the user in Azure DevOps, organized by type and sorted by recently changed. It prompts for a project name or lists available projects if not provided, then fetches work item details and displays them in a formatted table with clickable links.
How do I install boards-my-work?
Run npx skills add https://github.com/microsoft/azure-devops-skills --skill boards-my-work in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/boards-my-work/ (personal) or .claude/skills/boards-my-work/ (project).
Which AI agents can use boards-my-work?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is boards-my-work safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains boards-my-work?
It is published by microsoft in microsoft/azure-devops-skills, and it is an official skill from the maker of the technology it covers. It has 113 recorded installs.
More from microsoft/azure-devops-skills
pipelines-build-summary
microsoft/azure-devops-skills
List, inspect, and troubleshoot Azure DevOps pipeline builds. Shows recent builds for a pipeline definition, drills into a specific build's status and result, displays logs for failed steps, and lists the changes associated with a build.
boards-work-item-summary
microsoft/azure-devops-skills
Open the skill to read its SKILL.md instructions.
work-iterations
microsoft/azure-devops-skills
List, create, and assign iterations for Azure DevOps projects and teams.
security-alert-review
microsoft/azure-devops-skills
List and review Advanced Security alerts for an Azure DevOps repository. Shows dependency vulnerabilities, secret exposure, and code scanning findings with filtering by severity, state, and alert type.
skill-name
microsoft/azure-devops-skills
Description of what the skill does and when to use it
boards-backlog-summary
microsoft/azure-devops-skills
Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.