Skip to main content
affpapa.org
RU EN
skill CX Codex

aem-workflow — Claude Code skill: routing AEM 6.5 LTS workflow tasks

Entry point for the AEM 6.5 LTS Workflow skill set: reads your request and routes it to the right specialist, from model design to stuck-instance debugging.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add adobe/skills --skill aem-workflow -a claude-code
Open on GitHub

What aem-workflow does

The skill acts as a router. It matches your request against an intent table and picks one specialist skill: model design, custom step development, workflow triggering, launcher configuration, debugging, or incident triage. Broad requests that touch several areas go to the orchestrator, which coordinates across the specialists.

What's inside: links to a separate SKILL.md per area plus reference tables. One table lists 6.5 LTS and AMS capabilities — JMX access through Felix Console, retrying failed items with retryFailedWorkItems, stale detection with countStaleWorkflows, restart via restartStaleWorkflows(dryRun=true), cleanup with purgeCompleted. Another covers guardrails: don't edit /libs, keep models at /conf/global/settings/workflow/models/<id>, use /var/workflow/models/<id> for runtime API calls, and resolve service users through ResourceResolverFactory.getServiceResourceResolver() rather than loginAdministrative.

You need AEM 6.5 LTS or Adobe Managed Services, plus a Maven project with core and ui.apps modules. Without that layout the skill has nothing to anchor its paths and examples to.

What it helps with

  • design a workflow model with steps and OR/AND splits
  • implement a custom WorkflowProcess and register it as an OSGi service
  • start a workflow from code, the HTTP API, or the Timeline UI
  • configure a launcher to auto-start on asset upload
  • trace why a step is stuck or failed using logs and JMX

Example prompts for the agent

  • help me design a workflow model for asset publishing
  • the workflow is stuck on a step, check JMX and the logs
  • set up a launcher so the workflow starts on asset upload

How to install aem-workflow

1Skills CLI (Vercel)

npx skills add adobe/skills --skill aem-workflow -a claude-code

2Manually: put the files in place

~/.claude/skills/aem-workflow/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/aem-workflow/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about aem-workflow

How do I install aem-workflow in Claude?

Run npx skills add adobe/skills --skill aem-workflow -a claude-code. The skill file then lands at ~/.claude/skills/aem-workflow/SKILL.md.

What does aem-workflow do?

It takes an AEM Workflow request and routes it to the matching specialist skill — model design, development, triggering, launchers, debugging, or triaging. Requests spanning several concerns go through the orchestrator.

What do I need for the skill to work?

AEM 6.5 LTS or Adobe Managed Services and a Maven project with core and ui.apps modules. For diagnostics, access to JMX and the logs under crx-quickstart/logs/ helps.

Source text

SKILL.md · Apache-2.0 
---
name: aem-workflow
description: |
  Single entry point for all AEM 6.5 LTS Workflow skills. Covers workflow model design,
  custom process step and participant chooser development, launcher configuration, workflow triggering,
  and production support including debugging stuck/failed workflows, triaging incidents with JMX,
  Splunk, direct log access, thread pool analysis, and Sling Job diagnostics for the Granite Workflow Engine.
license: Apache-2.0
compatibility: Requires AEM 6.5 LTS or Adobe Managed Services (AMS). Maven project structure with core and ui.apps modules.
metadata:
  version: "1.0"
  aem_version: "6.5 LTS"
---

# AEM 6.5 LTS Workflow

Route user requests to the appropriate specialist skill based on intent.

## Intent Router

| User Intent | Skill | Path |
|---|---|---|
| Create a workflow model, add steps, design OR/AND splits, configure variables | Model Design | [workflow-model-design/SKILL.md](./workflow-model-design/SKILL.md) |
| Implement a custom WorkflowProcess step, ParticipantStepChooser, OSGi service registration | Development | [workflow-development/SKILL.md](./workflow-development/SKILL.md) |
| Start a workflow from code, HTTP API, Timeline UI, Manage Publication, replication triggers | Triggering | [workflow-triggering/SKILL.md](./workflow-triggering/SKILL.md) |
| Configure a launcher, auto-start on asset upload, overlay OOTB launcher | Launchers | [workflow-launchers/SKILL.md](./workflow-launchers/SKILL.md) |
| Workflow stuck, failed step, missing Inbox task, stale instances, thread pool exhaustion, purge | Debugging | [workflow-debugging/SKILL.md](./workflow-debugging/SKILL.md) |
| Classify a workflow incident, determine required logs, JMX diagnostics, Splunk queries | Triaging | [workflow-triaging/SKILL.md](./workflow-triaging/SKILL.md) |
| End-to-end lifecycle or requests spanning multiple concerns | Orchestrator | [workflow-orchestrator/SKILL.md](./workflow-orchestrator/SKILL.md) |

## How to Use

1. Match the user's request to one row in the Intent Router table above.
2. Read the linked SKILL.md for that specialist skill.
3. Follow the workflow, references, and output contract defined in that skill.
4. For broad or ambiguous requests that span multiple concerns, use the **Orchestrator** which coordinates across all specialist skills and loads foundation references.

## 6.5 LTS / AMS Capabilities

| Capability | Detail |
|---|---|
| JMX | Full access via Felix Console (`/system/console/jmx`) or JMX client |
| Retry failed items | JMX `retryFailedWorkItems` or Inbox Retry |
| Stale detection | JMX `countStaleWorkflows` |
| Stale restart | JMX `restartStaleWorkflows(dryRun=true)` then execute |
| Purge | JMX `purgeCompleted(dryRun=true)` or Purge Scheduler |
| Log access | Direct filesystem (`crx-quickstart/logs/`) or AMS log access |
| Config changes | Felix Console, OSGi config in repo, or CRX/DE |

## 6.5 LTS Guardrails

| Rule | Detail |
|---|---|
| Avoid editing `/libs` | Use overlays under `/apps` or store at `/conf/global` |
| Model design-time path | `/conf/global/settings/workflow/models/<id>` (preferred) or `/etc/workflow/models/<id>` (legacy) |
| Model runtime path (for API calls) | `/var/workflow/models/<id>` |
| Launcher config paths | `/conf/global/settings/workflow/launcher/config/` (preferred) |
| Service users | Use `ResourceResolverFactory.getServiceResourceResolver()` with a sub-service; avoid `loginAdministrative` |
| OSGi annotations | DS R6 preferred; Felix SCR still supported on 6.5 LTS |
| Deploy via | Package Manager, Maven + Content Package Plugin |

## Specialist Skills

- [workflow-model-design/SKILL.md](./workflow-model-design/SKILL.md) — model structure, step types, variables, and model XML
- [workflow-development/SKILL.md](./workflow-development/SKILL.md) — WorkflowProcess, ParticipantStepChooser, metadata, and error handling
- [workflow-triggering/SKILL.md](./workflow-triggering/SKILL.md) — Timeline UI, Manage Publication, WorkflowSession API, HTTP API, and replication triggers
- [workflow-launchers/SKILL.md](./workflow-launchers/SKILL.md) — launcher configuration, JCR event binding, and OOTB overlay
- [workflow-debugging/SKILL.md](./workflow-debugging/SKILL.md) — stuck workflows, failed steps, JMX remediation, thread pools, and purge
- [workflow-triaging/SKILL.md](./workflow-triaging/SKILL.md) — symptom classification, JMX diagnostics, log patterns, Splunk queries, and data gathering
- [workflow-orchestrator/SKILL.md](./workflow-orchestrator/SKILL.md) — full lifecycle orchestration across all skills

© adobe · Apache-2.0 · adobe/skills

Similar skills

All skills for Agent setup: memory, context, orchestration →
AEM Front-End Specialist official github Builds Adobe Experience Manager components using HTL and Tailwind CSS v4, extracting design tokens directly from Figma. ★ 40,418repo stars siem-detection briiirussell Engineers and audits SIEM detection rules across Sigma, KQL, SPL, and Elastic, mapping coverage against MITRE ATT&CK. CX Codex +1 330installs threat-hunting briiirussell Proactively hunts for adversaries in SIEM, EDR, and logs before alerts fire. Guides hypothesis-driven investigations using the PEAK framework and MITRE ATT&CK. CX Codex +1 333installs migrating-to-workflow-sdk Vercel Inc. Ports orchestration from Temporal, Inngest, Trigger.dev or AWS Step Functions to the Workflow SDK, returning a migration plan and rewritten code. CX Codex +1 734installs aws-step-functions aws Authors and edits AWS Step Functions definitions in Amazon States Language: state types, JSONata, Retry/Catch, Distributed Map. CX Codex +1 3,900installs inngest sickn33 Skill for working with Inngest: configure background jobs, event-driven workflows, and durable processes without managing queues or workers. Use it for delayed operations, multi-step workflows, or webhook processing. CX Codex +1 1,200installs

From the same set46

create-site Walks an agent through a brand-new AEM Edge Delivery site: repo from the boilerplate, aem-code-sync, starter DA pages, live preview link. CX Codex +1 1,500installs ensure-agents-md Creates AGENTS.md and CLAUDE.md at the root of an AEM 6.5 LTS project when they are missing. It adapts project guidance from pom.xml and the module structure. CX Codex +1 1,100installs da-auth Fetches an Adobe IMS access token into DA_TOKEN so your agent can call admin.da.live without a manual copy-paste. CX Codex +1 1,000installs create-component Generates complete AEM components with HTL markup, Sling Models, dialogs, and tests. Extends Core Components and converts Figma designs into code. CX Codex +1 1,000installs dispatcher One entry point for the AEM 6.5 LTS Dispatcher skills: it reads your request and hands it to the right specialist. CX Codex +1 986installs migration A skill for moving a legacy AEM 6.x, AMS or on-prem project to AEM as a Cloud Service: scan the project first, then fix one blocker per session. CX Codex +1 918installs content-distribution Skill for AEM as a Cloud Service: publish content programmatically through the Replication API and watch distribution events. CX Codex +1 851installs aem-cli Helps configure and run the Adobe AEM CLI for Edge Delivery Services, resolve dev server errors, manage TLS, and handle content sync. CX Codex +1 840installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor