Static Site Cloner

v1.0.0

Static site reproduction expert - Analyze target websites and manually code their structure, visual style, and basic interactions using pure HTML/CSS/JavaScr...

0· 130·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for openlark/static-site-cloner.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Static Site Cloner" (openlark/static-site-cloner) from ClawHub.
Skill page: https://clawhub.ai/openlark/static-site-cloner
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install static-site-cloner

ClawHub CLI

Package manager switcher

npx clawhub@latest install static-site-cloner
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, SKILL.md, examples, and template all focus on producing front-end HTML/CSS/JS. There are no unrelated environment variables, binaries, or install steps requested — the resources included (examples, patterns, template) match the stated goal.
Instruction Scope
The runtime instructions explicitly call for using web_fetch to retrieve a target URL's HTML and then recreate structure/styles/interactions as pure front-end code. That stays within the stated purpose. Note: fetching arbitrary URLs can surface copyrighted, sensitive, or private content; the SKILL.md does include a copyright compliance admonition but does not enforce it. This is a behavioral/ethical risk (possible copyright/privacy issues), not an incoherence.
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. This is the lowest-risk install model and is proportionate for a documentation/templating skill.
Credentials
The skill requires no environment variables, credentials, or config paths. That is proportional to its purpose of producing front-end code and matches the SKILL.md (no hidden credential access).
Persistence & Privilege
always is false and the skill does not request any persistent system-wide configuration or modify other skills. Autonomous invocation is allowed by default but is not combined with other concerning privileges here.
Assessment
This skill is internally coherent for generating front-end clones and does not request credentials or install code. Before installing, consider these practical points: 1) Legal/ethical: reproducing the look-and-feel of an existing site can raise copyright, trademark, or terms-of-service issues — avoid copying protected text, logos, or other trademarked assets and confirm you have the right to reproduce the target. 2) Privacy: do not use the skill to fetch pages behind authentication or containing private data. 3) web_fetch behavior: verify how your platform's web_fetch handles cookies, authenticated content, and rate limits so the agent won't inadvertently access restricted resources. 4) Review generated code before use: the skill outputs runnable HTML/CSS/JS — inspect it for correctness and remove any content you don't own. If you need stricter safeguards, require human approval before the agent fetches or reproduces pages.

Like a lobster shell, security has layers — review code before you run it.

latestvk975bn7eadxv7s7pzk08p5y1hs855abh
130downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Static Site Cloner

Based on a target website URL, accurately reproduce the site's structure, visuals, and interactions using pure HTML, CSS, and JavaScript. Output only front-end code, without involving backend functionality.

Use Cases

  • User requests to "reproduce a website," "clone a website," "recreate a website," "copy a web page"
  • User provides a website URL and requests code rewrite
  • User needs to convert an existing website into pure front-end code
  • User wants to learn or understand the front-end implementation of a particular website

Workflow

1. Information Gathering

Use web_fetch to retrieve the HTML content of the target website:

web_fetch(url="target_url", extractMode="markdown")

Analyze and document:

  • Page structure (navigation, header, main content, footer)
  • Visual elements (colors, typography, spacing, shadows)
  • Interactive behaviors (clicks, hovers, animations)

2. Structure Reproduction

Write semantic HTML:

  • Use proper HTML5 tags (header, nav, main, section, article, footer)
  • Maintain DOM hierarchy consistent with the original site
  • Add clear comments explaining the function of each section

3. Style Restoration

Write CSS styles:

  • Prefer Flexbox/Grid layout
  • Implement responsive design (media queries)
  • Pay attention to pseudo-classes and transition effects (:hover, :focus, transition)
  • Use CSS variables to manage colors and spacing

4. Interaction Implementation

Use vanilla JavaScript:

  • Event listeners (addEventListener)
  • DOM manipulation (classList, style, innerHTML)
  • Animation effects (requestAnimationFrame or CSS Animation)

5. Output Specification

Generate runnable code:

project_directory/
├── index.html
├── styles/
│   └── main.css
└── scripts/
    └── main.js

Or a single-file version (inline CSS/JS).

Code Conventions

<!-- HTML: Semantic + Comments -->
<header class="site-header">
  <!-- Navigation bar -->
  <nav class="navbar">...</nav>
</header>

/* CSS: BEM Naming + CSS Variables */
:root {
  --primary-color: #3498db;
  --spacing-unit: 8px;
}

.navbar__link--active {
  color: var(--primary-color);
}

// JavaScript: Modern ES6+ Syntax
const toggleMenu = () => {
  document.body.classList.toggle('menu-open');
};

Limitations

  • Pure front-end technologies only: HTML, CSS, JavaScript (no React/Vue/jQuery)
  • No backend functionality: No database, API, or server-side rendering
  • Image placeholders: Use placeholder services (e.g., placeholder.com, picsum.photos)
  • Copyright compliance: Do not copy original site text content, trademarks, or sensitive information

References

For more detailed examples and patterns, refer to:

Comments

Loading comments...