| name | technical-advisory |
| description | Provide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEMaaCS cloud workflows only, with public-doc citations and cloud-specific MCP verification plans. Use for conceptual questions such as `statfileslevel`, filter rules, URL decomposition, cache invalidation behavior, rewrite behavior, and security headers. |
| 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"] |
| metadata | {"mcp-tool-contract":"core-7-tools"} |
Dispatcher Technical Advisory (Cloud)
Provide deterministic guidance for AEMaaCS use cases involving the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration.
Variant Scope
- This skill is cloud-service-only.
- Scope is fixed by this skill directory; do not ask the user to choose deployment variant.
MCP Tool Contract
Use only these Dispatcher MCP tools when producing verification plans:
validatelintsdktrace_requestinspect_cachemonitor_metricstail_logs
Workflow
- Confirm scope and assumptions.
- If the repo layout or execution path is unclear, start with quick-start-execution-path.md and repo-layout-workflows.md.
- Apply cloud-service-aemaacs-guardrails.md to lock immutable/include constraints, validator-enforced topology checks (symlinks/aliases/includes), reserved probe-path behavior, and CDN-vs-Dispatcher boundaries.
- Use capability-coverage-map.md to route prompt/tool/resource intents to the right dispatcher skill flow.
- Select a scenario path from core7-capability-playbook.md for development/debugging requests.
- Convert the selected playbook to exact MCP commands with playbook-command-linkage.md.
- For conceptual questions (e.g. statfileslevel, filter order, URL decomposition, cache invalidation), use concepts.md and cite official docs.
- Use curated public references for recommendations in this variant.
- Produce MCP verification steps for this variant when needed.
- Route execution-heavy changes to this variant's execution skills.
Verification Scope Selection
Use shared references for deterministic coverage:
Output Contract
Use one of these output shapes:
- Explanation-only question: recommendation summary + citation list from curated public-docs index.
- Recommendation/change question: recommendation summary + citation list + MCP verification plan with expected evidence + risk/rollback guidance and open risks.
Guardrails
- Do not claim a check was executed unless tool evidence exists.
- Keep variant assumptions explicit for every recommendation.
- For migration/cross-variant requests, produce a side-by-side variant delta plan from the verification matrix and flag when the companion variant plugin must be run separately.
- Follow citation discipline from
public-doc-citation-rules.md.
- Keep cloud-service-only guardrails explicit: immutable/default include contracts and CDN-vs-Dispatcher ownership.
References
