Skill Name
Scaffold a new Azure DevOps–style agent skill from Microsoft's placeholder SKILL.md before you replace generic instructions with real workflows.
Overview
skill-name is an agent skill for the Build phase that provides a blank Microsoft-style SKILL.md template for authoring custom skills in the azure-devops-skills pack.
Install
npx skills add https://github.com/microsoft/azure-devops-skills --skill skill-nameWhat is this skill?
- Minimal SKILL.md skeleton with name, description, and instructions section placeholders
- Matches Microsoft azure-devops-skills repo layout for custom skill additions
- Intended starting point before domain-specific Azure DevOps guidance is written
- No bundled commands, MCP hooks, or Azure API steps in the stub body
Adoption & trust: 27 installs on skills.sh; 23 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want to add a skill to a Microsoft skills repo but only have an empty instructions file with no structure to follow.
Who is it for?
Maintainers forking azure-devops-skills who need the canonical empty skill file pattern.
Skip if: Builders seeking ready-made Azure Pipelines, board automation, or issue triage without writing their own instructions first.
When should I use this skill?
When authoring a new skill file in the azure-devops-skills repository and you need the default placeholder layout.
What do I get? / Deliverables
You get a consistent SKILL.md shell you can edit into a real Azure DevOps or workflow skill before publishing to your agent.
- Edited SKILL.md with real instructions replacing the stub
Recommended Skills
Journey fit
Authoring and packaging agent skills sits in Build under agent-tooling as the default shelf for skill templates. The file is literally a name/description/instructions stub for skill creators—not a runtime DevOps automation.
How it compares
Meta authoring stub—not a workflow skill like github-issue-creator or a security index like owasp-mcp.
Common Questions / FAQ
Who is skill-name for?
Skill authors extending Microsoft's azure-devops-skills collection who need the default template file before filling in behavior.
When should I use skill-name?
At the start of Build/agent-tooling when you create a new skill slug and want the repo's placeholder structure—not during Ship or Launch.
Is skill-name safe to install?
The stub has no commands or network behavior by itself; still review the Security Audits panel on this Prism page for the parent repository.
SKILL.md
READMESKILL.md - Skill Name
# Skill Instructions Your detailed instructions, guidelines, and examples go here...