plugins/aem/cloud-service/skills/dispatcher/SKILL.md
Single entry point for all AEM as a Cloud Service Dispatcher skills. Covers config authoring, technical advisory, incident response, performance tuning, security hardening, and full lifecycle orchestration for the Adobe Dispatcher Apache HTTP Server module and its HTTPD/dispatcher configuration.
npx skillsauth add adobe/skills dispatcherInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Route user requests to the appropriate specialist skill based on intent.
| User Intent | Skill | Path |
|---|---|---|
| Create, modify, review, or harden dispatcher config files (.any, vhost, rewrite, cache, filter) | Config Authoring | config-authoring/SKILL.md |
| Conceptual questions (statfileslevel, filter rules, URL decomposition, cache invalidation, rewrite behavior, security headers) | Technical Advisory | technical-advisory/SKILL.md |
| Investigate runtime incidents, failures, probe regressions, or cache anomalies | Incident Response | incident-response/SKILL.md |
| Optimize cache efficiency, latency, and throughput | Performance Tuning | performance-tuning/SKILL.md |
| Security audit, threat model, exposure control, header hardening | Security Hardening | security-hardening/SKILL.md |
| End-to-end lifecycle (design → implement → validate → release → incident) or requests spanning multiple concerns | Workflow Orchestrator | workflow-orchestrator/SKILL.md |
All specialist skills share the same core-7 MCP tool set:
validate — static config validationlint — deep/order-aware lintingsdk — SDK check-files and diff-baselinetrace_request — trace a request through dispatcherinspect_cache — inspect cache statemonitor_metrics — runtime metricstail_logs — log tailingtools
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).
tools
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.
tools
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.
development
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.