Name: publish-extension
Rating: 73.6 (1 reviews)
Author: microsoft

publish-extension

Publish your Command Palette extension to the Microsoft Store or WinGet. Use when asked to publish, distribute, release, deploy to store, create MSIX packages, submit to WinGet, set up CI/CD for releases, or automate builds with GitHub Actions.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-structured with excellent progressive disclosure, but the workflows lack explicit validation checkpoints for destructive packaging/submission operations, and executable detail is mostly offloaded to reference files.

Suggestions

Add explicit validation checkpoints to each workflow, e.g. verify the MSIX bundle installs locally and the manifest validates with 'wingetcreate validate' before submission.

Include at least one copy-paste-ready command snippet in SKILL.md (e.g. the MakeAppx bundle command or the wingetcreate submit command) so the main file is actionable without opening a reference.

Note the destructive nature of Partner Center submissions and add a 'verify build before submit' step so the feedback-loop requirement is satisfied.

Dimension	Reasoning	Score
Conciseness	The body is lean: a comparison table, numbered summaries, and prerequisites with no padding or explanation of concepts Claude already knows (no 'what is the Microsoft Store' filler). Every token earns its place.	5 / 5
Actionability	Concrete commands appear in prerequisites ('winget install Microsoft.WingetCreate') and step lists name specific tools (Inno Setup, wingetcreate), but the body delegates executable detail to references rather than providing copy-paste code in SKILL.md itself — minor gaps.	4 / 5
Workflow Clarity	Both Store and WinGet paths give clear numbered sequences, but package builds and store submissions are destructive/batch operations with no explicit validation or verification checkpoints before submission, which caps the score per the rubric's feedback-loop guidance.	3 / 5
Progressive Disclosure	SKILL.md is a clean overview with two well-signaled, one-level-deep references ([store-publishing.md], [winget-publishing.md]) that exist as real files, plus concise inline summaries — easy navigation with no nesting.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and fully answers both what the skill does and when to invoke it, with a distinct niche. It is a model example of the rubric's top anchors.

Dimension	Reasoning	Score
Specificity	Names concrete actions across two channels: 'Publish your Command Palette extension to the Microsoft Store or WinGet', 'create MSIX packages', 'submit to WinGet', 'set up CI/CD', 'automate builds with GitHub Actions' — comprehensive coverage of the publishing domain.	5 / 5
Completeness	Explicitly answers both 'what' (publishing a Command Palette extension to Store/WinGet) and 'when' via a clear 'Use when...' clause with concrete trigger phrases — matching the 5-anchor example.	5 / 5
Trigger Term Quality	The 'Use when asked to publish, distribute, release, deploy to store, create MSIX packages, submit to WinGet, set up CI/CD for releases, or automate builds with GitHub Actions' clause provides comprehensive natural-language trigger terms users would actually say.	5 / 5
Distinctiveness Conflict Risk	'Command Palette extension', 'Microsoft Store or WinGet', and 'MSIX packages' carve a clear niche with minimal overlap risk against generic packaging or store skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/PowerToys
Path: src/modules/cmdpal/ExtensionTemplate/TemplateCmdPalExtension/.github/skills/publish-extension/SKILL.md
Commit: b9c82a4

Reviewed: ~15 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.