page-decomposition

Decompose a page section into neutral content sequences with breaking points.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Royincog/cpedia --skill page-decomposition-royincog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: page-decomposition
Source: https://github.com/Royincog/cpedia/tree/main/.agents/skills/page-decomposition
Command: npx skills add https://github.com/Royincog/cpedia --skill page-decomposition-royincog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a single page section to identify content sequences and neutral descriptions, enabling non-prescriptive, authoring-friendly decomposition during page import with no bias toward blocks.

Core Features & Use Cases

  • Identify internal content sequences within a section
  • Provide neutral, non-naming descriptions of sequences
  • Output structured step-by-step sequence data for later tooling

Quick Start

Analyze the active section to identify its content sequences and breaking points.

Frequently Asked Questions about page-decomposition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a page section into content sequences during an AEM import?

To decompose page sections during an AEM import, this Skill identifies internal breaking points and outputs neutral content sequences for accurate structure understanding. It operates on individual sections to provide non-prescriptive, authoring-friendly data for downstream tooling.

What are neutral descriptions in page section analysis for Edge Delivery?

Neutral descriptions in page section analysis are non-naming, unbiased summaries of content sequences. They identify breaking points within a section without bias toward blocks, enabling accurate structure understanding and authoring-friendly decomposition during page import.

Can I use section decomposition to identify breaking points for downstream tooling?

Yes, section decomposition identifies internal breaking points within a page section and outputs structured step-by-step sequence data. This data is specifically designed for later tooling and authoring decisions during the content import process.

Do I need to identify page structure before decomposing sections?

Yes, section decomposition relies on context provided by identify-page-structure. It is configured to operate on individual sections during page import, requiring the broader page structure to be established first to accurately identify content sequences.

Why does section decomposition avoid bias toward blocks during content import?

Section decomposition avoids bias toward blocks to provide non-prescriptive, authoring-friendly output. By generating neutral descriptions of content sequences instead of block-specific structures, it enables accurate structure understanding without forcing predefined authoring decisions.

What is the best way to analyze content sequences for AEM Edge Delivery page imports?

The best way to analyze content sequences is using neutral section decomposition, which identifies internal breaking points and outputs structured sequence data. This approach provides non-prescriptive, authoring-friendly results for downstream tooling during page import.