PluginPublic

adobe/aem-6-5-lts

All AEM 6.5 LTS skills: Workflow model design, development, triggering, launchers, debugging, and triaging; Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening; Replication agent configuration, content activation, API usage, and troubleshooting for AEM 6.5 LTS and AMS environments; Jackrabbit Oak query/index tuning (property, Lucene index definitions); and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quick Start Guide — AEM Workflow Development (6.5 LTS)

Determine What You Need

User request
    ├── "How do I create a workflow model?"
    │       → workflow-model-design/SKILL.md
    │
    ├── "How do I write a custom process step / participant chooser?"
    │       → workflow-development/SKILL.md
    │
    ├── "How do I start a workflow programmatically / via API?"
    │       → workflow-triggering/SKILL.md
    │
    ├── "How do I auto-trigger a workflow when content changes?"
    │       → workflow-launchers/SKILL.md
    │
    └── "I need end-to-end help designing + building + deploying a workflow"
            → workflow-orchestrator/SKILL.md

Minimum Viable Workflow (3 Steps)

Create a model in the Workflow Model Editor or via content package at /conf/global/settings/workflow/models/my-workflow
Implement a WorkflowProcess class registered with process.label=My Step
Deploy via Maven (mvn install -P autoInstallPackage) or Package Manager

Prerequisite Checklist

Before starting:
- [ ] AEM 6.5 LTS instance running (author)
- [ ] Maven project with core + ui.content modules
- [ ] Service user created with appropriate ACLs
- [ ] Bundle deployed; process.label visible in Workflow Model Editor
- [ ] Filter.xml covers model + launcher paths

Verify Deployment

# Check bundle is active
curl -u admin:admin http://localhost:4502/system/console/bundles/com.example.my-bundle.json

# Check process.label registered (visible in model editor step picker)
# Navigate to: Tools → Workflow → Models → Create → add Process step → configure

# Check model synced to /var
curl -u admin:admin "http://localhost:4502/var/workflow/models/my-workflow.json"

Start a Test Workflow via API

# POST to /var/workflow/instances — NOT /api/workflow/instances (posting there silently
# writes stray JCR nodes and returns a misleading 2xx without starting any workflow).
# Returns HTTP 201 with an HTML body linking to the new instance path.
curl -u admin:admin -X POST \
  "http://localhost:4502/var/workflow/instances" \
  --data-urlencode "_charset_=utf-8" \
  --data-urlencode "model=/var/workflow/models/my-workflow" \
  --data-urlencode "payloadType=JCR_PATH" \
  --data-urlencode "payload=/content/test-page"

# Confirm it is running
curl -u admin:admin "http://localhost:4502/var/workflow/instances.RUNNING.json"

Monitor at: Tools → Workflow → Instances → filter by model or status.