skill: package microsoft/skills curated subset into dockyard

Package a curated subset of agent skills from microsoft/skills into the Dockyard registry.

Source

• Repo: https://github.com/microsoft/skills
• License: MIT
• Upstream HEAD (at survey time): a2c0524 (2026-04-17)
• Skill count upstream: 177+ (explicitly too large to ingest wholesale)
• Trust signal: Microsoft org; 2.1k stars

Curation guidance

Do not package all 177 skills. Pick a high-value subset aligned with Dockyard themes. Candidates to consider:

• .github/skills/skill-creator
• .github/skills/mcp-builder
• .github/skills/kql
• .github/skills/entra-agent-id
• .github/skills/copilot-sdk
• Azure AI language SDK skills (e.g., azure-ai-agents-persistent-dotnet) — only if clearly reusable outside Azure
• README-listed named skills: cloud-solution-architect, frontend-design-review, github-issue-creator, microsoft-docs

Acceptance criteria

• Curation decision documented in the PR description
• One spec.yaml per selected skill under skills/<name>/
• spec.ref pinned to an audited upstream commit SHA
• task validate-skill passes for each
• task scan-skill findings triaged
• Single PR grouping all Microsoft skills (branch skills/microsoft)

Related repos from Microsoft also worth considering in follow-up issues: microsoft/azure-skills (56 skills), microsoft/azure-devops-skills, microsoft/power-platform-skills, microsoft/Dataverse-skills.

Part of the vendor-by-vendor sweep following #466 (Trail of Bits).

Start by reviewing the Microsoft skills repository at the pinned upstream commit and the candidate skills listed in the issue. Add one spec.yaml under skills// for each selected skill, document the curation decision in the PR, then run task validate-skill and task scan-skill for every entry; done means findings are triaged and all selected skills are grouped in the skills/microsoft branch PR.