adobe/helix-website
15 skills434 installs675 starsGitHub
Install
npx skills add https://github.com/adobe/helix-websiteSkills in this repo
1Authoring AnalysisThis skill decides the authoring approach for each content sequence when importing a page into AEM Edge Delivery Services (Adobe Helix). For every sequence it first asks whether an author could type it as default content, and only then selects a block, invoking content-modeling when the block choice is unclear. It is invoked by the page-import orchestrator and feeds its decisions into generate-import-html. A developer uses it during content migration to keep the authoring experience simple.33installs2Identify Page StructureThis skill analyzes a scraped webpage's structure for an AEM Edge Delivery Services import using a two-level hierarchy: first section boundaries, then content sequences within each section. It reads the screenshot and cleaned HTML to find visual/thematic breaks, delegates per-section analysis to page-decomposition, and surveys available blocks via block-inventory. It is invoked by the page-import orchestrator and feeds authoring-analysis. A developer uses it to understand page structure before making authoring decisions.32installs3Page DecompositionThis skill analyzes the content sequences within a single section of a scraped page for an AEM Edge Delivery Services import, describing them neutrally without assigning block names. It finds breaking points where content shifts type and returns structured sequence descriptions per section. It is invoked by identify-page-structure once per section so that later authoring decisions stay unbiased.32installs4Page ImportThis skill is the orchestrator for importing or migrating a single webpage from any URL into AEM Edge Delivery Services. It scrapes the page, identifies its structure, maps content to existing blocks following David's Model, and generates HTML for local preview, delegating each phase to specialized sub-skills. A developer uses it to convert existing or competitor pages into EDS-authorable content. It imports main body content only and skips header, navigation, and footer.31installs5Preview Importpreview-import opens imported content in a local AEM Edge Delivery Services development server and verifies it renders correctly. A developer runs it after generating import HTML to check block styling, image loading, and metadata against the original page screenshot. It is the final verification step of Adobe's page-import workflow.31installs6Scrape Webpagescrape-webpage extracts content, metadata, and images from a source webpage to prepare it for migration into AEM Edge Delivery Services. It loads the page in headless Chromium, scrolls to trigger lazy images, downloads and rewrites images to local paths, and saves cleaned HTML plus a metadata.json with document paths. A developer runs it as the first step of Adobe's page-import workflow.30installs7Building BlocksThis skill guides creating a new AEM Edge Delivery block or making significant changes to an existing one, following Content Driven Development principles. It walks through verifying prerequisites, finding similar blocks, creating block files, implementing the decorate(block) JavaScript, adding scoped CSS, testing, and documenting. A front-end developer uses it during the implementation phase of a CDD workflow to build reusable EDS blocks.29installs8Code ReviewThis skill reviews code for AEM Edge Delivery Services projects against EDS coding standards, performance requirements, and best practices. It runs in two modes: a self-review of uncommitted working-directory changes before a commit, and a full pull-request review that fetches the diff and posts findings. It checks JavaScript style, LCP/TBT performance, accessibility, and PR structure such as before/after preview URLs. A developer uses it before opening a PR or when reviewing one.29installs9Modeling ContentThis skill designs content models for AEM Edge Delivery Services blocks, defining the HTML table structure authors work with in Google Docs or SharePoint. It helps identify which of the four canonical models (Standalone, Collection, Configuration, Auto-Blocked) fits a block and how to lay out the table with semantic, predictable, reusable structure. It is usually invoked from the content-driven-development skill when creating or changing a block's author-facing structure.29installs10Block InventoryThis skill surveys the blocks available to an AEM Edge Delivery Services project, both local blocks and the public Block Collection, and catalogs each with its purpose. It gives an agent the same block-palette context a real author would see before making authoring decisions. It is invoked by identify-page-structure during a page import so later steps know which blocks exist.28installs11Generate Import HtmlThis skill generates the structured import HTML for an AEM Edge Delivery Services page from a completed authoring analysis. It creates one div per section, applies block tables and section-metadata styling, builds a page metadata block, and manages the images folder. It insists on importing every section and validating the section count against the earlier page-structure analysis. It is invoked by the page-import orchestrator as its HTML-generation step.28installs12Searching Aem Documentationsearching-aem-documentation runs a local script that searches the complete aem.live docs and blog corpus for AEM Edge Delivery Services topics. It returns ranked results with titles, snippets, and relevance scores so a developer reads only the most relevant pages with WebFetch. It saves context when a basic web search does not surface the right AEM documentation.26installs13Using The Block Collection And Block Partyusing-the-block-collection-and-block-party helps a developer find reference implementations, code snippets, and integration patterns for AEM Edge Delivery blocks. It searches Adobe's vetted Block Collection and the community-driven Block Party for existing blocks, plugins, and build tools to use as a starting point. A developer runs it while building a new block to reuse proven patterns.26installs14Testing Blockstesting-blocks guides a developer through testing code changes in AEM Edge Delivery Services projects: blocks, core scripts, and styles. It applies a value-versus-cost philosophy, recommending durable unit tests for logic and throwaway browser tests for DOM and visual validation. A developer follows it after making changes and before opening a pull request.25installs15Using Content Driven Developmentusing-content-driven-development applies a content-first development process to AEM Edge Delivery Services work. It requires identifying or creating test content before writing or modifying block code, prioritizing author-friendly content models. A developer follows it for building or changing blocks and core decoration, orchestrating the content-modeling, building-blocks, and testing-blocks skills.25installs