Call Azure DevOps REST APIs via az devops invoke command. Use when you need to access Azure DevOps features not available in the CLI, such as work item comments, search, boards, backlogs, capacities, or any wit/work/search API endpoint. Use when the user mentions "invoke", "REST API", "API call", or needs features like comments, search, board columns, or team capacity.
/plugin marketplace add JoshuaRamirez/ms-ado-az-claude-code-plugin/plugin install ado-work-items@ms-ado-azThis skill inherits all available tools. When active, it can use any tool Claude has access to.
--in-file requires actual file path - Does NOT accept stdin (-):
# WRONG - will fail:
echo '{}' | az devops invoke --in-file -
# CORRECT:
echo '{"searchText": "query"}' > /tmp/request.json
az devops invoke --in-file /tmp/request.json
Comments API doesn't work via invoke - Use --discussion on update instead:
# WRONG - returns 404:
az devops invoke --area wit --resource comments --route-parameters workItemId=123
# CORRECT - add comment via update:
az boards work-item update --id 123 --discussion "My comment" -o json
Route parameters must match exactly - Missing or extra params cause KeyError
az devops invoke \
--area {AREA} \
--resource {RESOURCE} \
--route-parameters {key}={value} \
--http-method {GET|POST|PUT|PATCH|DELETE} \
--in-file {file.json} \
--api-version {VERSION} \
-o json
Create search payload:
echo '{"searchText": "pipeline", "$top": 10}' > /tmp/search.json
Execute search:
az devops invoke \
--area search \
--resource workitemsearchresults \
--http-method POST \
--in-file /tmp/search.json \
--api-version 7.0 \
-o json
With JMESPath query for clean output:
az devops invoke \
--area search \
--resource workitemsearchresults \
--http-method POST \
--in-file /tmp/search.json \
--api-version 7.0 \
--query "results[].{id:fields.\"system.id\", title:fields.\"system.title\", state:fields.\"system.state\"}" \
-o table
az devops invoke \
--area work \
--resource boards \
--route-parameters project=ProjectName team="TeamName" \
--api-version 7.0 \
-o json
az devops invoke \
--area work \
--resource columns \
--route-parameters project=ProjectName team="TeamName" board=Features \
--api-version 7.0 \
-o json
az devops invoke \
--area work \
--resource backlogs \
--route-parameters project=ProjectName team="TeamName" \
--api-version 7.0 \
-o json
az devops invoke \
--area work \
--resource capacities \
--route-parameters project=ProjectName team="TeamName" iterationId={GUID} \
--api-version 7.0 \
-o json
| Resource | Route Parameters | Verified |
|---|---|---|
| boards | project, team | YES |
| columns | project, team, board | YES |
| backlogs | project, team | YES |
| capacities | project, team, iterationId | - |
| teamdaysoff | project, team, iterationId | - |
| Resource | Method | Verified |
|---|---|---|
| workitemsearchresults | POST | YES |
| Resource | Note |
|---|---|
| comments | NOT WORKING via invoke - use az boards work-item update --discussion instead |
To see ALL available API areas and resources:
az devops invoke -o json > api-discovery.json
This returns 214 areas with 1,407+ resources.
team="Team Name"This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.