azure-devops-tickets

Create and retrieve Azure DevOps User Story work items via REST API.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill azure-devops-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-devops-tickets
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/azure-devops-tickets
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill azure-devops-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, pandoc, and includes scripts (resource) components.

What problem does it solve?

Azure DevOps users often spend time creating and tracking User Stories manually via the web UI or REST calls. This skill automates the creation and retrieval of User Stories, ensuring consistent formatting and faster turnaround.

Core Features & Use Cases

  • Create a User Story in a specified Azure DevOps project by supplying a title, a Markdown description, and Acceptance Criteria
  • Retrieve any existing User Story or work item by ID and render its key fields in a readable Markdown format
  • Use cases include logging new features, updating task tracking, and quick status checks across projects

Quick Start

Create a User Story with a title, Markdown description, and acceptance criteria, or fetch a work item by ID.

Frequently Asked Questions about azure-devops-tickets

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

FAQPage Schema
How do I create Azure DevOps user stories automatically using the REST API?

Fetching Azure DevOps work items by ID retrieves specific work item details from the REST API and renders the key fields into a readable Markdown format. This skill parses the JSON response and extracts the relevant data for quick status checks.

Do I need a PAT token to automate Azure DevOps work item retrieval?

This skill relies on jq and pandoc for processing Azure DevOps API responses. jq parses the JSON work item data from the API, while pandoc converts the HTML description fields into readable Markdown for consistent formatting.

Can I fetch existing Azure DevOps work items and render them in Markdown?

Configuring Azure DevOps REST API automation requires setting up a config.env file with your PAT token, organization name, and project name. This configuration provides the necessary authentication and routing details for the scripts to interact with the correct Azure DevOps instance.

What dependencies are needed to script Azure DevOps work item creation?

To script Azure DevOps work item creation, you need jq and pandoc installed. jq parses the JSON payloads and API responses, while pandoc converts Markdown descriptions into the HTML format required by the Azure DevOps REST API.