Overview Benchmark Contents Activity Versions 1 Ratings 0
See it in action One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Prompt Provide a complete empty template of the required status update response format for site quality auditing tasks.
What was checked, without and with the skill Checked Without skill With skill Includes the keys status, plan, actions_taken, verification, and remaining. Missed Passed
Show both answers
What's inside The instructions your model reads when the skill loads.
SKILL.md 99 lines single file
webhint for Browser-Facing Frontends in .NET Repositories
Trigger On
the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality
the repo has .hintrc, hint scripts, or a served local frontend that should be audited
the team needs more than syntax linting and wants runtime-oriented site checks
Do Not Use For
JavaScript or TypeScript semantic linting; route that to eslint or biome
stylesheet-only linting; route that to stylelint
static HTML structure checks alone; route that to htmlhint
Inputs
the nearest AGENTS.md
package.json
.hintrc if present
the real audit target: local dev URL, preview URL, deployed URL, or built output
Workflow
Choose the audit surface deliberately:
running local URL such as https://localhost:3000
preview or deployed URL
local connector against built output when no browser runtime is needed
Prefer repo-local installation and a checked-in .hintrc.
Start from a documented preset such as web-recommended, then customize only for real repo requirements.
Add repeatable scripts to package.json, for example:
hint https://localhost:3000
hint https://example.test --config .hintrc
Keep runtime prerequisites explicit:
supported Node.js version
browser availability when the connector needs Chromium-based automation
Treat findings as categorized work:
headers and transport
accessibility and HTML issues
performance
PWA and manifest signals
When it activates Automatically, when a task matches.
Use when a repo needs CLI audits for accessibility, performance, security headers, PWA signals, SEO, or runtime page quality against a. USE FOR: the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality; the repo has .hintrc, hint scripts, or a. DO NOT USE FOR: JavaScript or TypeScript semantic linting; route that to eslint or biome; stylesheet-only linting;
Track record Benchmark 17 / 20
test cases passed, vs 13 / 20 without
Adoption
Users 2
Times used 34 View activity → Safety and source details
SkillSafety ✓ 3 of 3 passed ✓ Code scan 15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026
View 15 scanner checks live_secret remote_code_execution reverse_shell data_exfiltration ssrf_metadata agent_snooping anti_refusal destructive_commands obfuscated_unicode unicode_homoglyph opaque_blob suspicious_url tool_overreach trigger_abuse prompt_injection_phrasing
✓ Intent Safe
LLM judge · does the skill do what it claims
✓ Content Clean
LLM judge · policy & harmful-content review
Source Imported managedcode / dotnet-skills
catalog/Tools/webhint/skills/webhint/SKILL.md
View on GitHub ↗ License MITImported 8/3/2026Version v1