clone-website

Clone websites into isolated worktrees with assets, CSS, and content sections.

Updated May 27, 2026
One-click install
npx skills add https://github.com/ashcabula30/NowhereToSpend --skill clone-website-ashcabula30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clone-website
Source: https://github.com/ashcabula30/NowhereToSpend/tree/main/.agents/skills/clone-website
Command: npx skills add https://github.com/ashcabula30/NowhereToSpend --skill clone-website-ashcabula30

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Reverse-engineering and cloning websites, capturing assets, CSS, and content sections into auditable, isolated worktrees for parallel construction and reproducibility.

Core Features & Use Cases

  • Pixel-accurate website clones that preserve layout, typography, and imagery.
  • Section-by-section extraction with per-site isolation and parallel task dispatch.
  • Generates auditable artifacts in docs/research and public assets for builders.

Quick Start

Clone the target URL(s) to begin extracting assets, CSS, and content into dedicated worktrees.

Frequently Asked Questions about clone-website

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clone a website exactly with CSS and assets at scale?

To clone a website exactly, this Skill reverse-engineers target URLs by extracting global styles, assets, and content sections into isolated worktrees for parallel construction and pixel-perfect fidelity.

How does parallel website cloning work for multiple URLs?

Parallel website cloning works by processing multiple target URLs independently, dispatching tasks to isolated worktrees while preserving artifacts in dedicated folders for auditable, multi-site orchestration.

Can I use browser automation to extract assets and content for a CSS clone?

Yes, you can use a browser automation layer to extract global styles, assets, and content sections, ensuring the cloned site maintains pixel-accurate layout, typography, and imagery.

What's the best way to reverse-engineer website sections into isolated worktrees?

The best way to reverse-engineer website sections is through frontmatter-driven instructions that extract content into isolated worktrees, generating auditable artifacts in docs/research and public assets folders.

Do I need frontmatter-driven instructions to reproduce website assets accurately?

Yes, frontmatter-driven instructions are required to orchestrate multi-site cloning, ensuring reproducible artifact generation and pixel-perfect fidelity across independent target URLs.