New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Glmv Web Replication

by zai-org in zai-org/GLM-skills

Frontend visual replication skill. An agent skill from zai-org/GLM-skills.

Apache-2.0Auto-check passedDatabases

Install Glmv Web Replication

skills CLI
$ npx skills add zai-org/GLM-skills --skill glmv-web-replication -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zai-org/GLM-skills glmv-web-replication --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zai-org/GLM-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/glmv-web-replication .claude/skills/glmv-web-replication && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
glmv-web-replication
GitHub stars
475
Token cost
~4.8k tokens
SKILL.md length
1,344 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Frontend visual replication skill. An agent skill from zai-org/GLM-skills.

  • Works in 5 steps: Initialize the project → Recursively collect pages and build the… → Generate summary outputs → …
  • Tasks that involve Database administration
  • SKILL.md covers Prerequisites, Authorization Gate (MUST…, Scope & Limitations and Core Idea, plus 2 more sections
  • Reaches angelokeirsebilck.be

What it does

Glmv Web Replication is an agent skill from zai-org/GLM-skills. Frontend visual replication skill. Explores a target website’s publicly visible pages via Playwright MCP or agent-browser, captures screenshots and layout information, then generates a static or client-side frontend replica that approximates the original’s visual appearance and page structure. This skill replicates FRONTEND PRESENTATION ONLY — it does not reproduce backend logic, server-side behavior, databases, or any non-public content. The user is responsible for ensuring they have proper authorization…

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering Database administration, Browser automation and Backend development. It works with Model Context Protocol and Playwright. The repository describes itself as: Official skills for the GLM family of models. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Database administration
  • Tasks that involve Browser automation
  • Tasks that involve Backend development

Example prompts

  • “/glmv-web-replication”

Requirements

  • Pre-approved tools (allowed-tools): Bash(glmv-web-replication:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Initialize the project
  2. Recursively collect pages and build the sitemap
  3. Generate summary outputs
  4. Frontend Visual Replication
  5. Visual Comparison & Revision

What it can do on your machine

Read from SKILL.md and the folder at commit 2ecd31c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(glmv-web-replication:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • angelokeirsebilck.be

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Glmv Web Replication loads about 4.8k tokens when it runs. Until then it costs about 202 tokens; SKILL.md has 1,344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~202
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zai-org/GLM-skills at commit 2ecd31c, republished under its Apache-2.0 licence (© zai-org). 1,344 words, ~4,756 tokens.

Download SKILL.mdSave it as .claude/skills/glmv-web-replication/SKILL.md (or your agent's skills folder).
name
glmv-web-replication
description
Frontend visual replication skill. Explores a target website’s publicly visible pages via Playwright MCP or agent-browser, captures screenshots and layout information, then generates a static or client-side frontend replica that approximates the original’s visual appearance and page structure. This skill replicates FRONTEND PRESENTATION ONLY — it does not reproduce backend logic, server-side behavior, databases, or any non-public content. The user is responsible for ensuring they have proper authorization (ownership, license, or explicit permission) before replicating any website. ⚠️ Authorization gate: Before starting, the agent MUST confirm with the user that they have the legal right to replicate the target site. If the user cannot confirm, the skill MUST refuse to proceed.
allowed-tools
Bash(glmv-web-replication:*)
read_when
When the user wants to create a frontend visual replica of a website they own or have explicit permission to replicate, When the user needs a static/HTML…

Website Frontend Visual Replication

Prerequisites

This workflow depends on either Playwright MCP or the agent-browser skill. As long as at least one of them is installed and available, the workflow can run normally. If neither is available in your environment, remind the user to install one.

Authorization Gate (MUST execute first)

Before proceeding, the agent MUST ask the user:

“Do you own this website, or do you have explicit written permission from the owner to replicate it? Unauthorized replication may violate copyright, terms of service, or applicable law.”

  • If the user confirms authorization → proceed.
  • If the user cannot confirm → STOP. Do not proceed with replication. Suggest alternatives (e.g., building an original design inspired by general layout patterns).

Scope & Limitations

This skill replicates FRONTEND VISUAL PRESENTATION only. Specifically:

IncludedNOT Included
Page layout & visual stylingBackend / server-side logic
Navigation structureDatabases & data stores
Publicly visible text & imagesAuthentication systems / sessions
CSS/design tokensAPI business logic
Client-side interaction patternsNon-public or behind-login content
Static asset files (images, fonts)Credentials, secrets, or API keys

Data handling rules:

  1. Never scrape behind a login wall. Only capture publicly accessible pages.
  2. Never collect or store credentials, API keys, session tokens, or personal data (PII).
  3. Never reproduce copyrighted content verbatim (articles, copy text) unless the user holds rights.
  4. Respect robots.txt and rate limits. If the site signals crawl restrictions, honor them.
  5. Output is for reference & mockup purposes unless the user has confirmed full rights.

Core Idea

  1. Recursively explore every public page of the target website, systematically record its visual content, client-side interaction logic, and publicly available asset files, and organize everything into a structured “website replication blueprint.” This blueprint should comprehensively include detailed information for each page, and naturally map the site’s navigation relationships through folder hierarchy. Specifically, during exploration, use nested folders to organize and record the collected page information: represent the current page as a folder, and represent all pages reachable from it as child folders. At the same time, save that page’s screenshots, component interaction records, and related asset files inside the page folder. With this structure, the final blueprint will clearly present both the content and interaction details of each page, while also implicitly reflecting the website’s overall information architecture and navigation paths.

An example blueprint folder structure:

text
blueprint/
├── _meta.md                      # Site-wide metadata
├── _sitemap.md                   # Sitemap
├── _assets/                      # Global assets (fonts, favicon, etc.)
├── home/                         # Homepage
│   ├── _page.md                  # Page blueprint (sections, components, interaction summary)
│   ├── _full.png                 # Full-page screenshot
│   ├── _scroll_00.png ~ N.png    # Scrolling screenshot sequence
│   ├── _interactions.md          # Record of all interactions
│   ├── _interactions/            # Interaction state screenshots (organized by interaction type)
│   ├── _assets/                  # Assets for this page (images, videos, etc.)
│   ├── products/                 # "Product list" reachable from homepage
│   │   ├── _page.md
│   │   ├── _full.png
│   │   ├── _scroll_00.png ~ N.png 
│   │   ├── _interactions.md
│   │   ├── _interactions/
│   │   ├── _assets/
│   │   ├── product-detail/       # "Product detail" reachable from product list
│   │   │   ├── _page.md
│   │   │   └── ...
│   │   └── category/             # "Category filter" reachable from product list
│   │       └── ...
│   ├── about/                    # "About us" reachable from homepage
│   │   └── ...
│   ├── blog/                     # "Blog" reachable from homepage
│   │   └── ...
│   └── login/                    # "Login" reachable from homepage
│       └── ...
└── _navigation_graph.md          # Site-wide navigation graph (Mermaid)
  1. After completing the blueprint construction above, build a frontend visual replica of the target website based on that blueprint, approximating the original's page-to-page navigation, visual layout, and client-side interaction patterns. This is a frontend-only reproduction and does not include backend behavior replication.

Replication Workflow

The whole process is divided into five phases: initialization → recursively collect pages and build the sitemap → generate summary outputs → frontend visual replication → visual comparison and revision.

The first three phases focus on exploration and documentation, while the final two phases focus on implementing the frontend replica based on the collected blueprint and visually verifying it. Below, the agent-browser workflow is used as an example; if using Playwright MCP, the overall process and usage are essentially the same and can be followed with the same approach.

Step 1: Initialize the project
bash
# Create the blueprint root directory
mkdir -p blueprint/_assets
# Open the browser and visit the target site
agent-browser open <target URL>
agent-browser set viewport 1920 1080
agent-browser wait --load networkidle

Write the following content into blueprint/_meta.md:

markdown
# Website Replication Blueprint
- Target website: <URL>
- Exploration date: <date>
- Viewport size: 1920×1080
Step 2: Recursively collect pages and build the sitemap

For every recursively discovered page, execute the following standard procedure:

First capture a full-page screenshot → download assets → traverse interaction states → scroll down → download assets again → traverse interaction states again → scroll down again → ... → continue until reaching the bottom of the page.

2.1: Asset download

After opening the page and waiting for it to fully load, collect all asset links on the page (images, videos, fonts, etc.) and download them into that page’s _assets/ directory whenever possible. Record all failed downloads and the reasons for failure.

2.2: Traverse interaction states

Obtain the list of interactive elements on the page, interact with all of them, capture UI changes, and record all newly discovered pages.

bash
# === Example using a product list page before any downward scrolling ===
agent-browser open <Product List URL>
agent-browser screenshot blueprint/home/products/_scroll_00.png
agent-browser wait --load networkidle
agent-browser snapshot -i 
# Suppose the output is:
# button "All" [ref=e1]                ← filter tab
# button "Electronics" [ref=e2]
# card "Product A" [ref=e3]            ← product card
# select "Sort" [ref=e4]               ← sort dropdown
# link "Home" [ref=e5]                 ← breadcrumb link
# button "Learn More" [ref=e6]         ← button inside product card
# --- Interaction 1: hover over product card ---
agent-browser hover @e3
agent-browser screenshot blueprint/home/products/_interactions/card_hover.png
# --- Interaction 2: click filter tab ---
agent-browser click @e2
agent-browser wait --load networkidle
agent-browser screenshot blueprint/home/products/_interactions/filter_electronics.png
# --- Interaction 3: change sorting ---
agent-browser select @e4 "Price: Low to High"
agent-browser wait --load networkidle
agent-browser screenshot blueprint/home/products/_interactions/sort_price_asc.png
# --- Interaction 4: click product card (triggers navigation) ---
agent-browser click @e3
agent-browser wait --load networkidle
agent-browser get url    # → /products/123
agent-browser screenshot blueprint/home/products/product-detail/_full.png --full
agent-browser back
# --- Interaction 5: click breadcrumb "Home" ---
agent-browser click @e5
agent-browser wait --load networkidle
agent-browser get url    # → /
agent-browser screenshot blueprint/home/_full.png --full
agent-browser back
# --- Interaction 6: click "Learn More" button (external navigation) ---
agent-browser click @e6
agent-browser wait --load networkidle
agent-browser get url    # → https://www.angelokeirsebilck.be/
agent-browser screenshot blueprint/home/products/_interactions/learn_more_external.png --full
agent-browser back

Write the updated sitemap into blueprint/_sitemap.md.

Write the updated page collection results into blueprint/home/products/_page.md:

markdown
# Product List Page
- URL: /products
- Source: Homepage main navigation "Products" link

## Section Structure
| No. | Section Name | Layout Pattern | Content Type |
|------|--------------|----------------|--------------|
| 1 | Page header | Full-width single column | H1 heading + descriptive text |
| 2 | Filter bar | Horizontal layout | Category tabs + sorting dropdown |
| 3 | Product grid | 3-column grid | Product cards × N |
| 4 | Pagination | Centered single column | Pagination button group |

## Screenshots
- Full page: ![Full page screenshot](./_full.png)
- Scroll sequence: ![Screen 1](./_scroll_00.png) ![Screen 2](./_scroll_01.png)

## Outbound Navigation
| Trigger Element | Trigger Method | Target | Child Folder |
|----------------|----------------|--------|--------------|
| Product card | Click | /products/:id | ./product-detail/ |
| Category tab | Click | /products/category/:slug | ./category/ |
| Breadcrumb "Home" | Click | / | (return to parent) |
| Learn More button | Click | https://www.angelokeirsebilck.be/ | None |

## Page Assets
| File | Purpose |
|------|---------|
| _assets/product-01.jpg | Product card thumbnail |
| _assets/product-02.jpg | Product card thumbnail |

Write all updated interactions into blueprint/home/products/_interactions.md:

markdown
# Product List Page - Interaction Behavior

## Interaction List
| Element | Trigger Method | Behavior | Navigation | Screenshot |
|---------|----------------|----------|------------|------------|
| Product card | hover | Card rises + shadow deepens | No | ![](./_interactions/card_hover.png) |
| Product card | click | Navigates to product detail | Yes → ./product-detail/ | — |
| Filter tab "Electronics" | click | List refreshes to electronics category | No (AJAX) | ![](./_interactions/filter_electronics.png) |
| Sort dropdown | select | Product list reorders | No (AJAX) | ![](./_interactions/sort_price_asc.png) |
| Breadcrumb "Home" | click | Navigates to homepage | Yes → ../ | — |
| Learn More button | click | Opens external link | Yes → https://www.angelokeirsebilck.be/ | — |

## State Transitions
Default list --[click filter tab]--> Filtered list
Default list --[change sorting]--> Sorted list
Product card (default) --[hover]--> Product card (hover state)
Product card --[click]--> /products/:id (navigation)
Learn More button --[click]--> External link (navigation to https://www.angelokeirsebilck.be/)
Step 3: Generate summary outputs

After all page collection is complete, generate the global summary files.

blueprint/_sitemap.md
markdown
# Sitemap
home/                          # / (homepage)
├── products/                  # /products (product list)
│   ├── product-detail/        # /products/:id (product detail)
│   └── category/              # /products/category/:slug (category)
├── about/                     # /about (about us)
├── blog/                      # /blog (blog list)
│   └── blog-post/             # /blog/:slug (blog post)
├── contact/                   # /contact (contact us)
└── login/                     # /auth/login (login)
    └── register/              # /auth/register (register)
blueprint/_navigation_graph.md
markdown
# Site-wide Navigation Graph
graph LR
    Home["home /"] -->|Nav - Products| Products["products /products"]
    Home -->|Nav - About| About["about /about"]
    Home -->|Nav - Blog| Blog["blog /blog"]
    Home -->|Header - Login| Login["login /auth/login"]
    Products -->|Card click| Detail["product-detail /products/:id"]
    Products -->|Filter tab| Category["category /products/category/:slug"]
    Blog -->|Post card| Post["blog-post /blog/:slug"]
    Login -->|Register link| Register["register /auth/register"]

## Navigation Details
| ID | Source Folder | Trigger Element | Target Folder | Navigation Type |
|----|---------------|----------------|---------------|-----------------|
| N001 | home/ | Main nav "Products" | home/products/ | Internal |
| N002 | home/ | Hero CTA button | home/products/ | Internal |
| N003 | home/products/ | Product card | home/products/product-detail/ | Internal |
| N004 | home/products/ | Category tab "Electronics" | home/products/category/ | Internal |
| N005 | home/products/ | Breadcrumb "Home" | home/ | Internal |
| N006 | home/products/ | Learn More button | External link https://www.angelokeirsebilck.be/ | External |
| ... | ... | ... | ... | ... |
Close the browser
bash
agent-browser close
Step 4: Frontend Visual Replication

After completing website exploration and blueprint generation, build a frontend visual replica based on the collected blueprint. During replication, refer to the blueprint’s page structures, visual styles, and publicly available assets, and use your preferred frontend tools and frameworks to rebuild the website’s client-side presentation. The goal is to approximate the original’s visual design and navigation — not to reproduce backend behavior or non-public functionality.

Step 5: Visual Comparison & Revision

After finishing the frontend replication, use Playwright MCP or the agent-browser skill to render both the original website and the replicated version, systematically compare them for visual consistency in layout, colors, typography, and navigation structure, verify the degree of visual approximation page by page, and make adjustments based on the comparison results.

Show full SKILL.md (535 more words)Show less

Key Rules

  1. Authorization first. Never begin replication without user confirmation of legal right to replicate.
  2. Public pages only. Only explore and capture publicly accessible pages. Do not attempt to access login-protected areas, admin panels, or authenticated endpoints.
  3. No credential/PII handling. If any captured content contains credentials, tokens, or personal data, redact or exclude it immediately.
  4. Frontend only. Never claim or attempt to replicate backend business logic, database schemas, or server-side behavior.
  5. Folders represent navigation relationships. If page A can navigate to page B, then page B should be created as a subfolder inside page A’s folder.
  6. If multiple pages can navigate to the same target page, you may skip redundant exploration of that page and create its folder only once under the most natural parent. However, all navigation sources must still be recorded in _sitemap.md, _navigation_graph.md, and the related pages’ _page.md files.
  7. Every folder must contain:
    • _page.md — page blueprint (sections, components, outbound navigation)
    • _full.png — full-page screenshot
    • _interactions.md — interaction behavior record
    • _interactions/ — directory for interaction state screenshots
    • _assets/ — page-specific assets
    • scrolling screenshot sequence _scroll_00.png ~ _scroll_N.png
  8. Screenshots must be captured from the real site. Do not describe visual information from memory; all visual details must be based on actual screenshots.
  9. Interactions must be genuinely triggered and recorded one by one, including hover, click, focus, and so on.
  10. Assets should be downloaded whenever possible. Use curl to download images, and use agent-browser eval or Playwright MCP to extract SVG source code and save it. All failed downloads must be recorded together with the reasons for failure.
  11. Record only; do not evaluate. Accurately document observed results without making quality judgments.
  12. Keep files updated in real time. After finishing exploration of each page window, update the sitemap and all related blueprint files such as _page.md and _interactions.md so the output always remains synchronized with the current exploration state.
  13. Ensure elements are visible. Before interacting with any page element, make sure the target element is within the visible viewport. Scroll the page or adjust the viewport position if necessary.
  14. Each call to agent-browser may execute only one command, such as taking a screenshot, getting the element list, or performing one interaction. Do not combine multiple commands in a single call. The consecutive commands in the example are only for illustrating the workflow; in actual execution they must be split into separate calls.
  15. If interaction with a webpage element triggers navigation to an external domain, there is no need to deeply explore or continue scraping that external page. However, you must record the key information of that external link, including the external URL, the page element that triggered the link (text/button name/selector or ref), and the trigger method (such as click). In the replicated website, the corresponding page element should preserve the same trigger method and external destination.
  16. _full.png is used to record the overall visual overview of the page, while the scrolling screenshot sequence (_scroll_00.png ~ _scroll_N.png) can record details of each segment. During website replication, both the overall information from the full-page screenshot and the detailed information from the scrolling screenshot sequence should be referenced together to ensure accurate visual reproduction and complete detail restoration.

© zai-org, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/glmv-web-replication of zai-org/GLM-skills.

Open the folder on GitHubat commit 2ecd31c

Compare with similar skills

Glmv Web Replication next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Glmv Web Replication compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Glmv Web Replication this skillzai-org/GLM-skills475—~4.8kAutomated safety check: PassApache-2.0
Web ReplicationLeoYeAI/openclaw-master-skills2.2k—~4.2kAutomated safety check: PassMIT
Sap Sac Test Automationsecondsky/sap-skills460—~4.2kAutomated safety check: PassGPL-3.0
Test Electron AppPostHog/posthog-foss721—~3kAutomated safety check: PassMIT
Cdp Connectadobe/skills195—~847Automated safety check: PassApache-2.0
Autofillinsundial-org/awesome-openclaw-skills663—~1.8kAutomated safety check: PassNone

Similar skills

  • Web Replication

    LeoYeAI/openclaw-master-skills

    Use Playwright MCP or the agent-browser skill to systematically explore all internal pages of a target website, collect screenshots, interaction logic, and assets, and output a “website replication…

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    DatabasesAuto-check passed

  • Sap Sac Test Automation

    secondsky/sap-skills

    SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows…

    460 GitHub stars~4.2k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Test Electron App

    PostHog/posthog-foss

    Official

    Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser.

    721 GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

  • Cdp Connect

    adobe/skills

    Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol).

    195 GitHub stars~847 tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Autofillin

    sundial-org/awesome-openclaw-skills

    Automated web form filling and file uploading skill with Playwright browser automation.

    663 GitHub stars~1.8k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed

  • Lightpanda

    lightpanda-io/agent-skill

    Lightpanda browser, drop-in replacement for Chrome-based browsing in any AI agent - faster and lighter for tasks without graphical rendering like data retrieval.

    101 GitHub stars~6k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from zai-org/GLM-skills

All 16 skills in this repo

  • Glmocr

    zai-org/GLM-skills

    Extract text from images using GLM-OCR API. An agent skill from zai-org/GLM-skills.

    475 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed

  • Glm Image Gen

    zai-org/GLM-skills

    Official skill for generating high-quality images from text prompts using ZhiPu GLM-Image API.

    475 GitHub stars~2.9k tokensUpdated 5 mo ago
    Auto-check passed

  • Glmocr Formula

    zai-org/GLM-skills

    Official skill for recognizing and extracting mathematical formulas from images and PDFs into LaTeX format using ZhiPu GLM-OCR API.

    475 GitHub stars~2.2k tokensUpdated 5 mo ago
    Auto-check passed

  • Glmocr Handwriting

    zai-org/GLM-skills

    Official skill for recognizing handwritten text from images using ZhiPu GLM-OCR API.

    475 GitHub stars~1.7k tokensUpdated 5 mo ago
    Auto-check passed

  • Glmocr Table

    zai-org/GLM-skills

    Official skill for recognizing and extracting tables from images and PDFs into Markdown format using ZhiPu GLM-OCR API.

    475 GitHub stars~1.7k tokensUpdated 5 mo ago
    Auto-check passed

  • Glmv Caption

    zai-org/GLM-skills

    Generate captions (descriptions) for images, videos, and documents using ZhiPu GLM-V multimodal model series.

    475 GitHub stars~2k tokensUpdated 5 mo ago
    Auto-check: notes

Works with

Categories

Questions about Glmv Web Replication

What does Glmv Web Replication do?

Frontend visual replication skill. An agent skill from zai-org/GLM-skills. Glmv Web Replication is an agent skill from zai-org/GLM-skills. Frontend visual replication skill.

When should I use Glmv Web Replication?

Glmv Web Replication fits situations like: tasks that involve Database administration; tasks that involve Browser automation; tasks that involve Backend development.

How do I install Glmv Web Replication in Claude Code?

Run `npx skills add zai-org/GLM-skills --skill glmv-web-replication -a claude-code`. Or copy the skill folder (skills/glmv-web-replication in zai-org/GLM-skills) into .claude/skills/glmv-web-replication in your project. Claude Code loads it when a task matches its description.

How do I install Glmv Web Replication in Codex?

Run `npx skills add zai-org/GLM-skills --skill glmv-web-replication -a codex`. Or copy the skill folder (skills/glmv-web-replication in zai-org/GLM-skills) into .agents/skills/glmv-web-replication in your project. Codex loads it when a task matches its description.

Can I use Glmv Web Replication in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zai-org/GLM-skills --skill glmv-web-replication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glmv-web-replication, .gemini/skills/glmv-web-replication, .github/skills/glmv-web-replication and .opencode/skills/glmv-web-replication in your project.

What does Glmv Web Replication need to run?

SKILL.md names no scripts, command-line tools or credentials: Glmv Web Replication is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(glmv-web-replication:*).

Does Glmv Web Replication access the network?

SKILL.md names 1 domain. In commands or code: angelokeirsebilck.be; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Glmv Web Replication safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Glmv Web Replication use?

Glmv Web Replication is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Glmv Web Replication use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Glmv Web Replication?

Skills that share tags, products or a category with Glmv Web Replication: Web Replication (LeoYeAI/openclaw-master-skills, 2.2k stars), Sap Sac Test Automation (secondsky/sap-skills, 460 stars), Test Electron App (PostHog/posthog-foss, 721 stars) and Cdp Connect (adobe/skills, 195 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Glmv Web Replication?

zai-org (a GitHub organization) maintains it in zai-org/GLM-skills, which has 475 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on April 15, 2026.

Source: zai-org/GLM-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.