aem-rde

Deploy, inspect, and troubleshoot AEM Rapid Development Environments via the aio CLI plugin.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill aem-rde-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aem-rde
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/aem-rde
Command: npx skills add https://github.com/aemgdc/aemdev --skill aem-rde-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @adobe/aio-cli-plugin-aem-rde, and includes references (resource) components.

What problem does it solve? Working with AEM Rapid Development Environments requires knowing the exact aio aem rde command surface, deployment types, configuration model, and error codes of the @adobe/aio-cli-plugin-aem-rde plugin. This Skill translates user goals into the correct commands and guides diagnosis of failed deployments, log triage, and snapshot management without guesswork. ## Core Features & Use Cases - Deployment guidance: Maps artifacts (OSGi bundles, OSGi configs, content packages, dispatcher configs, frontend builds, env-config YAML) to the correct install --type, target (author/publish), and flags. - Diagnostics playbook: Walks through setup --show, status, history <id>, logs, and inspect commands to triage failed deploys, inactive bundles, and unsatisfied OSGi components. - Configuration & CI support: Explains the three Cloud Manager IDs, local vs. global .aio config storage, experimental feature flags for inspect and snapshot, and scripted CI usage with --quiet --json. - Snapshot lifecycle: Guides create/restore/delete/undelete flows with realistic duration expectations and EAP enrollment requirements. - Use Case: A developer's content package deploy reports success but JCR content never appears; the Skill identifies the SKYOPS-140701 base-image regression and provides the exact OSGi config workaround to deploy. ## Quick Start Ask the assistant to deploy your OSGi bundle to your AEM RDE, for example: "Deploy core/target/my-bundle.jar to my RDE and confirm it is active."

Frequently Asked Questions about aem-rde

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

FAQPage Schema
How do I deploy an OSGi bundle to an AEM RDE?▼

Run `aio aem rde install path/to/bundle.jar` after configuring your org, program, and environment IDs with `aio aem rde setup`. The plugin guesses `osgi-bundle` from the .jar extension and deploys to both author and publish by default; verify with `aio aem rde status`.

How do I configure the aio aem rde plugin for multiple environments?▼

Use `aio config:set -l` to write cloudmanager_orgid, cloudmanager_programid, and cloudmanager_environmentid into a local `.aio` file per project directory. Local config overrides global config, so each repo pins its own RDE without cross-contamination.

What deployment types does aio aem rde install support?▼

The install command supports osgi-bundle, osgi-config, content-package, content-file, content-xml, dispatcher-config, frontend, and env-config. If `--type` is omitted, the plugin guesses from the file extension or by inspecting zip contents; pass `--type` explicitly for remote URLs.

Why does my RDE content package deploy succeed but no content appears?▼

This is a known base-image regression (SKYOPS-140701) where the RDE provider bundle is missing from the LoginAdminAllowList, silently aborting content extraction. Confirm via `aio aem rde logs -e ""` for a LoginException, then deploy the documented LoginAdminWhitelist fragment OSGi config as a workaround.

How do I enable RDE snapshot and inspect commands?▼

Both topics are experimental and gated behind a config flag: run `aio config set -l -j aem-rde.experimental-features '["aem:rde:inspect","aem:rde:snapshot"]'`. Snapshots additionally require enrollment in Adobe's snapshot EAP, otherwise the API returns a 451 NON_EAP error.

When should I use RDE reset versus snapshot restore?▼

Use `reset` to wipe deployed artifacts (optionally keeping mutable content with `--keep-mutable-content`) when the environment is in a broken state. Use `snapshot restore <name>` to return to a known-good captured state; both take roughly 10-20 minutes and should be confirmed before running.