adobe/aem-workflow
plugins/aem/6.5-lts/skills/aem-workflow/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add adobe/skills aem-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 9, 2026, 4:02 AM121.4s44 files scanned
SKILL.md
- name:
- aem-workflow
- description:
- |
- license:
- Apache-2.0
- compatibility:
- Requires AEM 6.5 LTS or Adobe Managed Services (AMS). Maven project structure with core and ui.apps modules.
- 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 | | Implement a custom WorkflowProcess step, ParticipantStepChooser, OSGi service registration | Development | workflow-development/SKILL.md | | Start a workflow from code, HTTP API, Timeline UI, Manage Publication, replication triggers | Triggering | workflow-triggering/SKILL.md | | Configure a launcher, auto-start on asset upload, overlay OOTB launcher | Launchers | workflow-launchers/SKILL.md | | Workflow stuck, failed step, missing Inbox task, stale instances, thread pool exhaustion, purge | Debugging | workflow-debugging/SKILL.md | | Classify a workflow incident, determine required logs, JMX diagnostics, Splunk queries | Triaging | workflow-triaging/SKILL.md | | End-to-end lifecycle or requests spanning multiple concerns | Orchestrator | workflow-orchestrator/SKILL.md |
How to Use
- Match the user's request to one row in the Intent Router table above.
- Read the linked SKILL.md for that specialist skill.
- Follow the workflow, references, and output contract defined in that skill.
- 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 — model structure, step types, variables, and model XML
- workflow-development/SKILL.md — WorkflowProcess, ParticipantStepChooser, metadata, and error handling
- workflow-triggering/SKILL.md — Timeline UI, Manage Publication, WorkflowSession API, HTTP API, and replication triggers
- workflow-launchers/SKILL.md — launcher configuration, JCR event binding, and OOTB overlay
- workflow-debugging/SKILL.md — stuck workflows, failed steps, JMX remediation, thread pools, and purge
- workflow-triaging/SKILL.md — symptom classification, JMX diagnostics, log patterns, Splunk queries, and data gathering
- workflow-orchestrator/SKILL.md — full lifecycle orchestration across all skills
Related Skills
adobe/run-workflow
tools
VerifiedTrustedCommunity
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).
150SKILL.mdUpdated Jul 28, 2026
adobe/run-featured-workflow
tools
VerifiedTrustedCommunity
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.
150SKILL.mdUpdated Jul 28, 2026
adobe/commerce-app-migrate
tools
VerifiedTrustedCommunity
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.
150SKILL.mdUpdated Jul 24, 2026
adobe/commerce-app-webhooks
development
VerifiedTrustedCommunity
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.
150SKILL.mdUpdated Jul 24, 2026