config-authoring

Configure and harden Adobe AEM Cloud Dispatcher and HTTPD configurations.

1|Updated Apr 14, 2026

Search Tags:#validation #configuration #mcp #cloud #aem #guardrails #dispatcher

Ready to run

npx skills add https://github.com/adobe/aem-auth-demo --skill config-authoring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: config-authoring
Source: https://github.com/adobe/aem-auth-demo/tree/main/.agents/skills/config-authoring
Command: npx skills add https://github.com/adobe/aem-auth-demo --skill config-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM as a Cloud Service environments only. Use for .any, vhost, rewrite, cache, and filter changes.

Core Features & Use Cases

Create, modify, review, and harden Dispatcher and Apache HTTPD config for AEMaaCS cloud environments.
Enforce cloud guardrails around vhosts, rewrites, filters, and cache rules to ensure consistent, secure deployments.
Provide repeatable playbooks and validation steps that reduce drift and accelerate compliant releases.

Quick Start

Start by normalizing the dispatcher source root, then apply the chosen playbook and run the MCP toolchain for static and runtime verification.

Frequently Asked Questions about config-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I harden Dispatcher configuration for AEM as a Cloud Service?▼

Harden Dispatcher configuration for AEM Cloud by applying guardrails to vhosts, rewrites, filters, and cache rules, then verifying changes through static checks, lint, and runtime tracing to ensure compliant deployments.

What is the best way to validate AEM Dispatcher rules before cloud deployment?▼

The best way to validate AEM Dispatcher rules is to normalize the dispatcher source root, apply the necessary configuration playbooks, and run the MCP toolchain for static validation, lint, and SDK checks before deployment.

Does this approach support Apache HTTPD vhost and rewrite modifications for AEMaaCS?▼

Yes, it supports creating, modifying, and reviewing Apache HTTPD vhosts, rewrites, cache, and filter configurations specifically within AEM as a Cloud Service environments to enforce cloud guardrails.

How do I analyze configuration drift in AEM Dispatcher?▼

Analyze configuration drift by normalizing the dispatcher source root and applying validation playbooks that run static checks and runtime tracing to detect and resolve deviations from cloud guardrails.

Can I use .any configuration files for Dispatcher filters in cloud environments?▼

Yes, you can use .any configuration files to create and modify Dispatcher filters and cache rules in AEM as a Cloud Service, ensuring all changes pass static validation and enforce cloud guardrails.

Why does my Dispatcher configuration fail validation during AEM cloud deployment?▼

Dispatcher configuration fails validation when vhosts, rewrites, filters, or cache rules violate cloud guardrails, requiring static checks, drift analysis, and linting to identify and resolve the non-compliant rules.