plugins/web/skills/page-collect/SKILL.md
Extract structured resources (icons, metadata, text, forms, videos, social links) from any webpage using playwright-cli. Supports individual collectors via subcommands (icons, metadata, text, forms, videos, socials) or all at once. The icon collector classifies SVGs as icon/logo/image based on size and DOM context, optimizes them for EDS, and outputs to /icons/ for use with decorateIcons(). Use when migrating pages, auditing sites, or extracting assets.
npx skillsauth add adobe/skills page-collectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract structured resources from any webpage via playwright-cli.
Node 22+ required. Run playwright-cli --help for the command reference.
| Subcommand | Purpose | Output |
|------------|---------|--------|
| all | Run all collectors | collection.json, screenshot.jpg + assets |
| icons | SVGs, icon fonts, CSS icons → classified SVGs | icons/ + icons.json |
| metadata | Meta tags, OG, structured data | metadata.json |
| text | Body text, headings, word count | text.json |
| forms | Form structures, fields, actions | forms.json |
| videos | Video embeds, sources | videos.json |
| socials | Social media links | socials.json |
If CLAUDE_SKILL_DIR is set:
SCRIPT="${CLAUDE_SKILL_DIR}/scripts/page-collect.js"
Otherwise, find it:
SCRIPT="$(find ~/.claude -path "*/page-collect/scripts/page-collect.js" -type f 2>/dev/null | head -1)"
node "$SCRIPT" <subcommand> <url> [--output <dir>]
Default output: ./page-collect-output/
playwright-cli must be on PATH. Optionally pass --browser-recipe <path> to
use a browser-recipe.json from the browser-probe skill to bypass bot protection.
The icon collector extracts SVGs from multiple sources:
<svg> elements<img> tags with .svg src or data:image/svg+xml URIsbackground-image SVG data URIs<use> sprite references (resolved to standalone SVGs)| Class | Criteria | Output |
|-------|----------|--------|
| icon | ≤ 48px, inside button/link/nav | /icons/{name}.svg |
| logo | Brand area, "logo" in class/alt/src | /icons/logo.svg |
| image | > 48px, standalone | Excluded |
Icons are named from DOM context (aria-label, class, ID). When no
meaningful name can be derived, they get icon-{n} with
nameConfidence: "low" in the manifest — review these and rename.
Each icon SVG is cleaned:
currentColor (icons only, not logos)For more details, read the collectors reference in references/collectors.md.
{
"url": "https://example.com",
"icons": [
{
"name": "search",
"class": "icon",
"source": "inline-svg",
"file": "icons/search.svg",
"nameConfidence": "high",
"context": "header button Search"
}
]
}
icons.json — rename any nameConfidence: "low" icons/icons/*.svg to the EDS project's /icons/ directory:iconname: notationdecorateIcons() in aem.js handles renderingall results:Review collection.json for a full resource inventory of the page.
When used as part of a header migration:
node "$SCRIPT" icons <source-url> --output <extraction-dir>icons.json and copies SVGs to /icons/nav.plain.html uses :iconname: for tools/utility iconsprogram.md notes available iconstools
Use the run-workflow MCP to discover, compose, execute, publish, and save Adobe Firefly workflows. TRIGGER when: user asks what actions are available, what the MCP can do, how to process images/video/3D via workflow, wants to build/run/save/publish a workflow, OR pastes any workflow/batch/execution ID. BARE ID (UUID/workflowId/batchId) = INSPECT ONLY — call inspect_run, NEVER run_workflow_submit. ALWAYS call list_actions first for capability/discovery questions. DO NOT TRIGGER for direct Firefly API calls without MCP (use firefly-api-specs).
tools
Run predefined featured workflows via run-workflow MCP. TRIGGER when user names a featured workflow (retargeting, banners at scale, localization, packaging, banner advertising, etc.) or asks to run a known marketing/production workflow. Requires run-workflow MCP. ALWAYS call get_featured_workflow before compose_workflow. DO NOT TRIGGER for custom one-off workflows with no named template — use run-workflow skill.
tools
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A questions answered with their defaults. Pass --doc-scan-only to scan README.md and env.dist for outdated content without modifying any files. Use when the user wants to migrate an App Builder project from the Integration Starter Kit or Checkout Starter Kit to the App Management approach, or mentions upgrading their Adobe Commerce extension architecture.
development
Add or modify webhook interceptors in an Adobe Commerce app. Use when the user wants to intercept Commerce operations to validate input, append data, or modify behavior — before or after execution. Requires a base app initialized with commerce-app-init.