Agent skill

Config Authoring

Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM 6.5 LTS environments only.

Apache-2.0Auto-check passed

Install Config Authoring

skills CLI

$ npx skills add adobe/skills --skill config-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install adobe/skills config-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/aem/6.5-lts/skills/dispatcher/config-authoring .claude/skills/config-authoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "config-authoring" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring into .claude/skills/config-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-authoring", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add adobe/skills --skill config-authoring -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install adobe/skills config-authoring --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/aem/6.5-lts/skills/dispatcher/config-authoring .agents/skills/config-authoring && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "config-authoring" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring into .agents/skills/config-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-authoring", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add adobe/skills --skill config-authoring -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install adobe/skills config-authoring --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/aem/6.5-lts/skills/dispatcher/config-authoring .cursor/skills/config-authoring && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "config-authoring" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring into .cursor/skills/config-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-authoring", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/adobe/skills.git --path plugins/aem/6.5-lts/skills/dispatcher/config-authoring

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add adobe/skills --skill config-authoring -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install adobe/skills config-authoring --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/aem/6.5-lts/skills/dispatcher/config-authoring .gemini/skills/config-authoring && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "config-authoring" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring into .gemini/skills/config-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-authoring", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install adobe/skills config-authoring

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add adobe/skills --skill config-authoring -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/aem/6.5-lts/skills/dispatcher/config-authoring .github/skills/config-authoring && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "config-authoring" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring into .github/skills/config-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-authoring", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add adobe/skills --skill config-authoring -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install adobe/skills config-authoring --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/aem/6.5-lts/skills/dispatcher/config-authoring .opencode/skills/config-authoring && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "config-authoring" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/6.5-lts/skills/dispatcher/config-authoring into .opencode/skills/config-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "config-authoring", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: config-authoring
GitHub stars: 195
Token cost: ~1.4k tokens
SKILL.md length: 293 words
Files: 17 (incl. references)
Skills in repo: 105
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM 6.5 LTS environments only.

SKILL.md covers Variant Scope, MCP Tool Contract, Workflow and Verification Scope Selection, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Config Authoring is an agent skill from adobe/skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including reference files (for example `references/config-authoring/config-patterns.md`, `references/config-authoring/config-scenario-playbooks.md` and `references/config-authoring/mcp-tool-orchestration.md`). Compatibility notes: Requires Dispatcher MCP for AMS (AEMDEPLOYMENTMODE=ams) or AMS Dispatcher MCP SDK (pre-set to ams).

It works with Adobe Experience Manager. The repository describes itself as: Adobe Skills for Agents. The licence is Apache-2.0.

Example prompts

“/config-authoring”

Requirements

Compatibility (from SKILL.md): Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`).
Pre-approved tools (allowed-tools): validate, lint, sdk, trace_request, inspect_cache, monitor_metrics, tail_logs

What it can do on your machine

Read from SKILL.md and the folder at commit cbc9952. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- validate
- lint
- sdk
- trace_request
- inspect_cache
- monitor_metrics
- tail_logs
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`).
From compatibility in the SKILL.md frontmatter.

Context cost

Config Authoring loads about 1.4k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 293 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~57
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from adobe/skills at commit cbc9952, republished under its Apache-2.0 licence (© adobe). 293 words, ~1,366 tokens.

Download SKILL.mdSave it as .claude/skills/config-authoring/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.

name: config-authoring
description: 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.
allowed-tools: validate, lint, sdk, trace_request, inspect_cache, monitor_metrics, tail_logs
compatibility: Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`).
license: Apache-2.0
metadata.mcp-tool-contract: core-7-tools

Dispatcher Config Authoring (AMS)

Design minimal, deterministic changes for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM 6.5/AMS, then verify with MCP evidence.

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:

validate
lint
sdk
trace_request
inspect_cache
monitor_metrics
tail_logs

Workflow

text

AMS Config Progress
- [ ] 1) Confirm scope and acceptance criteria; if the repo layout is unclear, normalize it with `repo-layout-workflows.md`
- [ ] 2) Apply AMS 6.5 guardrails for tier routing, variables, flush ACL, and immutable boundaries
- [ ] 3) Decompose target URLs (path/selectors/extension/suffix) and use that model for all URL-based rules—filters, cache rules, etc.—using `/path`, `/selectors`, `/extension`, `/suffix` or aligned globs (not raw `/url`) where applicable; then design complete section-level edits
- [ ] 4) Update config with least-privilege defaults (produce final merged section, not isolated rule snippets)
- [ ] 5) Run static checks: validate -> lint (deep/order-aware when filters changed)
- [ ] 6) Run SDK checks: `sdk({"action":"check-files","config_path":"<dispatcher src path>"})`, `sdk({"action":"diff-baseline","config_path":"<dispatcher src path>"})` as needed
- [ ] 7) Run runtime verification in host-path/log environment
- [ ] 8) Return diff, evidence table, risk/rollback, and citations

Verification Scope Selection

Use the shared references to select the minimum evidence set:

Output Contract

Always include:

files changed + intent
exact insertion location and final merged section content for each edited block
checks executed + evidence
selected test IDs
risk/rollback plan
residual risks and next checks

Feature cross-boundary (Playbook G: auth_checker)

Permission-sensitive caching (/auth_checker) is end-to-end: it requires both Dispatcher config and an AEM servlet. When implementing Playbook G from scratch, create or verify the auth-check servlet in the project core bundle (path /bin/permissioncheck, HEAD/GET, 200 or 403) and allowlist it on publish; then add the /auth_checker block, filter allow for the endpoint, and /allowAuthorized "1" in /cache. See config-scenario-playbooks.md Playbook G and reference-snippets.md.

Guardrails

Do not weaken deny-by-default security posture without explicit user approval.
Do not claim runtime verification if host-path/log prerequisites were missing.
Keep changes minimal and scoped.

References

config-patterns.md
config-scenario-playbooks.md – high-value development scenarios adapted from broader MCP surfaces to core-7 execution
reference-snippets.md – reusable starter snippets for consistent config authoring
validation-playbook.md
mcp-tool-orchestration.md
For runtime prompts and troubleshooting scenarios (tail_logs, trace_request, monitor_metrics, inspect_cache), use the incident-response skill reference runtime-prompts-and-troubleshooting-scenarios.md when incident triage is needed.
quick-start-execution-path.md – single entry path for new users and broad requests
repo-layout-workflows.md – map the user repo to the dispatcher src root and likely file families
playbook-command-linkage.md – convert selected playbooks into exact MCP command chains
ams-6-5-guardrails.md
mode-specific-verification-matrix.md
test-case-catalog.md
change-risk-and-rollback-template.md
public-doc-citation-rules.md
public-docs-index.md
core-7-tools-reference.md

Files

SKILL.md and 16 other files (references) in plugins/aem/6.5-lts/skills/dispatcher/config-authoring of adobe/skills.

SKILL.md
references/config-authoring/config-patterns.md
references/config-authoring/config-scenario-playbooks.md
references/config-authoring/mcp-tool-orchestration.md
references/config-authoring/reference-snippets.md
references/config-authoring/validation-playbook.md
references/dispatcher-foundation/README.md
references/dispatcher-foundation/ams-6-5-guardrails.md
references/dispatcher-foundation/change-risk-and-rollback-template.md
references/dispatcher-foundation/core-7-tools-reference.md
references/dispatcher-foundation/mode-specific-verification-matrix.md
references/dispatcher-foundation/playbook-command-linkage.md
references/dispatcher-foundation/public-doc-citation-rules.md
references/dispatcher-foundation/public-docs-index.md
references/dispatcher-foundation/quick-start-execution-path.md
references/dispatcher-foundation/repo-layout-workflows.md
references/dispatcher-foundation/test-case-catalog.md

Open the folder on GitHubat commit cbc9952

Compare with similar skills

Config Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Config Authoring compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Config Authoring this skilladobe/skills	195	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Sanity Migrationsanity-io/agent-toolkit	187	—	~1.4k	Automated safety check: Pass	MIT	yesterday
Content Management Systemsgithub/awesome-copilot	40k	1 repos	~1.3k	Automated safety check: Pass	MIT	today
App Builder UI ScaffolderNeverSight/learn-skills.dev	216	1 repos	~2.2k	Automated safety check: Pass	Apache-2.0	yesterday
Authoring Analysismajiayu000/claude-skill-registry	666	2 repos	~3.1k	Automated safety check: Pass	MIT	today
Block Inventorymajiayu000/claude-skill-registry	666	1 repos	~2.1k	Automated safety check: Pass	MIT	today

Similar skills

Sanity Migration
sanity-io/agent-toolkit
Official
Plans, implements, and reviews migrations from other CMSes and content systems into Sanity.
187 GitHub stars~1.4k tokensUpdated yesterday
Documents & OfficeAuto-check passed
Content Management Systems
github/awesome-copilot
Official
Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and…
40k GitHub starsUsed in 1 repo~1.3k tokens
Sales & SupportAuto-check passed
App Builder UI Scaffolder
NeverSight/learn-skills.dev
Generates React Spectrum UI code for Adobe Experience Cloud Shell apps and AEM UI Extensions from annotated patterns.
216 GitHub starsUsed in 1 repo~2.2k tokens
Frontend & DesignAuto-check passed
Authoring Analysis
majiayu000/claude-skill-registry
Analyze content sequences and determine authoring approach (default content vs blocks).
666 GitHub starsUsed in 2 repos~3.1k tokens
Auto-check passed
Block Inventory
majiayu000/claude-skill-registry
Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring.
666 GitHub starsUsed in 1 repo~2.1k tokens
Auto-check passed
Identify Page Structure
majiayu000/claude-skill-registry
Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import.
666 GitHub starsUsed in 1 repo~1.5k tokens
Auto-check passed

Questions about Config Authoring

What does Config Authoring do?

Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM 6.5 LTS environments only. Config Authoring is an agent skill from adobe/skills.5 LTS environments only.

How do I install Config Authoring in Claude Code?

Run `npx skills add adobe/skills --skill config-authoring -a claude-code`. Or copy the skill folder (plugins/aem/6.5-lts/skills/dispatcher/config-authoring in adobe/skills) into .claude/skills/config-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Config Authoring in Codex?

Run `npx skills add adobe/skills --skill config-authoring -a codex`. Or copy the skill folder (plugins/aem/6.5-lts/skills/dispatcher/config-authoring in adobe/skills) into .agents/skills/config-authoring in your project. Codex loads it when a task matches its description.

Can I use Config Authoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adobe/skills --skill config-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/config-authoring, .gemini/skills/config-authoring, .github/skills/config-authoring and .opencode/skills/config-authoring in your project.

What does Config Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: Config Authoring is instructions for the agent only. Its frontmatter pre-approves these tools: validate, lint, sdk, trace_request, inspect_cache, monitor_metrics, tail_logs. Compatibility (from SKILL.md): Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`)..

Does Config Authoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Config Authoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Config Authoring use?

Config Authoring is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Config Authoring use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Config Authoring?

Skills that share tags, products or a category with Config Authoring: Sanity Migration (sanity-io/agent-toolkit, 187 stars), Content Management Systems (github/awesome-copilot, 40k stars), App Builder UI Scaffolder (NeverSight/learn-skills.dev, 216 stars) and Authoring Analysis (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Config Authoring?

adobe (a GitHub organization) maintains it in adobe/skills, which has 195 GitHub stars. The repository holds 105 skills in this directory. The repository was last updated on October 6, 2026.

Source: adobe/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Config Authoring

Facts

At a glance

What it does

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Dispatcher Config Authoring (AMS)

Variant Scope

MCP Tool Contract

Workflow

Verification Scope Selection

Output Contract

Feature cross-boundary (Playbook G: auth_checker)

Guardrails

References

Files

Compare with similar skills

Similar skills

More from adobe/skills

Related

Questions about Config Authoring