Technical Advisory

adobe/skills/plugins/aem/6.5-lts/skills/dispatcher/technical-advisory

by adobe940b8795c0dfApache-2.0197 starsListed Oct 9, 2026Updated Oct 8, 2026Repository updated today

Provide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM 6.5 / AMS workflows only, with public-doc citations and AMS-specific MCP verification plans. Use for conceptual questions such as `statfileslevel`, filter rules, URL decomposition, cache invalidation behavior, rewrite behavior, and security headers.

AI-generated overview

Gives AMS-only advisory guidance on Adobe Dispatcher and HTTPD configuration for AEM 6.5, with citations and MCP verification plans.

What it does
This instruction-only skill answers conceptual and change questions about the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM 6.5 / AMS. It routes requests through reference files covering concepts such as statfileslevel, filter rules, URL decomposition, cache invalidation and rewrite behavior, then applies AMS guardrails. Outputs are a recommendation summary with curated public-doc citations, plus MCP verification steps with expected evidence and risk/rollback guidance when a change is proposed.
When to use it
Use it for conceptual questions about Dispatcher behavior, such as statfileslevel, filter order, URL decomposition or invalidate versus flush. Use it when recommending or reviewing Dispatcher/HTTPD configuration changes in an AMS AEM 6.5 context and a verification plan is needed. It is AMS-only and does not cover other deployment variants.
Requirements
Requires Dispatcher MCP for AMS (AEM_DEPLOYMENT_MODE=ams) or the AMS Dispatcher MCP SDK pre-set to ams, exposing the tools validate, lint, sdk, trace_request, inspect_cache, monitor_metrics and tail_logs. Ships no scripts; it is instructions plus reference documents only.

Dispatcher Technical Advisory (AMS)

Provide deterministic guidance for AEM 6.5/AMS use cases involving the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration.

Variant Scope

  • This skill is AMS-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:

  • validate
  • lint
  • sdk
  • trace_request
  • inspect_cache
  • monitor_metrics
  • tail_logs

Workflow

  1. Confirm scope and assumptions.
  2. If the repo layout or execution path is unclear, start with quick-start-execution-path.md and repo-layout-workflows.md.
  3. Use capability-coverage-map.md to route prompt/tool/resource intents to the right dispatcher skill flow.
  4. Select a scenario path from core7-capability-playbook.md for development/debugging requests.
  5. For conceptual questions (e.g. statfileslevel, filter order, URL decomposition, cache invalidation), use concepts.md and cite official docs.
  6. Apply ams-6-5-guardrails.md before recommendations (tier boundaries, variables, flush ACL, immutable constraints).
  7. Convert the selected playbook to exact MCP commands with playbook-command-linkage.md.
  8. Use curated public references for recommendations in this variant.
  9. Produce MCP verification steps for this variant when needed.
  10. Route execution-heavy changes to this variant's execution skills.

Verification Scope Selection

Use shared references for deterministic coverage:

  • mode-specific-verification-matrix.md
  • test-case-catalog.md

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.

References

  • core7-capability-playbook.md – high-value development/debugging playbooks for the current core-7 MCP contract
  • capability-coverage-map.md – prompt/tool/resource coverage map to current dispatcher skill workflows
  • concepts.md – key concepts (filter last-match, URL decomposition, statfileslevel, invalidate vs flush) for explanations
  • quick-start-execution-path.md – single entry path for broad or first-time requests
  • repo-layout-workflows.md – normalize repos to the dispatcher src root and likely file families
  • playbook-command-linkage.md – deterministic linkage from playbooks to MCP commands and tests
  • ams-6-5-guardrails.md – AMS topology/variables/flush and immutable-file constraints
  • public-docs-index.md
  • public-doc-citation-rules.md
  • mode-specific-verification-matrix.md
  • test-case-catalog.md
  • change-risk-and-rollback-template.md
  • core-7-tools-reference.md
  • request-router.md

Source and attribution

Source:adobe/skillsinplugins/aem/6.5-lts/skills/dispatcher/technical-advisoryat commit940b879

License: Apache-2.0

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal