.claude/skills/vision/SKILL.md
Smart visual analysis for websites and images using Playwright screenshots and AI vision.
npx skillsauth add khamel83/oneshot visionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Smart visual analysis that handles both websites and images.
/vision <url> [prompt]
<url> — Website URL OR direct image URL[prompt] — Optional: what to look for (default: comprehensive analysis)| URL Type | What Happens |
|----------|--------------|
| Website (https://example.com) | Playwright navigates → screenshots → analyzes |
| Image (https://.../*.png|jpg|jpeg) | Direct analysis with mcp__4_5v_mcp__analyze_image |
/vision https://example.com
→ Navigates to site, takes screenshot, analyzes layout and design
/vision https://example.com "What colors are used?"
→ Screenshots site, analyzes color palette
/vision https://mockup.png "replicate"
→ Direct image analysis for UI replication
/vision https://diagram.png "Describe the architecture"
→ Direct image analysis
/vision https://mysite.com "replicate"
Uses the replication prompt: "Describe in detail the layout structure, color style, main components, and interactive elements to facilitate code generation."
When invoked:
Detect URL type:
.png, .jpg, .jpeg (case insensitive) → imageFor images:
mcp__4_5v_mcp__analyze_image directlyFor websites:
mcp__playwright__browser_navigate with the URLmcp__playwright__browser_screenshot to capturemcp__4_5v_mcp__analyze_image on the screenshotmcp__playwright__browser_navigate — Navigate to websitesmcp__playwright__browser_screenshot — Capture screenshotsmcp__4_5v_mcp__analyze_image — AI vision analysismcp__4_5v_mcp__analyze_image MCP must be availableFor local image files, use Read tool directly:
Read: screenshots/mockup.png
development
--- name: tdd description: Test-driven development with mandatory RED-GREEN-REFACTOR cycle. Enforces writing failing tests before production code. Use when implementing new features, fixing bugs with test coverage, or when the user wants TDD discipline. Trigger keywords: tdd, test first, test driven, red green refactor, add tests, coverage, write a test, failing test. --- # /tdd — Test-Driven Development RED-GREEN-REFACTOR cycle. No production code without a failing test shown first. ## Usage
tools
Quick iterations on existing projects. Load context, ask what's next, execute in burn-down mode.
tools
Manage encrypted secrets between the master vault and projects using SOPS/Age.
documentation
Restore context from a handoff document and continue work.