Clone Section for Openclaw

Clone Section extracts a live website section and turns its real styles and structure into code for your chosen framework or site builder.

soraiabarroso
v1.0.0
Oct 15, 2026
0
27
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install clone-section

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install clone-section using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Clone Section?

Clone Section helps developers recreate a specific part of a live website—such as a hero, pricing table, navigation bar, or footer—as usable component code. It extracts the page’s resolved CSS and returns the section’s actual colors, fonts, spacing, and copy, providing a more faithful starting point than guessing from a screenshot.

As one of the Openclaw Skills for frontend work, it supports Tailwind, React JSX, Vue, HTML, Elementor, and Shopify outputs. Use the generated code as a reference to adapt to your project’s conventions, assets, and design tokens; check licensing before republishing another site’s content.

Clone Section Use Cases

  • Rebuild a named section from a live URL, such as a hero, footer, FAQ, or pricing table.
  • Create a reference implementation when a screenshot alone is not enough to identify real styles and copy.
  • Generate React, Vue, Tailwind, or HTML code that fits the project’s existing stack.
  • Produce an importable Elementor template for WordPress or a Shopify theme section.
  • Extract a less common page block by choosing a selector from the API’s returned section list.
  • Retry client-rendered or runtime-styled pages in a browser when static extraction returns limited results.

How Clone Section Works

  1. Identify the source URL and the section the user wants. Use a supported named section or, if needed, a selector returned by the API.
  2. Choose the output format to match the user’s project: Tailwind, JSX, Vue, HTML, Elementor, or Shopify. Set a component name for JSX or Vue when appropriate.
  3. Call extract_code through connected MiroMiro tools, or call the REST API with the equivalent parameters and MIROMIRO_API_KEY authorization.
  4. Review the returned code, section metadata, design tokens, theme, and summary.styledCoverage. If the response includes a hint or coverage is low, retry with render: true to execute the page in a browser.
  5. Adapt the extracted structure to the target project, preserve the source design values where appropriate, and integrate assets, tokens, and any returned animation keyframes.
  6. Deliver the finished component or importable file, noting any theme mismatch and reminding the user to check rights before commercial reuse.

Clone Section Setup

  1. Obtain a MiroMiro API key from the onboarding page. The documented free plan includes 300 credits per month without a card; each standard extraction call costs 25 credits. Never invent or assume a key.
  2. Set the key in the environment used by the agent:
export MIROMIRO_API_KEY="your_api_key"
  1. With MiroMiro tools connected, call extract_code. For OpenClaw or another agent without those tools, use the REST API:
curl -s "https://miromiro.app/api/v1/code?url=linear.app&section=pricing&framework=tailwind" \
  -H "Authorization: Bearer $MIROMIRO_API_KEY"
  1. Replace the example URL, section, and framework with the user’s requirements. Supported named sections are hero, header, footer, pricing, features, testimonials, faq, and cta. Omit section to auto-detect the hero.
  2. For pages that need JavaScript rendering, retry with render: true; this adds 5 credits. A rendered request can also use screenshot: true or screenshot: "full" to return a rendered-page URL.
  3. For Elementor, save the complete code JSON as a .json file and import it through Templates > Saved Templates > Import. For Shopify, save the complete Liquid output as sections/<name>.liquid and add it in the theme editor—not in a Custom Liquid block.

Clone Section Data Schema & Taxonomy

  • Request inputs: page url, optional section or returned selector, framework, optional component name, optional theme, and rendering options such as render and screenshot.
  • Supported section names: hero, header, footer, pricing, features, testimonials, faq, and cta. Without a section, extraction defaults to the hero.
  • Response fields: generated code; where applicable, a css string; a sections array with labels and selectors; design tokens; a theme value; and extraction diagnostics such as summary.styledCoverage and hint.
  • Framework-specific output: JSX and Vue can represent repeated items as data arrays rendered with .map() or v-for. HTML returns markup with a companion CSS string. Elementor returns a complete template JSON in code; Shopify returns a complete Liquid section in code and uses css: null because styles are included in the file.
  • Files and integration: Elementor output is saved as .json; Shopify output belongs in sections/<name>.liquid. Tailwind, JSX, and Vue responses may include @keyframes in css; add those rules to the project’s global stylesheet or animations may not run.
  • Metadata: The skill is named clone-section, describes website-section reconstruction, and declares MIROMIRO_API_KEY as its primary environment variable. It lists the MiroMiro API as its homepage.

Clone Section Advanced Features

  • Section discovery: The API returns other extractable sections with human-readable labels and ready-to-use selectors; use these instead of guessing CSS selectors.
  • Browser-rendered extraction: Retry with render: true when JavaScript-rendered content or runtime styling limits static extraction. This costs 5 additional credits and is intended as a retry rather than the default.
  • Theme selection: Request theme: "dark" when appropriate and check the returned theme field. Sites whose theme is controlled purely by JavaScript may not support this selection.
  • Framework-aware output: Repeated JSX and Vue structures are represented as reusable templates and data; Elementor and Shopify receive complete, styled importable files.
  • Scoped styles and animations: Elementor and Shopify styles are scoped to avoid theme clashes. For Tailwind, JSX, and Vue, move any returned @keyframes into the global stylesheet.
  • Design-token handoff: Use the returned section-specific design tokens in the project theme rather than hardcoding colors when the project supports tokens.
  • Extraction diagnostics: Review summary.styledCoverage and any hint to decide whether static extraction is sufficient or a browser-rendered retry is needed.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*