windows

Routes Windows platform tasks to sub-skills for WinMD API search, WASAPI audio, and native interop.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill windows-jose-polanco-oxte
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: windows
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/windows
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill windows-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When working on a Windows desktop application, it is hard to know which specialized guidance applies to a given task — discovering the right Windows API, writing low-latency WASAPI audio code, or building correct C# native interop. This root skill acts as a router that directs the agent to the correct sub-skill so only the relevant instructions are loaded. ## Core Features & Use Cases - Task Routing: Matches a Windows platform task to the correct sub-skill and loads only that sub-skill's SKILL.md, conserving context budget. - WinMD API Search Sub-skill: Discovers Windows desktop APIs (camera, files, notifications, UI controls, sensors) from a local WinMD metadata cache with full type, member, and enum details. - WASAPI Development Sub-skill: Guides design, implementation, debugging, and optimization of Windows Audio Session API and Core Audio code on Windows 10/11. - Windows Native Interop Sub-skill: Covers CsWin32, P/Invoke, LibraryImport, COM, HWND, handles, and unmanaged memory for C#/.NET desktop apps. - Use Case: While building a WinUI 3 audio visualizer, ask how to capture system loopback audio; the router loads the WASAPI sub-skill, which provides format negotiation, event-driven capture, and device-change recovery guidance. ## Quick Start Ask the agent to help with a Windows platform task such as finding the right API for notifications or implementing WASAPI loopback capture, and it will load the matching sub-skill.

Frequently Asked Questions about windows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right Windows API for a feature like camera or notifications?▼

Use the winmd-api-search sub-skill, which searches a local cache of Windows Platform SDK and WinAppSDK WinMD metadata. Run Update-WinMdCache.ps1 first, then query with Invoke-WinMdQuery.ps1 using search, members, types, or enums actions.

How do I capture system audio with WASAPI on Windows 10 or 11?▼

Use the wasapi-development sub-skill, which covers endpoint loopback capture with AUDCLNT_STREAMFLAGS_LOOPBACK in shared mode, plus process loopback via ActivateAudioInterfaceAsync on Windows 10 build 20348 or later.

What is the recommended way to call Win32 APIs from C#?▼

The windows-native-interop sub-skill recommends CsWin32 as the default for Win32 calls from C#, with a minimal NativeMethods.txt. Use LibraryImport for custom native DLLs on modern .NET and WinRT projections for Windows.* APIs.

Does the WinMD API search work without restoring NuGet packages?▼

Yes, baseline coverage of the Windows Platform SDK and WinAppSDK is always available without restore or build. Additional NuGet package WinMD files require dotnet restore or a packages.config file before cache generation.

When should I use shared mode versus exclusive mode in WASAPI?▼

Prefer shared mode by default, using IAudioClient3 for low-latency shared streams on Windows 10+. Reserve exclusive mode for requirements like bit-exact output or verified latency needs that shared low-period operation cannot satisfy.