page-decomposition

Analyze page sections to generate neutral, block-agnostic content sequence descriptions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify the internal content flow within a single page section and produce neutral descriptions that do not name or assume blocks, enabling consistent, author-friendly guidance during page import.

Core Features & Use Cases

  • Analyze a single section to uncover content sequences
  • Generate neutral, block-agnostic descriptions for each sequence
  • Output a structured representation of sequences and breaking points for downstream steps such as block-inventory and content-modeling

Use Case: During page import, this skill is invoked per section to map how content shifts between sequences, informing where blocks may be introduced later.

Quick Start

Invoke the skill for each page section during import to generate neutral sequence descriptions 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 analyze page sections to identify content sequences during an AEM Edge Delivery page import?

Page section analysis identifies content sequences within a section and produces neutral, block-agnostic descriptions. Applied per-section during page import, it determines breaking points between content patterns to inform AEM Edge Delivery authoring decisions.

What are neutral, block-agnostic descriptions and why are they needed for content sequences?

Neutral, block-agnostic descriptions map a page section's internal content flow without assuming or naming specific blocks. This enables consistent, author-friendly guidance during page import by informing where blocks may be introduced later in the workflow.

How do I map breaking points between content patterns for downstream content modeling?

Mapping breaking points involves analyzing a single page section to uncover its content sequences. The skill generates a structured representation of these sequences and breaking points, serving as direct input for downstream content-modeling and block-inventory steps.

Can I use this section analysis skill independently, or do I need downstream skills like identify-page-structure?

This section analysis skill is designed for a per-section pipeline and integrates with downstream skills such as identify-page-structure, block-inventory, and content-modeling. While it functions as a standalone analysis step, its structured outputs specifically inform those subsequent workflow stages.

Does this skill support AEM Edge Delivery workflows by generating structured section sequences?

Yes, this skill supports AEM Edge Delivery workflows by analyzing individual page sections to generate structured content sequences. It outputs neutral descriptions and breaking points that directly inform authoring decisions during the page import process.