config-authoring

Create and validate Adobe Dispatcher and Apache HTTPD configuration changes for AEM as a Cloud Service.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill config-authoring-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: config-authoring
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/config-authoring
Command: npx skills add https://github.com/aemgdc/aemdev --skill config-authoring-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Editing Dispatcher filters, cache rules, vhosts, and rewrites in AEM as a Cloud Service is error-prone: a wrong filter order, a broken include, or a rewrite that intercepts probe paths can block deployments or take down a site. This Skill guides minimal, guardrail-compliant config changes and verifies them with MCP tool evidence before release. ## Core Features & Use Cases - Guardrailed config authoring: Applies AEMaaCS cloud guardrails (immutable files, symlink topology, required wildcard ServerAlias coverage, reserved probe paths) before proposing any .any, vhost, rewrite, cache, or filter edit. - Deterministic verification workflow: Sequences the core-7 MCP tools (validate, lint, sdk, trace_request, inspect_cache, monitor_metrics, tail_logs) with a verification matrix and test-case catalog so every change ships with evidence. - Scenario playbooks: Provides 15 playbooks covering new site baselines, headless/API enablement, multi-host routing, cache invalidation tuning, permission-sensitive caching with /auth_checker, CORS, GraphQL persisted queries, and CI pre-deploy gates. - Use Case: When adding a new public API route, the Skill decomposes the URL into path/selectors/extension/suffix, produces the final merged /filter section with deny-by-default posture, runs validate and lint, and traces one allowed and one denied request as proof. ## Quick Start Ask the assistant to add a cache rule or filter allow for a specific URL in your dispatcher/src folder and have it validated against AEMaaCS cloud guardrails.

Frequently Asked Questions about config-authoring

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

FAQPage Schema
How do I add a filter allow rule in AEM Dispatcher cloud config?▼

Decompose the target URL into path, selectors, extension, and suffix, then add an explicit allow rule after the deny-by-default baseline in filters.any. Remember the last matching filter wins, so place targeted denies after broad allows, then run validate and lint before tracing a sample request.

How do I set up permission-sensitive caching with auth_checker in Dispatcher?▼

First create an AEM servlet at /bin/permissioncheck that returns 200 or 403 based on session read permission, and allowlist it on publish. Then add the /auth_checker block to the farm, set /allowAuthorized "1" in /cache, and allow only GET/HEAD to the endpoint in filters.

Does this skill support AMS or on-premise Dispatcher configurations?▼

No, this skill is scoped to AEM as a Cloud Service only. It enforces cloud-specific guardrails such as immutable managed files, enabled_farms/enabled_vhosts symlink topology, and required *.adobeaemcloud.net and *.adobeaemcloud.com ServerAlias coverage.

Why does the Dispatcher validator fail on my cloud config?▼

Common failures include missing enabled farms or vhosts, includes pointing to unknown file locations, ServerName set to "*", and invalid statfileslevel values. The skill maps these validator signatures to exact file edits and corroborates with sdk check-files and diff-baseline.

What verification is required before deploying Dispatcher cache changes?▼

Run validate and lint statically, plus sdk check-files and diff-baseline for drift. For runtime proof, use inspect_cache on a cacheable URL and monitor_metrics for hit-ratio trends, and record any skipped runtime checks explicitly.