winmd-api-search

Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).

Quality

86%

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

86%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.

A well-structured, executable skill body: clear discover/lookup workflows with copy-paste commands, a scoring table, and troubleshooting, all pointing to real bundled scripts. Minor conciseness and lookup-path sequencing tweaks would push it higher.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and tables that earn their tokens; a few soft asides ("Even on a fresh clone with no restore or build..." and the .gitignore note) could be trimmed, keeping it just below level 5.	4 / 5
Actionability	Copy-paste-ready PowerShell commands for both discover and lookup paths, with concrete -Action examples (members, enums, types, namespaces) covering the common cases — matches the fully-executable anchor.	5 / 5
Workflow Clarity	The Discover path is numbered 0–5 with an explicit low-score (<60) fallback loop (web search → return for local signatures); the Lookup path is concrete but less explicitly sequenced, leaving minor checkpoint gaps versus the level-5 anchor.	4 / 5
Progressive Disclosure	Clear overview in SKILL.md with real one-level-deep references (Update-WinMdCache.ps1, Invoke-WinMdQuery.ps1, cache-generator/) that resolve to existing files, well-signaled sections, and no nested doc references — easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

87%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.

A well-crafted description that names the domain, concrete actions, and explicit natural-language triggers covering a broad capability range. It clearly distinguishes the skill from generic document/code skills.

Dimension	Reasoning	Score
Specificity	States concrete actions — "Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values)" — but enumerates output fields rather than a broad set of distinct operations, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers both what ("Find and explore Windows desktop APIs" + "Discovers... retrieves full type details") and when (explicit "Use when..." with concrete capability triggers), matching the level-5 anchor.	5 / 5
Trigger Term Quality	Strong natural triggers via "Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc.", though it lacks the synonym/extension breadth of a level-5 example.	4 / 5
Distinctiveness Conflict Risk	The Windows-desktop-API/WinMD niche is clearly bounded with distinct capability triggers, giving minimal overlap with other skills.	5 / 5
	Total	18 / 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: .github/skills/winmd-api-search/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.