block-inventory
Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions.
npx skills add majiayu000/claude-skill-registry --skill block-inventory-adobe-helix-website --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Block Inventory Survey and catalog available blocks to understand what authoring options exist. ## When to Use This Skill Use this skill when: - Starting a page import to understand available blocks - Planning content structure and need to know block options - An author would see a block library and choose from available options **Do NOT use this skill when:** - You already know which specific block you need - Building new blocks from scratch - Only checking if one specific block exists (use block-collection-and-party directly) ## Why This Skill Exists Real authors see a block library in their authoring tools. They think: "I want a hero section... oh, there's a Hero block!" This skill provides that same context - understanding what blocks are available BEFORE making authoring decisions. ## Related Skills - **page-import** - Top-level orchestrator - **identify-page-structure** - Invokes this skill to survey blocks (Step 2.5) - **block-collection-and-party** - This skill uses it to search Block Collection - **content-modeling** - Can reference block inventory but maintains independent judgment ## Block Inventory Workflow ### Step 1: Scan Local Project Blocks Check what blocks alrea
- When to Use This Skill
- Why This Skill Exists
- Related Skills
- Block Inventory Workflow
- Step 1: Scan Local Project Blocks
- Step 2: Search Block Collection for Common Blocks
- Step 3: Get Block Purposes
- Step 4: Consolidate Block Inventory
- Usage Example
- Key Principles
- Common Blocks Reference
- Limitations
List all local blocks ls -d blocks/*/ Search all common blocks in parallel node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js hero & node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js cards & node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js columns & node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js accordion & node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js tabs & node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js carousel & node .claude/skills/block-collection-and-party/scripts/search-block-collection-github.js quote &
What does the block-inventory skill do?
Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill block-inventory-adobe-helix-website --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.