Clone any website with pixel-perfect fidelity using an orchestrated multi-agent workflow.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwebsite-clonerExecute the skills CLI command in your project's root directory to begin installation:
Fetches website-cloner from horuz-ai/claude-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate website-cloner. Access via /website-cloner in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
10
total installs
10
this week
2
GitHub stars
0
upvotes
Run in your terminal
10
installs
10
this week
2
stars
Clone any website with pixel-perfect fidelity using an orchestrated multi-agent workflow.
This skill provides a complete system for cloning websites:
/clone-website <url> orchestrates the entire workflow┌─────────────────────────────────────────┐
│ ORCHESTRATOR (/clone-website) │
│ Delegates, doesn't code │
└─────────────────────────────────────────┘
│
┌───────────────┼───────────────┐
▼ ▼ ▼
┌─────────┐ ┌─────────┐ ┌─────────┐
│ screen- │ │ extrac- │ │ (can │
│ shotter │ │ tor │ │ parallel│
└─────────┘ └─────────┘ └─────────┘
│
▼
┌─────────────┐
│ cloner │◄────────┐
└─────────────┘ │
│ │
▼ │
┌─────────────┐ │
│ qa-reviewer │─────────┘
└─────────────┘ (loop until done)
Run /agents in Claude Code and create these 4 agents. For each, select "Generate with Claude" and provide the description.
| Agent Name | Description Summary |
|---|---|
website-screenshotter |
Captures comprehensive screenshots (full-page, sections, components, hover states) |
website-extractor |
Downloads assets to public/, extracts colors, typography, spacing, animations |
website-cloner |
Implements React component with Tailwind + motion, auto-detects project type |
website-qa-reviewer |
Pixel-by-pixel comparison, classifies issues as Critical/Major/Minor |
Detailed prompts for each agent: See references/subagents.md
Copy assets/clone-website.md to your commands folder:
# Project-level (shared via git)
cp assets/clone-website.md .claude/commands/
# Or user-level (personal)
cp assets/clone-website.md ~/.claude/commands/
Ensure Playwright MCP is configured in ~/.claude.json or .claude/settings.json:
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@anthropic-ai/mcp-playwright"]
}
}
}
/clone-website https://example.com
The orchestrator will:
.tasks/clone-{domain}/your-project/
├── public/
│ ├── images/ # Downloaded images
│ ├── videos/ # Downloaded videos
│ └── icons/ # Downloaded SVGs/icons
├── app/clone/page.tsx # React component (location varies by framework)
└── .tasks/clone-{domain}/
├── context.md # Extracted styles
├── screenshots/ # Visual references
└── review-notes.md # QA findings
| Technology | Reason |
|---|---|
| Tailwind CSS | Arbitrary values (bg-[#hex]) enable pixel-perfect color matching |
| motion | Modern, lighter alternative to framer-motion (import from "motion/react") |
| Single component | Focus on cloning, not architecture; sections divided by comments |
| Auto-detect framework | Supports Next.js, TanStack Start, Vite, etc. |
Detailed rationale: See references/tech-decisions.md
Phase-by-phase breakdown: See references/workflow.md
Edit the cloner agent's system prompt to specify a different output path.
Update project detection logic in cloner agent for additional frameworks.
Modify the slash command's Phase 5 to change max iterations (default: 5).
| Issue | Solution |
|---|---|
| Sub-agents not found | Verify names exactly match: website-screenshotter, website-extractor, website-cloner, website-qa-reviewer |
| Playwright errors | Run npm install -g @anthropic-ai/mcp-playwright |
| Assets not loading | Check public/ folder structure and image paths in component |
| Infinite loop | QA reviewer should set status; check review-notes.md for STATUS line |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
website-cloner is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for website-cloner matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: website-cloner is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in website-cloner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend website-cloner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend website-cloner for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in website-cloner — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: website-cloner is the kind of skill you can hand to a new teammate without a long onboarding doc.
website-cloner fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
website-cloner is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 64