SkillAgentSearch skills...

clone-website

Reverse-engineer and clone a website in one shot — extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website.

Install / Use

npx skills add vibeeval/vibecosystem --skill clone-website

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of clone-website

clone-website scores 87/100 on our quality scale, 2233rd of 4,714 Development & Engineering skills we index (top 48%).

Its SKILL.md is 29 KB long, well organised into 46 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 535 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-10-28 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

clone-website compared with similar skills

All 4 of these similar skills score higher than clone-website; compare them before choosing.

SkillScoreStarsUpdatedFormat
clone-website (this skill)by vibeeval875353mo agoSKILL.md
taste-skillby Leonxlnx100117.8k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install clone-website?
Run npx skills add vibeeval/vibecosystem --skill clone-website. The install tabs above show the steps for each supported agent.
Which AI agents does clone-website work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is clone-website safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is clone-website still maintained?
The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: clone-website description: Reverse-engineer and clone a website in one shot — extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website. Also triggers on phrases like "make a copy of this site", "rebuild this page", "pixel-perfect clone". Provide the target URL as an argument. argument-hint: "<url>" user-invocable: true

Clone Website

You are about to reverse-engineer and rebuild $ARGUMENTS as a pixel-perfect clone.

This is not a two-phase process (inspect then build). You are a foreman walking the job site — as you inspect each section of the page, you write a detailed specification to a file, then hand that file to a specialist builder agent with everything they need. Extraction and construction happen in parallel, but extraction is meticulous and produces auditable artifacts.

Scope Defaults

The target is whatever page $ARGUMENTS resolves to. Clone exactly what's visible at that URL. Unless the user specifies otherwise, use these defaults:

  • Fidelity level: Pixel-perfect — exact match in colors, spacing, typography, animations
  • In scope: Visual layout and styling, component structure and interactions, responsive design, mock data for demo purposes
  • Out of scope: Real backend / database, authentication, real-time features, SEO optimization, accessibility audit
  • Customization: None — pure emulation

If the user provides additional instructions (specific fidelity level, customizations, extra context), honor those over the defaults.

Pre-Flight

  1. Browser automation is required. Check for available browser MCP tools (Chrome MCP, Playwright MCP, Browserbase MCP, Puppeteer MCP, etc.). Use whichever is available — if multiple exist, prefer Chrome MCP. If none are detected, ask the user which browser tool they have and how to connect it. This skill cannot work without browser automation.
  2. Verify the target URL from $ARGUMENTS is valid and accessible via your browser MCP tool.
  3. Verify the base project builds: npm run build. The Next.js + shadcn/ui + Tailwind v4 scaffold should already be in place. If not, tell the user to set it up first.
  4. Create the output directories if they don't exist: docs/research/, docs/research/components/, docs/design-references/, scripts/.

Guiding Principles

These are the truths that separate a successful clone from a "close enough" mess. Internalize them — they should inform every decision you make.

1. Completeness Beats Speed

Every builder agent must receive everything it needs to do its job perfectly: screenshot, exact CSS values, downloaded assets with local paths, real text content, component structure. If a builder has to guess anything — a color, a font size, a padding value — you have failed at extraction. Take the extra minute to extract one more property rather than shipping an incomplete brief.

2. Small Tasks, Perfect Results

When an agent gets "build the entire features section," it glosses over details — it approximates spacing, guesses font sizes, and produces something "close enough" but clearly wrong. When it gets a single focused component with exact CSS values, it nails it every time.

Look at each section and judge its complexity. A simple banner with a heading and a button? One agent. A complex section with 3 different card variants, each with unique hover states and internal layouts? One agent per card variant plus one for the section wrapper. When in doubt, make it smaller.

Complexity budget rule: If a builder prompt exceeds ~150 lines of spec content, the section is too complex for one agent. Break it into smaller pieces. This is a mechanical check — don't override it with "but it's all related."

3. Real Content, Real Assets

Extract the actual text, images, videos, and SVGs from the live site. This is a clone, not a mockup. Use element.textContent, download every <img> and <video>, extract inline <svg> elements as React components. The only time you generate content is when something is clearly server-generated and unique per session.

Layered assets matter. A section that looks like one image is often multiple layers — a background watercolor/gradient, a foreground UI mockup PNG, an overlay icon. Inspect each container's full DOM tree and enumerate ALL <img> elements and background images within it, including absolutely-positioned overlays. Missing an overlay image makes the clone look empty even if the background is correct.

4. Foundation First

Nothing can be built until the foundation exists: global CSS with the target site's design tokens (colors, fonts, spacing), TypeScript types for the content structures, and global assets (fonts, favicons). This is sequential and non-negotiable. Everything after this can be parallel.

5. Extract How It Looks AND How It Behaves

A website is not a screenshot — it's a living thing. Elements move, change, appear, and disappear in response to scrolling, hovering, clicking, resizing, and time. If you only extract the static CSS of each element, your clone will look right in a screenshot but feel dead when someone actually uses it.

For every element, extract its appearance (exact computed CSS via getComputedStyle()) AND its behavior (what changes, what triggers the change, and how the transition happens). Not "it looks like 16px" — extract the actual computed value. Not "the nav changes on scroll" — document the exact trigger (scroll position, IntersectionObserver threshold, viewport intersection), the before and after states (both sets of CSS values), and the transition (duration, easing, CSS transition vs. JS-driven vs. CSS animation-timeline).

Examples of behaviors to watch for — these are illustrative, not exhaustive. The page may do things not on this list, and you must catch those too:

  • A navbar that shrinks, changes background, or gains a shadow after scrolling past a threshold
  • Elements that animate into view when they enter the viewport (fade-up, slide-in, stagger delays)
  • Sections that snap into place on scroll (scroll-snap-type)
  • Parallax layers that move at different rates than the scroll
  • Hover states that animate (not just change — the transition duration and easing matter)
  • Dropdowns, modals, accordions with enter/exit animations
  • Scroll-driven progress indicators or opacity transitions
  • Auto-playing carousels or cycling content
  • Dark-to-light (or any theme) transitions between page sections
  • Tabbed/pill content that cycles — buttons that switch visible card sets with transitions
  • Scroll-driven tab/accordion switching — sidebars where the active item auto-changes as content scrolls past (IntersectionObserver, NOT click handlers)
  • Smooth scroll libraries (Lenis, Locomotive Scroll) — check for .lenis class or scroll container wrappers

6. Identify the Interaction Model Before Building

This is the single most expensive mistake in cloning: building a click-based UI when the original is scroll-driven, or vice versa. Before writing any builder prompt for an interactive section, you must definitively answer: Is this section driven by clicks, scrolls, hovers, time, or some combination?

How to determine this:

  1. Don't click first. Scroll through the section slowly and observe if things change on their own as you scroll.
  2. If they do, it's scroll-driven. Extract the mechanism: IntersectionObserver, scroll-snap, position: sticky, animation-timeline, or JS scroll listeners.
  3. If nothing changes on scroll, THEN click/hover to test for click/hover-driven interactivity.
  4. Document the interaction model explicitly in the component spec: "INTERACTION MODEL: scroll-driven with IntersectionObserver" or "INTERACTION MODEL: click-to-switch with opacity transition."

A section with a sticky sidebar and scrolling content panels is fundamentally different from a tabbed interface where clicking switches content. Getting this wrong means a complete rewrite, not a CSS tweak.

7. Extract Every State, Not Just the Default

Many components have multiple visual states — a tab bar shows different cards per tab, a header looks different at scroll position 0 vs 100, a card has hover effects. You must extract ALL states, not just whatever is visible on page load.

For tabbed/stateful content:

  • Click each tab/button via browser MCP
  • Extract the content, images, and card data for EACH state
  • Record which content belongs to which state
  • Note the transition animation between states (opacity, slide, fade, etc.)

For scroll-dependent elements:

  • Capture computed styles at scroll position 0 (initial state)
  • Scroll past the trigger threshold and capture computed styles again (scrolled state)
  • Diff the two to identify exactly which CSS properties change
  • Record the transition CSS (duration, easing, properties)
  • Record the exact trigger threshold (scroll position in px, or viewport intersection ratio)

8. Spec Files Are the Source of Truth

Every component gets a specification file in docs/research/components/ BEFORE any builder is dispatched. This file is the contract between your extraction work and the builder agent. The builder receives the spec file contents inline in its prompt — the file also persists as an auditable artifact that the user (or you) can review if something looks wrong.

The spec file is not optional. It is not a nice-to-have. If you dispatch a builder without first writing a spec file, you are shipping incomplete instructions based on whatever you can remember from a browser MCP session, and the builder will guess to fill gaps.

9. Build Must Always Compile

Every builder agent must verify npx tsc --noEmit passes before finishing. After merging worktrees, you verify npm run build passes. A broken build is never acceptable, even temporarily.

Phase 1: Reconnaissance

Navigate to the target URL with browser MCP.

Screenshots

  • Take full-page screenshots at desktop (1440px) and mobile (390px) viewports
  • Save to docs/design-references/ with descriptive names
  • These are your master reference — builders will receive section-specific crops/screenshots later

Global Extraction

Extract these from the page before doing anything else:

Fonts — Inspect <link> tags for Google Fonts or self-hosted fonts. Check computed font-family on key elements (headings, body, code, labels). Document every family, weight, and style actually used. Configure them in src/app/layout.tsx using next/font/google or next/font/local.

Colors — Extract the site's color palette from computed styles across the page. Update src/app/globals.css with the target's actual colors in the :root and .dark CSS variable blocks. Map them to shadcn's token names (background, foreground, primary, muted, etc.) where they fit. Add custom properties for colors that don't map to shadcn tokens.

Favicons & Meta — Download favicons, apple-touch-icons, OG images, webmanifest to public/seo/. Update layout.tsx metadata.

Global UI patterns — Identify any site-wide CSS or JS: custom scrollbar hiding, scroll-snap on the page container, global keyframe animations, backdrop filters, gradients used as overlays, smooth scroll libraries (Lenis, Locomotive Scroll — check for .lenis, .locomotive-scroll, or custom scroll container classes). Add these to globals.css and note any libraries that need to be installed.

Mandatory Interaction Sweep

This is a dedicated pass AFTER screenshots and BEFORE anything else. Its purpose is to discover every behavior on the page — many of which are invisible in a static screenshot.

Scroll sweep: Scroll the page slowly from top to bottom via browser MCP. At each section, pause and observe:

  • Does the header change appearance? Record the scroll position where it triggers.

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars535
CategoryDevelopment
Updated3mo ago
Forks44

Languages

C#

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info
clone-website — Universal Skill: Install & Safety Check | SkillAgent