config-authoring

Plan and execute AMS Dispatcher config changes using Core-7 MCP tools.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill config-authoring-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-authoring
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/config-authoring
Command: npx skills add https://github.com/valithedge/etisalatedge --skill config-authoring-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Deterministic, MCP-tool-guided workflow for Dispatcher config authoring in AMS deployments.
  • Guardrails to enforce least-privilege, immutable-file boundaries, and structured verification across dispatcher blocks.
  • End-to-end support for authoring, review, validation, and rollback planning of .any, vhost, rewrite, cache, and filter configurations.

Quick Start

Normalize the repository to the Dispatcher src root and apply the recommended MCP tool chain to implement deterministic AMS configuration changes.

Frequently Asked Questions about config-authoring

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

FAQPage Schema
How do I safely author Dispatcher configuration changes for AMS deployments?

Author Dispatcher configuration changes for AMS deployments by enforcing least-privilege, immutable-file boundaries, and formal verification gates like validate, lint, and trace_request to ensure rollback readiness.

What are the immutable-file boundaries when modifying AEM Dispatcher vhost and filter files?

Immutable-file boundaries restrict modifications to AMS-specific dispatcher blocks such as .any, vhost, rewrites, cache, and filters, ensuring structural integrity and preventing unauthorized alterations to core configuration files.

How do I validate and lint Adobe Dispatcher .any configuration files before deployment?

Validate and lint Adobe Dispatcher .any configuration files using formal verification gates including sdk validation and lint checks, which produce auditable change evidence and ensure rollback readiness for AEM 6.5 LTS environments.

Does this Dispatcher config authoring workflow support AEM 6.5 LTS environments?

Yes, this Dispatcher config authoring workflow explicitly supports AEM 6.5 LTS environments, handling .any, vhost, rewrite, cache, and filter changes specifically for AMS deployments using guided MCP tool chains.

What's the best way to trace a request through Dispatcher cache and filter rules in AMS?

Trace requests through Dispatcher cache and filter rules in AMS using the trace_request and inspect_cache verification gates, which provide formal evidence of routing behavior and ensure configured guardrails are properly enforced.

Why does my Dispatcher configuration change fail validation after modifying rewrite rules?

Dispatcher configuration changes fail validation when modifications violate least-privilege principles or immutable-file boundaries, requiring coordination across dispatcher file families under the source root to pass formal lint and sdk verification gates.