powertoys-verification Skill
Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by bu Published by microsoft in PowerToys.
What is powertoys-verification Skill?
Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by bu Published by microsoft in PowerToys. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use powertoys-verification Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/PowerToys
- Skill file: .github/skills/powertoys-verification/SKILL.md
What it does
Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by bu
Skill instructions
When to use this skill Use this skill whenever you need to verify PowerToys behavior with the winapp CLI and emit a structured PASS / FAIL / BLOCKED verdict with evidence (UIA enumeration, log line, settings.json diff, screenshot, etc.). It runs in two scenarios that share the same drive techniques, helpers, taxonomy and report format — and differ only on what the checklist is and what bits you test: | Scenario | Trigger | Checklist source | Bits under test | |---|---|---|---| | A — Module checklist | "verify all <Module items", "sign off Color Picker" | Supplied file (references/release-checklist/<module.md) | Installed shipped artifact (read-only) | | B — PR validation | "validate PR N" (open or merged), "build it and test the fix", "verify the PRs in this release/hotfix", "sign off 0.X.Y" | Derived from each PR's description + diff | Installed shipped artifact if the code is already in the build; build + sideload if it isn't (unmerged / not-yet-released) | Step 0 for every run — pic
Explore related resources
Frequently asked questions
What is powertoys-verification?
powertoys-verification is a open-source AI agent skill with Copy skill directory. Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its.
Who is powertoys-verification best for?
powertoys-verification is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install powertoys-verification?
Install or run powertoys-verification using Copy skill directory. Check powertoys-verification for the latest setup command.
Is powertoys-verification actively maintained?
powertoys-verification may need a closer maintenance check before production use.
Auto-fetched from GitHub.
