preview-import

Validate imported HTML rendering against a reference screenshot in AEM Edge Delivery Services.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/trieloff/trrrrdt --skill preview-import-trieloff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/trieloff/trrrrdt/tree/main/.claude/skills/preview-import
Command: npx skills add https://github.com/trieloff/trrrrdt --skill preview-import-trieloff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This content validation workflow ensures that imported content renders correctly in a local AEM Edge Delivery Services development environment, helping catch rendering, layout, and asset discrepancies early.

Core Features & Use Cases

  • Preview locally rendered content from the import pipeline against the original page.
  • Verify asset loading, styling, and structure to ensure fidelity.
  • Troubleshoot rendering issues quickly by comparing against a reference screenshot.

Quick Start

Start the local AEM proxy with aem up and open the preview URL to verify the imported page.

Frequently Asked Questions about preview-import

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

FAQPage Schema
How do I preview imported content in a local AEM Edge Delivery Services dev server?

To preview imported content in a local AEM Edge Delivery Services dev server, start the proxy with aem up and open the preview URL to verify the rendered page against the original.

What do I need to validate imported content rendering in AEM?

Validating imported content rendering in AEM requires a valid HTML file, an images folder, a reference screenshot for comparison, and a documentPath from metadata.json to construct URLs.

How does screenshot comparison work for AEM content imports?

Screenshot comparison for AEM content imports works by rendering the imported page locally and comparing it against a reference screenshot to spot visual, layout, and asset discrepancies early.

Can I troubleshoot rendering issues for imported HTML files locally?

You can troubleshoot rendering issues for imported HTML files locally by running the AEM development server, previewing the rendered content, and comparing it directly with the original reference screenshot.

Does this content validation workflow integrate with the page-import and scrape-webpage workflows?

The content validation workflow integrates with the page-import and scrape-webpage workflows by using the imported HTML files, images, and metadata to construct URLs and verify rendering fidelity.

What rendering discrepancies can I catch when previewing imported AEM content?

Previewing imported AEM content helps catch rendering discrepancies including broken asset loading, styling issues, and structural layout differences between the local preview and the original page.