Agent skill

Identify Page Structure

by majiayu000 in majiayu000/claude-skill-registry

Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import.

MITAuto-check passed

Install Identify Page Structure

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a claude-code

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

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry identify-page-structure --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/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analysis/identify-page-structure .claude/skills/identify-page-structure && 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/

Paste into Claude Code

Install the "identify-page-structure" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure into .claude/skills/identify-page-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "identify-page-structure", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry identify-page-structure --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analysis/identify-page-structure .agents/skills/identify-page-structure && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "identify-page-structure" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure into .agents/skills/identify-page-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "identify-page-structure", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry identify-page-structure --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analysis/identify-page-structure .cursor/skills/identify-page-structure && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "identify-page-structure" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure into .cursor/skills/identify-page-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "identify-page-structure", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/majiayu000/claude-skill-registry.git --path skills/analysis/identify-page-structure

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry identify-page-structure --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analysis/identify-page-structure .gemini/skills/identify-page-structure && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "identify-page-structure" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure into .gemini/skills/identify-page-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "identify-page-structure", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry identify-page-structure

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analysis/identify-page-structure .github/skills/identify-page-structure && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "identify-page-structure" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure into .github/skills/identify-page-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "identify-page-structure", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install majiayu000/claude-skill-registry identify-page-structure --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analysis/identify-page-structure .opencode/skills/identify-page-structure && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "identify-page-structure" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/identify-page-structure into .opencode/skills/identify-page-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "identify-page-structure", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: identify-page-structure
GitHub stars: 666
Used in: 1 other repo
Token cost: ~1.5k tokens
SKILL.md length: 501 words
Files: 2
Skills in repo: 1,273
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import.

SKILL.md covers When to Use This Skill, Prerequisites, Related Skills and Key Concepts, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Identify Page Structure is an agent skill from majiayu000/claude-skill-registry. Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import. Performs two-level analysis (sections, then sequences per section) and surveys available blocks.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).

It works with Adobe Experience Manager. The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.

Example prompts

“/identify-page-structure”

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Identify Page Structure loads about 1.5k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 501 words of instructions outside code blocks.

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

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 majiayu000/claude-skill-registry at commit 2d14a69, republished under its MIT licence (© majiayu000). 501 words, ~1,546 tokens.

Download SKILL.mdSave it as .claude/skills/identify-page-structure/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: identify-page-structure
description: Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import. Performs two-level analysis (sections, then sequences per section) and surveys available blocks.

Identify Page Structure

Analyze webpage structure using two-level hierarchy: sections, then content sequences within each section.

When to Use This Skill

Use this skill when:

You have scraped webpage output (screenshot, HTML, metadata)
Need to identify section boundaries and content sequences
Ready to understand page structure before making authoring decisions

Invoked by: page-import skill (Step 2)

Prerequisites

From scrape-webpage skill, you need:

✅ screenshot.png showing full page
✅ cleaned.html with page content
✅ metadata.json with paths

page-import - Orchestrator that invokes this skill
scrape-webpage - Provides input (screenshot, HTML)
page-decomposition - This skill invokes it for EACH section
block-inventory - This skill invokes it to survey available blocks
authoring-analysis - Uses this skill's output to make authoring decisions

Key Concepts

CRITICAL: Content follows a strict two-level hierarchy:

DOCUMENT
├── SECTION (top-level container with optional metadata)
│   ├── Content Sequence 1 (default content OR block)
│   ├── Content Sequence 2 (default content OR block)
│   └── ...
├── SECTION
│   └── Content Sequence 1
└── ...

This skill analyzes BOTH levels:

Level 1: Section boundaries (Step 2a)
Level 2: Content sequences within EACH section (Step 2b per section)

Structure Identification Workflow

Step 2a: Identify Section Boundaries (Level 1)

Examine the screenshot to find visual/thematic breaks that indicate new sections.

Visual cues for section boundaries:

Background color changes (white → grey → dark → white)
Spacing/padding changes (tight → wide → normal)
Clear horizontal breaks or dividers
Thematic content shifts

What to exclude:

Header/navigation (auto-populated)
Footer (auto-populated)
Cookie banners, popups

For each section, note:

Section number (sequential: 1, 2, 3...)
Visual style (light, dark, grey, accent)
Brief overview of what's in it

Example output:

Section 1: light background, hero content
Section 2: light background, grid of features
Section 3: grey background, article cards
Section 4: dark background, tabs

Step 2b: Analyze Content Sequences Within Each Section (Level 2)

For EACH section identified in Step 2a, analyze its internal content sequences.

What is a "content sequence"? A vertical flow of related content that will become EITHER:

Default content (headings, paragraphs, lists, inline images)
A block (structured, repeating, or interactive component)

Breaking points between sequences:

Change from default content → block
Change from block → different block
Change from block → default content

INVOKE page-decomposition skill FOR EACH SECTION to get neutral descriptions.

For each section, get:

Sequence 1: [Neutral description - NO block names yet]
Sequence 2: [Neutral description]
...

Example output:

Section 1 (light):
  - Sequence 1: Large centered heading, paragraph, two buttons
  - Sequence 2: Two images displayed side-by-side

Section 2 (light):
  - Sequence 1: Centered heading
  - Sequence 2: Grid of 8 items, each with icon and short text
  - Sequence 3: Two centered buttons

Section 3 (grey):
  - Sequence 1: Eyebrow text, heading, paragraph, button
  - Sequence 2: Four items in grid, each with image, category tag, heading, description

Section 4 (dark):
  - Sequence 1: Tab navigation with three switchable content panels

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

Step 2.5: Survey Available Blocks

STOP: Before making any authoring decisions, understand what blocks are available.

INVOKE block-inventory skill to catalog available blocks.

Why this matters: Real authors see a block library and choose from available options. You need the same context to make authentic authoring decisions following David's Model.

What this provides:

Local blocks already in project
Common Block Collection blocks that can be added
Purpose/description for each block
Live example URLs

Example output:

Available Blocks:

LOCAL BLOCKS:
- custom-banner: Special promotional banner
- testimonial-slider: Customer testimonials carousel

BLOCK COLLECTION AVAILABLE:
- hero: Large heading, text, buttons for page intro
- cards: Grid of items with images/text
- columns: Side-by-side content layout
- accordion: Expandable Q&A sections
- tabs: Switchable content panels
- carousel: Rotating image/content displays
- quote: Highlighted testimonials
- fragment: Reusable content sections

Output Format

This skill provides complete page structure:

1. Section boundaries with styling:

Section 1: light background
Section 2: light background
Section 3: grey background (#f5f5f5)
Section 4: dark background (#1a1a1a)

2. Content sequences per section (neutral descriptions):

Section 1 (light):
  - Sequence 1: Large centered heading, paragraph, two call-to-action buttons
  - Sequence 2: Two images displayed side-by-side

Section 2 (light):
  - Sequence 1: Single centered heading
  - Sequence 2: Grid of 8 items, each with icon and short text
  - Sequence 3: Two centered buttons

[Continue for all sections...]

3. Block palette:

LOCAL BLOCKS: [list]
BLOCK COLLECTION AVAILABLE: [list with purposes]

Next step: Pass these outputs to authoring-analysis skill

Key Principles

Two-level analysis is mandatory:

You MUST identify sections first (2a)
Then analyze each section's content sequences (2b)
Don't skip levels or combine them

Stay neutral at this stage:

Describe WHAT you see, not WHAT it should be
"Grid of items with images" not "Cards block"
Authoring decisions come in next skill

Block inventory before decisions:

Survey blocks BEFORE making any authoring choices
Authors see a library and choose - you need same context

Files

SKILL.md and 1 other file in skills/analysis/identify-page-structure of majiayu000/claude-skill-registry.

SKILL.md
metadata.json

Open the folder on GitHubat commit 2d14a69

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.

NeverSight/learn-skills.devdata/skills-md/adobe/helix-website/identify-page-structure

Compare with similar skills

Identify Page Structure 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.

Identify Page Structure compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Identify Page Structure this skillmajiayu000/claude-skill-registry	666	1 repos	~1.5k	Automated safety check: Pass	MIT	today
Adobe App Builder Action Scaffolderadobe/skills	196	—	~3.1k	Automated safety check: Pass	Apache-2.0	today
Sanity Migrationsanity-io/agent-toolkit	188	—	~1.4k	Automated safety check: Pass	MIT	2 days ago
Content Management Systemsgithub/awesome-copilot	40k	1 repos	~1.3k	Automated safety check: Pass	MIT	today
Snowflakeadobe/skills	196	—	~3.7k	Automated safety check: Pass	Apache-2.0	today
App Builder UI ScaffolderNeverSight/learn-skills.dev	216	1 repos	~2.2k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Adobe App Builder Action Scaffolder
adobe/skills
Scaffolds, implements, deploys and debugs Adobe Runtime actions in App Builder projects, with templates for webhooks, events, database CRUD, sequences and Asset Compute workers.
196 GitHub stars~3.1k tokensUpdated today
Backend & APIsAuto-check passed
Sanity Migration
sanity-io/agent-toolkit
Official
Plans, implements, and reviews migrations from other CMSes and content systems into Sanity.
188 GitHub stars~1.4k tokensUpdated 2 days ago
Documents & OfficeAuto-check passed
Content Management Systems
github/awesome-copilot
Official
Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and…
40k GitHub starsUsed in 1 repo~1.3k tokens
Sales & SupportAuto-check passed
Snowflake
adobe/skills
Use this when converting an AI-generated static HTML page (Stardust, Mobirise, Relume, Lovable, v0, Figma-derived, etc.) into an Edge Delivery Services page while preserving the original design and…
196 GitHub stars~3.7k tokensUpdated today
DatabasesAuto-check passed
App Builder UI Scaffolder
NeverSight/learn-skills.dev
Generates React Spectrum UI code for Adobe Experience Cloud Shell apps and AEM UI Extensions from annotated patterns.
216 GitHub starsUsed in 1 repo~2.2k tokens
Frontend & DesignAuto-check passed
Appbuilder Project Init
adobe/skills
Initialize an Adobe App Builder project end-to-end and prepare the machine to build one.
196 GitHub stars~6.4k tokensUpdated today
DevelopmentAuto-check: notes

Questions about Identify Page Structure

What does Identify Page Structure do?

Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import. Identify Page Structure is an agent skill from majiayu000/claude-skill-registry. Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import.

How do I install Identify Page Structure in Claude Code?

Run `npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a claude-code`. Or copy the skill folder (skills/analysis/identify-page-structure in majiayu000/claude-skill-registry) into .claude/skills/identify-page-structure in your project. Claude Code loads it when a task matches its description.

How do I install Identify Page Structure in Codex?

Run `npx skills add majiayu000/claude-skill-registry --skill identify-page-structure -a codex`. Or copy the skill folder (skills/analysis/identify-page-structure in majiayu000/claude-skill-registry) into .agents/skills/identify-page-structure in your project. Codex loads it when a task matches its description.

Can I use Identify Page Structure 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 majiayu000/claude-skill-registry --skill identify-page-structure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/identify-page-structure, .gemini/skills/identify-page-structure, .github/skills/identify-page-structure and .opencode/skills/identify-page-structure in your project.

What does Identify Page Structure need to run?

SKILL.md names no scripts, command-line tools or credentials: Identify Page Structure is instructions for the agent only.

Does Identify Page Structure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Identify Page Structure 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 Identify Page Structure use?

Identify Page Structure is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Identify Page Structure use?

About 1.5k tokens (SKILL.md is roughly 6.2k 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 Identify Page Structure?

Skills that share tags, products or a category with Identify Page Structure: Adobe App Builder Action Scaffolder (adobe/skills, 196 stars), Sanity Migration (sanity-io/agent-toolkit, 188 stars), Content Management Systems (github/awesome-copilot, 40k stars) and Snowflake (adobe/skills, 196 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Identify Page Structure?

majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 1,273 skills in this directory. The repository was last updated on October 7, 2026.

Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Identify Page Structure

Facts

At a glance

What it does

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Identify Page Structure

When to Use This Skill

Prerequisites

Related Skills

Key Concepts

Structure Identification Workflow

Step 2a: Identify Section Boundaries (Level 1)

Step 2b: Analyze Content Sequences Within Each Section (Level 2)

Step 2.5: Survey Available Blocks

Output Format

Key Principles

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from majiayu000/claude-skill-registry

Related

Questions about Identify Page Structure