Audit Aspire documentation against runtime behavior using Playwright MCP navigation and snapshots.
npx skills add https://github.com/microsoft/aspire.dev --skill doc-tester
Please help me install this Agent Skill. Skill: doc-tester Source: https://github.com/microsoft/aspire.dev/tree/main/.github/skills/doc-tester Command: npx skills add https://github.com/microsoft/aspire.dev --skill doc-tester
This skill validates Aspire documentation against actual runtime behavior by systematically auditing pages, examples, and workflows.
Follow the documented testing workflow to run this skill in a dev environment. It does not require code changes; use the MCP tools to observe site behavior and report gaps.
High-intent search queries and answers about installing and using this skill.
Documentation auditing involves verifying that pages, examples, and workflows reflect actual features and CLI behavior. It identifies discrepancies between documentation and implementation, triggering tasks for doc-writers to resolve gaps.
Yes, this documentation validation approach requires no source code inspection. Testers operate strictly from the docs using Playwright MCP navigation and snapshotting to observe site behavior, reporting gaps rather than reading implementation code.
Use Playwright MCP guided navigation to traverse Getting Started, Fundamentals, and Integrations pages. Snapshot pages, collect evidence of behavioral gaps, and report blockers explicitly to fix documentation inaccuracies.
Sandbox the testing process in a local Aspire dev setup and follow the documented workflow. Navigate the site with Playwright MCP tools, compare documented flows against reality, and explicitly flag discrepancies for doc-writers to resolve.
Yes, a local Aspire dev environment is required. The framework is sandboxed within this local setup to safely observe runtime behavior, navigate pages with MCP tooling, and collect evidence of documentation gaps.
Testing fails when docs do not match implementation because the framework enforces explicit reporting of blockers and gaps. It flags discrepancies between documented flows and actual CLI behavior, triggering necessary fixes by doc-writers.
jonnymuirAutomates UI screenshot generation for Umbraco.Prism Aspire stack documentation using Playwright and workflows.
GACLoveGenerate annual Feishu document reports summarizing counts, PV, UV, likes, and comments.
spideynoloveNavigate web pages and interact with UI elements using Playwright MCP via mcporter.
GabeujinQuery official Microsoft documentation across Learn, Aspire.dev, VS Code, and GitHub.
