adobe/technical-advisory
plugins/aem/6.5-lts/skills/dispatcher/technical-advisory/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add adobe/skills technical-advisoryInstall 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: May 1, 2026, 12:35 AM69.7s1 file scanned
SKILL.md
- name:
- technical-advisory
- description:
- 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.
- license:
- Apache-2.0
- compatibility:
- Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`).
- allowed-tools:
- validate lint sdk trace_request inspect_cache monitor_metrics tail_logs
- mcp-tool-contract:
- core-7-tools
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:
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.
- 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.
- For conceptual questions (e.g. statfileslevel, filter order, URL decomposition, cache invalidation), use concepts.md and cite official docs.
- Apply ams-6-5-guardrails.md before recommendations (tier boundaries, variables, flush ACL, immutable constraints).
- Convert the selected playbook to exact MCP commands with playbook-command-linkage.md.
- 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:
- 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
srcroot 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
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