technical-advisory
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.
What this skill does
# 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](./references/dispatcher-foundation/quick-start-execution-path.md) and [repo-layout-workflows.md](./references/dispatcher-foundation/repo-layout-workflows.md). 3. Use [capability-coverage-map.md](./references/technical-advisory/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](./references/technical-advisory/core7-capability-playbook.md) for development/debugging requests. 5. For conceptual questions (e.g. statfileslevel, filter order, URL decomposition, cache invalidation), use [concepts.md](./references/technical-advisory/concepts.md) and cite official docs. 6. Apply [ams-6-5-guardrails.md](./references/dispatcher-foundation/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](./references/dispatcher-foundation/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](./references/dispatcher-foundation/mode-specific-verification-matrix.md) - [test-case-catalog.md](./references/dispatcher-foundation/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](./references/technical-advisory/core7-capability-playbook.md) – high-value development/debugging playbooks for the current core-7 MCP contract - [capability-coverage-map.md](./references/technical-advisory/capability-coverage-map.md) – prompt/tool/resource coverage map to current dispatcher skill workflows - [concepts.md](./references/technical-advisory/concepts.md) – key concepts (filter last-match, URL decomposition, statfileslevel, invalidate vs flush) for explanations - [quick-start-execution-path.md](./references/dispatcher-foundation/quick-start-execution-path.md) – single entry path for broad or first-time requests - [repo-layout-workflows.md](./references/dispatcher-foundation/repo-layout-workflows.md) – normalize repos to the dispatcher `src` root and likely file families - [playbook-command-linkage.md](./references/dispatcher-foundation/playbook-command-linkage.md) – deterministic linkage from playbooks to MCP commands and tests - [ams-6-5-guardrails.md](./references/dispatcher-foundation/ams-6-5-guardrails.md) – AMS topology/variables/flush and immutable-file constraints - [public-docs-index.md](./references/dispatcher-foundation/public-docs-index.md) - [public-doc-citation-rules.md](./references/dispatcher-foundation/public-doc-citation-rules.md) - [mode-specific-verification-matrix.md](./references/dispatcher-foundation/mode-specific-verification-matrix.md) - [test-case-catalog.md](./references/dispatcher-foundation/test-case-catalog.md) - [change-risk-and-rollback-template.md](./references/dispatcher-foundation/change-risk-and-rollback-template.md) - [core-7-tools-reference.md](./references/dispatcher-foundation/core-7-tools-reference.md) - [request-router.md](./references/technical-advisory/request-router.md)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.