/aem-workflow
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
$ npx -y skills add adobe/skills --skill aem-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/aem-workflow
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
aem-workflow.SKILL.mdname: 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
Read more
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
Repo: adobe/skills
Other skills on adobe-skills.
- /aa-conversion-funnel-analysis
Analyzes a multi-step conversion funnel to find where visitors drop off and which steps have the worst leakage. Use this skill when someone describes a journey and asks about conversion rates, drop-off, fallout, or step completion. Trigger for "analyze our checkout funnel,"
Open skill - /aa-executive-briefing
Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of
Open skill - /aa-kpi-pulse
Produces a compact KPI digest showing how key metrics changed over a period and what's driving the movement. Use this skill when someone asks for a performance summary, a weekly recap, a morning briefing, a KPI update, or any variation of "how did we do this week/month." Also
Open skill - /aa-segment-performance-comparator
Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences or visitor groups — for example, "how do mobile visitors compare to desktop on conversion," "compare new vs. returning visitors,"
Open skill - /aa-top-movers-watchlist
Identifies which items (pages, campaigns, products, channels, regions) had the biggest increases or decreases for a key metric between two time periods. Use this skill when someone asks "what's up and what's down," "which campaigns moved the most," "top gainers and losers,"
Open skill - /cja-dimension-analysis
Comprehensive dimension analysis and reporting for CJA. Use this skill whenever the user wants to analyze one or more dimensions — including cardinality, distribution/skew, trends, anomalies, data quality errors, comparisons, and forecasting. Also trigger when someone asks "what
Open skill

