adobe/workflow-orchestrator
plugins/aem/cloud-service/skills/dispatcher/workflow-orchestrator/SKILL.md
Orchestrate complete lifecycle work for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service, from design and implementation through validation, release readiness, and incident troubleshooting.
$ install --global
skillsauthnpx skillsauth add adobe/skills workflow-orchestratorInstall 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: Apr 29, 2026, 6:40 AM219.6s13 files scanned
SKILL.md
- name:
- workflow-orchestrator
- description:
- Orchestrate complete lifecycle work for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service, from design and implementation through validation, release readiness, and incident troubleshooting.
- license:
- Apache-2.0
- compatibility:
- Requires Dispatcher MCP configured for cloud variant (`AEM_DEPLOYMENT_MODE=cloud`).
- allowed-tools:
- validate lint sdk trace_request inspect_cache monitor_metrics tail_logs
- mcp-tool-contract:
- core-7-tools
Dispatcher Workflow Orchestrator (Cloud)
Use this skill when users need end-to-end Dispatcher support instead of a single specialist workflow.
Scope
- Full lifecycle orchestration for cloud Dispatcher work:
- requirements and design
- config implementation and hardening
- filter, cache, rewrite, vhost, and farm design
- feature-specific flows such as
/auth_checker, vanity URLs, GraphQL/CORS, Commerce proxy routes, frontend-static passthrough, and Dynamic Media delivery passthrough - static/runtime validation
- release readiness and rollback planning
- production incident triage
Routing Model
- Start in
config-authoringfor file design and edits. - Pull in
technical-advisoryfor policy, documentation, cloud guardrails, and evidence planning. - Pull in
security-hardeningandperformance-tuningfor non-functional risk checks and environment-sensitive review. - Switch to
incident-responsefor live failures, probe regressions, cache anomalies, or validator/runtime mismatches. - Return a single consolidated output: changes, evidence, risk, rollback, and follow-ups.
Operational Packaging
Use these shared references to keep broad requests deterministic:
- Start with quick-start-execution-path.md when the user is new, the repo root is ambiguous, or the request spans multiple concerns.
- Normalize the repo to a dispatcher
srcroot with repo-layout-workflows.md. - Convert the chosen specialist playbook into exact MCP commands with playbook-command-linkage.md.
- Use the specialist skill references only after the path above is fixed.
Entry Criteria
Use when user intent is any of:
- end-to-end implementation
- pre-release readiness review
- troubleshooting + fix + re-validation in one flow
- broad audit across config, security, and performance
- complete cloud-service dispatcher development from new feature to release gate
- “single point of development” requests that span authoring, validation, troubleshooting, and hardening
Exit Criteria
Always return:
- touched files and why
- executed checks (static + runtime) and evidence
- selected scenario/playbook path
- unresolved risks/gaps
- rollback trigger + rollback action
- next-step plan if prerequisites blocked verification
Related Skills
- config-authoring
- technical-advisory
- security-hardening
- performance-tuning
- incident-response
References
- quick-start-execution-path.md
- repo-layout-workflows.md
- playbook-command-linkage.md
- core-7-tools-reference.md
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