diagnostics Skill
Error handling and build-time diagnostics conventions - Result-not-panic, structured Diagnostics with stable codes, actionable help, color/JSON presentation layering, exit codes, and cold-path performance. Published by microsoft in webui.
What is diagnostics Skill?
Error handling and build-time diagnostics conventions - Result-not-panic, structured Diagnostics with stable codes, actionable help, color/JSON presentation layering, exit codes, and cold-path performance. Published by microsoft in webui. 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
- Developers using webui
Technical details
- Install or run with Copy skill directory
When to use diagnostics Skill
- Use it for developers using webui.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/webui
- Skill file: .github/skills/diagnostics/SKILL.md
What it does
Error handling and build-time diagnostics conventions - Result-not-panic, structured Diagnostics with stable codes, actionable help, color/JSON presentation layering, exit codes, and cold-path performance.
Skill instructions
Error Handling & Diagnostics Use this skill whenever you add, change, or review an error path: a build-time authoring error, a parser/handler failure, a CLI validation error, or anything surfaced to a host (FFI/WASM/Node) or a tool/agent. WebUI errors must be recoverable, actionable, and machine-consumable — for humans and AI agents alike. 1 - Never panic on recoverable input panic = "abort" in the release profile means a panic kills the process instantly — including any FFI/WASM/Node host embedding the framework. Bad template input, bad CLI input, and bad state are recoverable and must return Result, never panic!/unwrap()/expect(). | Situation | Do | |-----------|----| | Malformed template / CSS / route authored by a developer | Return Result with a structured Diagnostic (see §3). | | Missing/invalid CLI input (file, port, flag) | Return a typed CliError (see §6). | | A genuinely impossible internal state | Prefer ? with a typed error; only use unreachable!/expect with a justification
Explore related resources
Frequently asked questions
What is diagnostics?
diagnostics is a open-source AI agent skill with Copy skill directory. Error handling and build-time diagnostics conventions - Result-not-panic, structured Diagnostics with stable codes, actionable help, color/JSON presentation layering, exit codes, and cold-path performance.
Who is diagnostics best for?
diagnostics is best for reusing agent instructions, scripts, and references.
How do I install diagnostics?
Install or run diagnostics using Copy skill directory. Check diagnostics for the latest setup command.
Is diagnostics actively maintained?
diagnostics may need a closer maintenance check before production use.
Auto-fetched from GitHub.
