npx skills add https://www.modelscope.cn/skills/@gruckion/visual-verification
smithery/gruckion
visual-verification
Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.
Installation
npx skills add smithery/gruckion --skill visual-verification
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installs>- Use this skill when the user asks what information a Stripe Connect connected account must p…
25 installsUse when about to claim work is complete, fixed, or passing, before committing or creating PRs …
203.7K installsAlso in this package
Other skills from smithery/gruckion.
npx skills add smithery/gruckion
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,290 B -
docs
SUMMARY.md200 B
History
- First recorded snapshot · 0 installs
SKILL.md
Visual Verification
Verify implemented features work correctly through actual user interaction, not just automated tests.
When to Use
- After implementing any UI feature
- Before marking an issue as complete
- When acceptance criteria involve user-visible behavior
- After fixing UI bugs
Approaches
Web Applications: See [browser-verification.md](browser-verification.md) for Playwright MCP workflow.
Mobile Applications: See [mobile-verification.md](mobile-verification.md) (Coming soon)
Verification Checklist
Before marking any UI task complete:
- Dev server is running and accessible
- Feature renders without console errors
- Elements render correctly and do not incorrectly overlap
- User interactions work as expected
- Edge cases handled (empty states, loading, errors)
- Screenshot captured as evidence
What NOT to Do
- Skip visual verification because "tests pass"
- Mark issues complete without browser testing
- Assume dev mode catches all errors (run
npm run buildtoo) - Test only happy paths