plugins/aem/6.5-lts/skills/aem-replication/SKILL.md
Single entry point for all AEM 6.5 LTS Replication skills. Covers configuring replication agents, activating/deactivating content, using the Replication API programmatically, and troubleshooting distribution issues for Adobe Experience Manager 6.5 LTS.
npx skillsauth add adobe/skills aem-replicationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Route user requests to the appropriate specialist skill based on intent.
| User Intent | Skill | Path | |---|---|---| | Configure replication agents (default, dispatcher flush, reverse replication) | Configure Replication Agent | configure-replication-agent/SKILL.md | | Activate or deactivate content using UI or workflows | Replicate Content | replicate-content/SKILL.md | | Use Replication API programmatically in custom code | Replication API | replication-api/SKILL.md | | Diagnose blocked queues, connectivity issues, or distribution problems | Troubleshoot Replication | troubleshoot-replication/SKILL.md | | End-to-end workflows: new environment setup, incident response, performance optimization | Replication Orchestrator | replication-orchestrator/SKILL.md |
Set up and configure replication agents for:
When to use: First-time setup, adding new publish instances, reconfiguring agents
Activate and deactivate content through:
When to use: Publishing pages, assets, or DAM content; unpublishing content
Programmatic replication using official AEM 6.5 LTS public APIs:
When to use: Custom code integration, bulk operations, workflow process steps, servlets
Diagnose and fix common issues:
When to use: Replication failures, performance issues, content not distributing
Coordinates end-to-end replication workflows spanning multiple sub-skills:
When to use: Multi-step scenarios requiring coordination across configure, replicate, API, and troubleshoot skills
Shared reference materials used across all replication skills:
All skills reference official Adobe AEM 6.5 LTS documentation:
AEM as a Cloud Service uses the Sling Distribution API instead of replication agents. If planning migration:
skills/aem/cloud-service/skills/best-practices/references/replication.mdtools
Use the run-workflow MCP to discover, compose, execute, publish, and save Adobe Firefly workflows. TRIGGER when: user asks what actions are available, what the MCP can do, how to process images/video/3D via workflow, wants to build/run/save/publish a workflow, OR pastes any workflow/batch/execution ID. BARE ID (UUID/workflowId/batchId) = INSPECT ONLY — call inspect_run, NEVER run_workflow_submit. ALWAYS call list_actions first for capability/discovery questions. DO NOT TRIGGER for direct Firefly API calls without MCP (use firefly-api-specs).
tools
Run predefined featured workflows via run-workflow MCP. TRIGGER when user names a featured workflow (retargeting, banners at scale, localization, packaging, banner advertising, etc.) or asks to run a known marketing/production workflow. Requires run-workflow MCP. ALWAYS call get_featured_workflow before compose_workflow. DO NOT TRIGGER for custom one-off workflows with no named template — use run-workflow skill.
tools
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A questions answered with their defaults. Pass --doc-scan-only to scan README.md and env.dist for outdated content without modifying any files. Use when the user wants to migrate an App Builder project from the Integration Starter Kit or Checkout Starter Kit to the App Management approach, or mentions upgrading their Adobe Commerce extension architecture.
development
Add or modify webhook interceptors in an Adobe Commerce app. Use when the user wants to intercept Commerce operations to validate input, append data, or modify behavior — before or after execution. Requires a base app initialized with commerce-app-init.