microsoft / microsoft/win-dev-skills

Transform win-dev-skills into a true skills marketplace

Open
#126 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
442
Forks
33
Avg merge
2h 59m
Merged PRs (30d)
11

Description

Goal

Evolve microsoft/win-dev-skills from a WinUI-focused plugin into a true marketplace for anything Windows-related — additional skills and MCP servers (WinDbg, XAML tooling, diagnostics, packaging, interop, security, …) with curation and a clear contribution path.

Model this on dotnet/skills: a discoverable catalog, per-skill ownership, quality bar, and a documented "add your skill" flow.

Workstreams

  • Marketplace infra & curation — grow marketplace.json from one plugin to a multi-plugin catalog (per-skill entry, category/tags, independent versioning), keep the .claude-plugin / .agents / .codex-plugin manifests in sync, make skills discoverable, and define the curation gate: quality bar to be listed, per-skill ownership, review/deprecation process, and the release-tag pinning story.
  • Contribution path — CONTRIBUTING guide for new skills/MCP servers, skill template/scaffold, review checklist, ownership model.
  • Seed skills (tracked as sub-issues below).

Seed skills

  • #127
  • #128
  • #129

References

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the referenced dotnet/skills model, then inspect marketplace.json and the .claude-plugin, .agents, and .codex-plugin manifests. Review the existing contribution structure before defining the catalog, curation, ownership, and release-pinning requirements. Done means the marketplace supports multiple skills and a documented CONTRIBUTING flow with synchronized manifests.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.