Browser Discoverability
- 1 installs
- 74 repo stars
- Updated August 4, 2026
- sbroenne/mcp-windows
Guidance for surfacing browser automation support in an existing Windows MCP server without adding a separate browser automation model.
About
Explains how to keep browser-automation discovery compact by reusing the default semantic UI workflow and one focused browser prompt. A developer uses it when documenting browser support in the windows-mcp server.
- Reuses the default semantic UI automation workflow
- Uses one focused browser prompt and thin docs
Browser Discoverability by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,361 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sbroenne/mcp-windows --skill browser-discoverabilityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 74 |
| Last updated | August 4, 2026 |
| Repository | sbroenne/mcp-windows ↗ |
What it does
Guidance for surfacing browser automation support in an existing Windows MCP server without adding a separate browser automation model.
Files
Context
Use this when browser support already exists in the backend and the goal is to help users or LLMs discover it without adding a separate automation model.
Patterns
Reuse the default semantic workflow
Add a short browser note to the main quickstart or primary guidance surface instead of building a parallel browser-only story.
Add one focused browser prompt
Create a single prompt that covers the browser-specific gaps: launching with a URL, using ARIA labels as names, and using shortcuts for browser chrome like the address bar or tab switching.
Keep tool descriptions example-driven
Prefer tiny examples in app, ui_find, and ui_click over long prose. Mention msedge.exe or chrome.exe, visible text, and ARIA labels.
Keep docs thin
Use one short README note and one compact reference section when documentation is needed. Avoid repeating the same browser guidance across every doc surface.
Examples
WindowsAutomationPrompts.Quickstart()gets one browser sentence.WindowsAutomationPrompts.BrowserAutomation()handles URL launch, ARIA discovery, and keyboard fallback for browser chrome.- Tool descriptions mention
msedge.exelaunch and ARIA-backednamematching.
Anti-Patterns
- Duplicating full browser workflows across many prompts, resources, and docs.
- Introducing Playwright/Selenium/CDP language when the product direction is semantic UI Automation first.
- Explaining browser chrome and page-content automation as separate systems when they are mostly the same workflow plus a few shortcuts.
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71