reactor-devtools Skill
Driving a running Reactor app via mur devtools — screenshot, inspect visual tree, click/type/scroll, read hook state. Use when diagnosing visible bugs (layout, contrast) or verifying a UI change landed. Published by microsoft in microsoft-ui-reactor.
What is reactor-devtools Skill?
Driving a running Reactor app via mur devtools — screenshot, inspect visual tree, click/type/scroll, read hook state. Use when diagnosing visible bugs (layout, contrast) or verifying a UI change landed. Published by microsoft in microsoft-ui-reactor. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Design and media
- Security review use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use reactor-devtools Skill
- Use it for security review.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/microsoft-ui-reactor
- Skill file: plugins/reactor/skills/reactor-devtools/SKILL.md
What it does
Driving a running Reactor app via mur devtools — screenshot, inspect visual tree, click/type/scroll, read hook state. Use when diagnosing visible bugs (layout, contrast) or verifying a UI change landed.
Skill instructions
Reactor Devtools — CLI-driven UI automation The Reactor devtools let you look at a running debug-build app the way a user does (screenshots, rendered text, layout bounds) and drive it the way a user does (click, type, toggle, scroll). Always prefer the mur devtools CLI — every action composes with shell pipes and jq, each invocation is a complete audit record, and no MCP client setup is needed. Under the hood the CLI talks JSON-RPC to a loopback HTTP endpoint the app exposes. The MCP endpoint is still available at http://127.0.0.1:PORT/mcp as a parity escape hatch, but reach for it only when the CLI can't express what you need (structured args the CLI flattens, or another MCP client that's already wired up). Loopback-only — DEBUG builds only, never ship it. Auth is a per-launch bearer token written into the lockfile; the CLI applies it transparently during lockfile discovery, so you don't see it. Don't pass --endpoint for tool calls — without the token the server returns 401. --endpoin
Explore related resources
Frequently asked questions
What is reactor-devtools?
reactor-devtools is a open-source AI agent skill with Copy skill directory. Driving a running Reactor app via mur devtools — screenshot, inspect visual tree, click/type/scroll, read hook state. Use when diagnosing visible bugs (layout, contrast) or verifying a UI change landed.
Who is reactor-devtools best for?
reactor-devtools is best for reusing agent instructions, scripts, and references, security review workflows, design and media workflows.
How do I install reactor-devtools?
Install or run reactor-devtools using Copy skill directory. Check reactor-devtools for the latest setup command.
Is reactor-devtools actively maintained?
reactor-devtools may need a closer maintenance check before production use.
Auto-fetched from GitHub.
