CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

adobe/aem-6-5-lts

All AEM 6.5 LTS skills: Workflow model design, development, triggering, launchers, debugging, and triaging; Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening; Replication agent configuration, content activation, API usage, and troubleshooting for AEM 6.5 LTS and AMS environments; Jackrabbit Oak query/index tuning (property, Lucene index definitions); and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

SKILL.mdskills/dispatcher/performance-tuning/

name:
performance-tuning
description:
Optimize performance of the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration for AEM 6.5 / AMS workflows only, with AMS-specific baseline and runtime verification.
license:
Apache-2.0
compatibility:
Requires Dispatcher MCP for AMS (`AEM_DEPLOYMENT_MODE=ams`) or AMS Dispatcher MCP SDK (pre-set to `ams`).
allowed-tools:
validate lint sdk trace_request inspect_cache monitor_metrics tail_logs
metadata:
{"mcp-tool-contract":"core-7-tools"}

Dispatcher Performance Tuning (AMS)

Improve cache efficiency, latency, and throughput for AMS deployments that use 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:

  • validate
  • lint
  • sdk
  • trace_request
  • inspect_cache
  • monitor_metrics
  • tail_logs

Workflow

  1. Capture baseline metrics and cache evidence.
  2. Apply AMS 6.5 guardrails (tier boundaries, variable-driven config, flush ACL safety) to candidate optimizations.
  3. Prioritize low-risk/high-impact changes.
  4. Apply minimal edits.
  5. Verify with validate, lint, and sdk.
  6. Compare before/after runtime evidence.

Verification Scope Selection

Use shared references to select optimization evidence depth:

  • mode-specific-verification-matrix.md
  • test-case-catalog.md

Output Contract

Always return:

  • baseline metrics snapshot
  • prioritized optimization list with impact/risk
  • changed files and intent
  • executed checks + before/after evidence
  • selected test IDs and outcomes
  • rollback plan and open risks

Guardrails

  • Do not claim improvement without measurable comparison.
  • Keep high-risk tuning opt-in unless user explicitly requests it.
  • Keep AMS assumptions explicit for each recommendation batch.

References

skills

dispatcher

README.md

SKILL.md

README.md

tile.json