Scrape Analyze Page
Extract structured data (all available fields with values) from a page saved locally as an HTML file, optionally following a schema. Do not invoke when the user provides a URL. When invoking, pass the user's full request verbatim as args — do not pre-parse file paths and don't rephrase it.
Install
/plugin marketplace add zytedata/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add zytedata/claude-skills --skill scrape-analyze-pagegit clone --depth 1 https://github.com/zytedata/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/scrape-analyze-page ~/.claude/skills/scrape-analyze-pagePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
This file is 133 lines long; read all of them.
You are extracting structured data from a page. Given saved HTML, identify all available fields and extract their values.
## Input
This is the user prompt: `$ARGUMENTS`. You need to extract the following information from it:
1. Path to the saved HTML file, e.g. `product1.html`. This is what you need to analyze. Don't proceed if it's not provided.
2. Path to output file, e.g. `product1.json`. When provided, this is where you will save the structured analysis.
3. Path to data-type spec.json. When provided, guides extraction using schema field names, descriptions, and examples.
4. Whether to strictly extract only the fields listed in the schema, if the schema was provided. When asked for strict extraction, extract only schema fields — no extras.
5. `--list-mode`: when present, the page is a listing page. Extract ALL repeated item instances (e.g., every product card) as an array rather than a single-item object.
## Process
### 1. Clean and read the page
**Only process this one page.** Do not read or compare with other pages' analysis files.
`.scrape/.work/` is shared with the orchestrator and other concurrently
running agents. Never delete or "clean up" anything under it, at any point —
leave your intermediate files in place when you finish.
Clean the HTML and extract metadata, saving outputs to the work directory. Use `{page_id}.{html_variant}` as the filename base to avoid collisions:Details
- Skill name
scrape-analyze-page- Repository
- zytedata/claude-skills
- Path
skills/scrape-analyze-page/SKILL.md- Repo updated
- 26 October 2026
FAQ
What does the Scrape Analyze Page skill do?
Extract structured data (all available fields with values) from a page saved locally as an HTML file, optionally following a schema. Do not invoke when the user provides a URL. When invoking, pass the user's full request verbatim as args — do not pre-parse file paths and don't rephrase it.
How do I install the Scrape Analyze Page skill?
Claude Code plugin: /plugin marketplace add zytedata/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Scrape Analyze Page popular?
It lives in zytedata/claude-skills, which has 33 GitHub stars and 5 forks.
Related skills
Scrape
33zytedata/claude-skills
Build a full-site or multi-page Scrapy spider to get structured data from a website, in a new project or added to an existing one. Do not use for analyzing locally saved HTML, fixing or debugging an existing spider, schema-only or existing-spec work, Scrapy Cloud operations, or advisory questions.
Scrape Plan
33zytedata/claude-skills
Plan a web scrape and author a validated extraction spec — explore a detail page, discover fields, confirm the schema, then validate it with more pages, HTML-variant comparison, extracted values, and an optional browser review, and present the plan for approval.
Scrapy Extra
33zytedata/claude-skills
Read this BEFORE writing, modifying, debugging, or explaining any Scrapy or web-poet code — spiders, page objects, pipelines, settings, selectors — down to a one-line fix, or scaffolding/configuring a Scrapy project, scrapy-poet, scrapy-zyte-api, or browser rendering. These libraries moved on since your training cutoff; invoke this FIRST. NOT for building a scraper for a given site (scrape), a saved HTML file (scrape-analyze-page), or Scrapy Cloud deploy/jobs (zyte).
Employment Law Dashboard
43bstevescherer/heycounsel-community
Build a single-file HTML dashboard for any area of US employment law, modeled after the AI Employment Laws Dashboard. Use this skill any time the user wants to create, build, generate, or update a dashboard, tracker, comparison page, or visual brief covering an employment-law topic across US jurisdictions. Triggers include phrases like "make a dashboard for [topic]", "build a tracker for [employment topic]", "state-by-state comparison page for [topic]", "visualize the legal landscape for [topic]", "create a dashboard like the AI one but for [topic]". The dashboard always includes a masthead, T
Add Analytics Instrumentation
48amplitude/mcp-marketplace
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature
Analytics and Er
49dynamics365ninja/d365fo-cli
Model the D365FO analytical and document-generation surfaces — aggregate measurements and the entity store, tiles/cues and KPIs, and Electronic Reporting (ER). Invoke when the user asks about a workspace tile, a KPI, an aggregate measurement, the entity store, Power BI content, or running/binding an ER format.
Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.