AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Boards My Work

skill-microsoft-azure-devops-skills-boards-my-work · by microsoft

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.

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-microsoft-azure-devops-skills-boards-my-work

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-microsoft-azure-devops-skills-boards-my-work)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Boards My Work? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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_projects tool.
  • 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_projects to 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_my_work_items: Get work items from Azure DevOps that are assigned to the user
  • wit_get_work_items_batch_by_ids: Get work item details in batch by their IDs. Use this tool to get detailed information about the work items retrieved by wit_my_work_items.

Fields

When using the tool wit_get_work_items_batch_by_ids, 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

  1. Check if the user has provided a project name in their request. If not, prompt the user to provide a project name.
  2. If the user still does not provide a project name, call the core_list_projects tool to get the list of projects and prompt the user to select one.
  3. Once a project name is obtained, call the wit_my_work_items tool to retrieve the work items assigned to the user for that project. Use assigned to me as the filter criteria to get the relevant work items.
  4. Extract the IDs of the retrieved work items and call the wit_get_work_items_batch_by_ids tool to get detailed information about those work items, including the default fields if the user did not specify any.
  5. Organize the retrieved work items by their work item type (System.WorkItemType) and sort them by the most recently changed date (System.ChangedDate).
  6. 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.