preview-import

Validate imported HTML rendering and assets on a local AEM Edge Delivery Services dev server.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill preview-import-adobe-summit2026-l613
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/adobe-summit2026-l613/las-vegas-events/tree/main/.skills/preview-import
Command: npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill preview-import-adobe-summit2026-l613

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Previewing newly imported content often requires manual steps and separate tooling to validate rendering against the original page. This skill streamlines that by starting a local AEM dev server and providing a guided workflow to verify assets, structure, and visuals.

Core Features & Use Cases

  • Launch and verify imported HTML in a local AEM Edge Delivery Services dev server.
  • Compare rendering against the source page using provided metadata and screenshots.
  • Troubleshoot common rendering issues with a structured checklist.

Quick Start

Start the local AEM dev server and preview the imported HTML in the correct folder to verify rendering.

Frequently Asked Questions about preview-import

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

FAQPage Schema
How do I verify imported HTML rendering on a local AEM Edge Delivery Services dev server?

To verify imported HTML rendering on a local AEM Edge Delivery Services dev server, launch the local dev environment and use a guided workflow to check assets, structure, and visuals against the original page using provided metadata and screenshots.

What is the best way to validate locally imported content against the original page?

Validating locally imported content against the original page is best done by automating preview and rendering checks, which allows you to compare visuals, verify asset loading, and ensure metadata consistency directly on your local development server.

Why are assets missing when I preview imported content on my local AEM dev server?

Missing assets during preview often stem from incorrect folder paths or unverified metadata. You can troubleshoot these rendering issues using a structured checklist to verify asset loading and metadata consistency.

Do I need a running local AEM dev server to preview imported HTML?

Yes, you need a running local AEM Edge Delivery Services dev server to preview imported HTML, as the workflow requires an active local environment to accurately verify rendering and troubleshoot visual discrepancies.

How does SKILL.md metadata drive the preview workflow for imported content?

SKILL.md metadata drives the preview workflow by providing the context needed to compare rendering against the source page, ensuring accurate verification of structure, assets, and metadata consistency during local preview.