browser-verification
Skill2 starsChanged 3 months agoMITView on GitHub
Runs end-to-end browser user journey checks, console log audits, visual inspection, and mobile responsiveness validation for VoxDesk AI.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- SWEStash/swe-workflow-skillstheir own version, first seen Nov 8, 2026
- nahid-sparktales/agent-dispatchertheir own version, first seen Sep 21, 2026
- khuynh22/agent-dev-teamtheir own version, first seen Aug 31, 2026
- markoblogo/abvx-agent-skillstheir own version, first seen Jun 14, 2026
- motao123/dev-workflow-kittheir own version, first seen Jun 13, 2026
Used with
Projects with it also use incident-response.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillincident-response
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- nahid-sparktales/agent-dispatcher★ 59same name
- markoblogo/abvx-agent-skills★ 16same name
- khuynh22/agent-dev-team★ 9same name
- motao123/dev-workflow-kit★ 1same name
- SWEStash/swe-workflow-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- database-migration-safetySkill
- demo-data-integritySkill
- github-authorship-auditSkill
- portfolio-captureSkill
- security-auditSkill
- voice-provider-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use after launching local dev server (npm run dev) or deploying to production (https://voxdesk-ai.vercel.app) to verify full interactive …
- Distinctive: line 23
Test responsive layout at 1280px (Desktop), 768px (Tablet), and 375px (Mobile).
- Very specific: line 24
Document verification results in docs/BROWSER_VERIFICATION_REPORT.md.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Browser Verification Skill
When to Use
Use after launching local dev server (npm run dev) or deploying to production (https://voxdesk-ai.vercel.app) to verify full interactive functionality.
Inputs Required
- Target application URL.
- Test user credentials.
- Verification scenarios list.
Step-by-Step Process
- Navigate to target URL (Landing page, Auth, Dashboard, Call Console, Guided Story).
- Execute user journey steps (Login -> Create Agent -> Run Demo Call -> Book Appointment -> Review Lead Score -> Check Transcript).
- Inspect browser developer console for zero unhandled runtime errors or 404 assets.
- Test responsive layout at 1280px (Desktop), 768px (Tablet), and 375px (Mobile).
- Document verification results in
docs/BROWSER_VERIFICATION_REPORT.md.
Decision Tree
- Are console errors detected or buttons unclickable?
- YES -> Fail verification -> Repair underlying UI/API logic -> Re-run check.
- NO -> Pass verification -> Generate report.
Validation Checklist
- 23+ user journey checkpoints verified.
- Zero unhandled JS exceptions in browser console.
- Guided Client Story (
/demo/story) plays smoothly within ~60 seconds.
Failure Conditions
- Dead navigation buttons, broken API responses, or unresponsive layouts.
Expected Output
Browser verification report with route status, mobile responsiveness proof, and console audit logs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.