All AEM as a Cloud Service skills: component development, Workflow model design, development, triggering, launchers, debugging, and triaging, Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening, Rapid Development Environment (RDE) deployment, log inspection, snapshots, and troubleshooting via `aio aem rde`, Jackrabbit Oak query/index tuning (property, Lucene index definitions), and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Skills for developing, assessing, migrating, and operating AEM as a Cloud Service projects — component development, Dispatcher configuration, workflows, code assessment, content distribution, migration from legacy AEM, and Rapid Development Environments.
Claude Code:
/plugin marketplace add adobe/skills
/plugin install aem-cloud-service@adobe-skills| Skill | Description | Try it |
|---|---|---|
| ensure-agents-md | Auto-generates AGENTS.md and CLAUDE.md from pom.xml when missing — tailored to the project's modules and add-ons (CIF, Forms, SPA, precompiled scripts). Runs first, before any other work. | Set up my AEM project for AI agents |
| create-component | Create complete AEM components following Adobe best practices: component definition, dialog XML, HTL template, Sling Model, unit tests, clientlibs (component and dialog), and optional Sling Servlet for dynamic content. | Create a hero banner component with title, description, and CTA |
Config authoring, advisory, performance, security, and incident response. Requires Dispatcher MCP (AEM_DEPLOYMENT_MODE=cloud).
| Skill | Description | Try it |
|---|---|---|
| config-authoring | Create, modify, review, and harden Dispatcher config files (.any, vhost, rewrite, cache, filter) | Add a new vhost for my site |
| technical-advisory | Conceptual guidance on statfileslevel, filter rules, URL decomposition, cache invalidation, rewrite behavior, and security headers — with public-doc citations | Explain statfileslevel for my site |
| incident-response | Investigate runtime incidents, failures, probe regressions, and cache anomalies using Dispatcher MCP evidence | Why are my pages returning 403? |
| performance-tuning | Optimize Dispatcher cache efficiency, latency, and throughput with cloud-specific baselines | Tune my dispatcher cache for better hit ratios |
| security-hardening | Security audits, threat models, exposure control, and header hardening | Harden my dispatcher security headers |
| workflow-orchestrator | Orchestrate complete Dispatcher lifecycle from design through validation, release readiness, and incident troubleshooting | Walk me through setting up dispatcher for a new site end-to-end |
Granite Workflow Engine lifecycle: design, develop, deploy, debug.
| Skill | Description | Try it |
|---|---|---|
| workflow-model-design | Design workflow models — step types, variables, OR/AND splits, deployment through Cloud Manager pipeline | Design an approval workflow with OR split |
| workflow-development | Implement custom WorkflowProcess steps, ParticipantStepChooser, OSGi DS R6 registration | Create a custom workflow process step |
| workflow-triggering | Start workflows via Timeline UI, WorkflowSession API, HTTP API, or Manage Publication | How do I trigger a workflow programmatically? |
| workflow-launchers | Configure Workflow Launchers that auto-start workflows on JCR content changes | Set up a launcher for asset uploads |
| workflow-debugging | Debug stuck workflows, failed steps, missing Inbox tasks, thread pool exhaustion, queue backlogs, purge failures | My workflow is stuck — help debug |
| workflow-triaging | Classify workflow incidents, determine required logs, and map to Splunk queries | Triage this workflow failure from Cloud Manager logs |
| workflow-orchestrator | End-to-end workflow lifecycle orchestration across all sub-skills | Build a complete content approval workflow |
| Skill | Description | Try it |
|---|---|---|
| code-assessment | Detect and fix AEM CS code-quality issues locally — Sling Model patterns (@Inject to injector-specific), deprecated APIs, scheduler, replication, resource listeners, unbounded queries, outbound call timeouts, event migration, asset manager API, outdated Maven dependencies. Verifies with mvn compile. | Scan this AEM project for code issues |
| migration | Migrate legacy AEM (6.x, AMS, on-prem) to AEM CS using BPA CSV/cache or CAM/MCP discovery. Covers scheduler, ResourceChangeListener, replication, EventListener, OSGi EventHandler, DAM AssetManager, HTL lint, Classic UI dialog migration, Custom Design Widgets, static to editable template modernization, and OSGi config to Cloud Manager. One pattern per session; delegates refactors to code-assessment. Also validates migrated code on a local Cloud SDK via the AEM Quickstart MCP (Branch G, beta). | Review my code for AEMaaCS migration |
| Skill | Description | Try it |
|---|---|---|
| content-distribution | Programmatic content publishing via the Replication API (single-path, bulk, preview-tier, async) and distribution event monitoring via Sling Distribution events | Publish content programmatically |
| Skill | Description | Try it |
|---|---|---|
| aem-rde (beta) | Expert assistance for aio aem rde — deploy bundles/configs/content/frontend, inspect artifacts, tail logs, create/restore snapshots, and troubleshoot RDE issues. Activates only on explicit RDE references. | Deploy my bundle to the RDE |