plugins/aem/6.5-lts/skills/aem-replication/replicate-content/SKILL.md
Use when publishing, unpublishing, replicating, or activating/deactivating content in AEM 6.5 LTS. Covers Quick Publish, Manage Publication, tree activation, bulk content activation, package replication, workflow-based approval, scheduled activation/deactivation (on/off time), dispatcher flush, and the programmatic Replication Java API for AEM publish instances.
npx skillsauth add adobe/skills replicate-contentInstall 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.
Use this skill when the user asks to publish, unpublish, replicate, activate, deactivate, or bulk-replicate content on AEM 6.5 LTS publish instances.
configure-replication-agent| Method | When to Use | Scope |
|--------|-------------|-------|
| Quick Publish | Fast single-page activation, no approval | Selected pages only (shallow) |
| Manage Publication | Scheduling, references, or workflow control | Single/multiple pages with options |
| Tree Activation | Entire site section or initial site launch | Page tree (see references/TREE_ACTIVATION.md) |
| Package Replication | Specific content sets or cross-env deploy | Custom JCR filter (see references/PACKAGE_REPLICATION.md) |
| Workflow Replication | Approval required before going live | Any content with assigned approver |
| Scheduled Activation | Time-based publish/unpublish | On Time / Off Time in page properties |
| Replication API | Programmatic from Java or scripts | Any JCR path (see references/REPLICATION_API.md) |
Sites console → select page(s) → Quick Publish (toolbar or right-click menu)
Sites console → select page(s) → Manage Publication
http://localhost:4502/miscadmin → Replication → Activate Tree
/content/mysite/enFor full steps and performance guidance, see references/TREE_ACTIVATION.md.
/crx/packmgr → Create Package → add filters → Build → More → Replicate
http://publish:4503/crx/packmgr)For full steps, see references/PACKAGE_REPLICATION.md.
Select page → Timeline panel → Start Workflow → Request for Activation → assign approver
http://localhost:4502/aem/inbox: Approve → content activates; Reject → returns to authorPage Properties → Advanced tab → set On Time (activate) and/or Off Time (deactivate)
/etc/replication/agents.author/[agent] → Triggers tab → "On-/Offtime reached" is checked@Reference private Replicator replicator;
replicator.replicate(session, ReplicationActionType.ACTIVATE, "/content/path");
replicator.replicate(session, ReplicationActionType.DEACTIVATE, "/content/path");
curl -u $AEM_USER:$AEM_PASSWORD -X POST http://localhost:4502/bin/replicate.json \
-F "cmd=Activate" -F "path=/content/mysite/en/page"
# ✓ Verify: HTTP 200 with {"success":true,"path":"/content/mysite/en/page"}
For ReplicationOptions (synchronous, agent filtering) and full curl error handling, see references/REPLICATION_API.md.
Sites console → select page(s) → Quick Unpublish (or Manage Publication → Unpublish)
| Indicator | Meaning | |-----------|---------| | Green checkmark | Published and up-to-date | | Orange dot | Modified since last publish — re-publish needed | | Gray circle | Never published |
Check queue: Tools → Deployment → Replication → Agents on author → [agent] → queue should be idle/empty after processing.
Logs: crx-quickstart/logs/replication.log
For deep diagnostics, use the troubleshoot-replication skill.
Use the Assets console (/assets.html/content/dam) with the same Quick Publish / Manage Publication actions. All renditions and metadata replicate automatically. For shared datastores, enable binary-less replication (Serialization Type: Binary-less) on the agent to transfer only metadata nodes.
configure-replication-agent — set up and configure replication agentsreplication-api — full programmatic Replication API reference for custom OSGi services and servletstroubleshoot-replication — diagnose and resolve replication failurestools
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.