mcpField
W
windows-release-readiness

windows-release-readiness

github.com/sylphxaiTesting & quality151 installsUpdated today
Repository

About windows-release-readiness

A skill for assessing Windows release readiness across installation, updates, integrations, and user support. It produces a readiness matrix that distinguishes release blockers from administrative polish and support improvements.

Key features

  1. 01Reviews distribution and update models
  2. 02Audits installation and OS integration
  3. 03Checks data, credentials, and uninstall
  4. 04Creates a risk-based readiness matrix

Use cases

  1. 01Preparing a Windows release
  2. 02Finding installer, update, or uninstall risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill windows-release-readiness

After installing, type/windows-release-readinessin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/windows-release-systems.md

Details

From the project README

Windows Release Readiness

Use this skill to make Windows releases install cleanly, update safely, integrate predictably, and support users across diverse environments.

Workflow

  1. Identify distribution channel, installer type, privileges, background components, data locations, update path, and support posture.
  2. Read references/windows-release-systems.md.
  3. Audit package identity, signing/reputation, install/update/uninstall, startup/services, registry/file associations, notifications, credentials, data, firewall, crash logs, and Store certification if relevant.
  4. Separate release blockers from enterprise/admin polish and support improvements.
  5. Produce a Windows readiness matrix with proof needed for each high-risk area.

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 request admin rights unless the product needs machine-wide changes.
  • Do not hide services, startup tasks, scheduled tasks, firewall rules, drivers, or background agents.
  • Do not leave credentials, sensitive logs, startup entries, or broken file associations after uninstall.

Output format

Windows context:
Distribution/update model:

Readiness matrix:
- Installer/package:
- Signing/reputation:
- OS integration:
- Data/credentials/uninstall:
- Updates/diagnostics:

Blockers:
- <blocker> -> proof required

Support diagnostics:
- <field/log/user action>

Comments

Markdown supported