mcpField
M
microsoft-store-readiness

microsoft-store-readiness

github.com/sylphxaiDevelopment150 installsUpdated today
Repository

About microsoft-store-readiness

A skill for reviewing Windows apps before Microsoft Store submission. It structures readiness checks into a submission matrix, blockers, reviewer notes, telemetry planning, and support tasks.

Key features

  1. 01Audit package identity and capabilities
  2. 02Review listing, privacy, and monetization
  3. 03Check certification and rollout readiness
  4. 04Create blockers and reviewer notes
  5. 05Plan telemetry and support checklists

Use cases

  1. 01Assess a Windows app before Store submission
  2. 02Identify package or listing gaps
  3. 03Prepare reviewer notes and support plans

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill microsoft-store-readiness

After installing, type/microsoft-store-readinessin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/microsoft-store-systems.md

Details

From the project README

Microsoft Store Readiness

Use this skill to reduce Microsoft Store submission risk and make Windows distribution supportable.

Workflow

  1. Identify app type, package model, Store category, monetization, capabilities, supported devices, and Windows integration.
  2. Read references/microsoft-store-systems.md.
  3. Audit package identity, manifest capabilities, listing assets, privacy/support, monetization, quality, certification, rollout, and support readiness.
  4. Separate Store-specific requirements from general Windows release readiness.
  5. Produce a submission matrix, blockers, reviewer notes, telemetry plan, and support checklist.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not claim Store features, device support, privacy behavior, or in-app purchase support that the build does not implement.
  • Do not hide background tasks, restricted capabilities, or external payment flows from review notes.
  • Verify current Microsoft Store policies before submission; this skill is product readiness guidance, not policy/legal advice.

Output format

Microsoft Store context:
Package/monetization model:

Submission matrix:
- package identity:
- listing/assets:
- capabilities/privacy:
- monetization:
- quality/certification:
- rollout/support:

P0 blockers:
- <blocker> -> evidence needed

Reviewer notes:
- <note>

Comments

Markdown supported