block-inventory

Catalog local AEM Edge Delivery Services blocks and Block Collection examples with live URLs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and authors often lack a clear map of which content blocks are available locally and which canonical blocks exist in the Block Collection, causing inefficient content modeling and stalled migration decisions. This Skill systematically discovers and catalogs available blocks so authors and content modelers can choose existing components rather than reinventing them.

Core Features & Use Cases

  • Local block scan: Enumerates blocks present in the project's blocks directory and records names and on-code descriptions when available.
  • Block Collection discovery: Searches a curated list of common block types (hero, cards, columns, accordion, tabs, carousel, quote, fragment) and retrieves live example URLs to understand intended usage.
  • Purpose inference & consolidation: Produces a consolidated palette that pairs local availability with Block Collection alternatives and short-purpose descriptions for author-facing decisions.
  • Use case: Run prior to a page import or content migration to determine which blocks are already available and which vetted Block Collection blocks can be adopted.

Quick Start

Run a block inventory scan against the local project and Block Collection to produce a consolidated list of available blocks and their purposes.

Frequently Asked Questions about block-inventory

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

FAQPage Schema
How do I inventory available AEM blocks before a content migration?

Cataloging AEM blocks involves scanning local project directories and the Block Collection to list available blocks, matching examples with live URLs, and inferring purposes. This consolidated inventory guides content modeling and migration planning decisions.

What is the Block Collection in AEM Edge Delivery Services?

The Block Collection is a curated list of common AEM Edge Delivery Services block types including hero, cards, accordion, tabs, carousel, quote, and fragment. It provides live example URLs to help teams understand intended block usage and adopt vetted components.

Can I scan my local AEM project directory to find existing content blocks?

Yes, you can scan your local AEM project's blocks directory to enumerate available content blocks. The scan records block names and on-code descriptions when available, identifying local blocks for authoring and content modeling decisions.

How do I compare local AEM blocks against Block Collection examples?

You compare local AEM blocks against Block Collection examples by producing a consolidated palette that pairs local availability with matching Block Collection alternatives and short-purpose descriptions. This helps teams choose existing vetted components rather than reinventing them.

When should I run a block inventory scan for AEM site structure planning?

Run a block inventory scan when preparing page imports, planning site structure, or auditing authoring options in AEM Edge Delivery Services. The scan identifies local blocks and discovers common Block Collection components to inform content modeling decisions.

Does the block inventory scan trust fetched content from Block Collection example pages?

No, the block inventory scan treats fetched content from Block Collection example pages as untrusted. It visits example pages to retrieve live URLs and understand intended block usage while maintaining security precautions against untrusted content.