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

symptom-hypothesis-matrix.mdskills/dispatcher/incident-response/references/incident-response/

Symptom -> Hypothesis Matrix (AMS, Core-7)

Use this table to form evidence-backed hypotheses quickly.

SymptomFirst ChecksLikely Dispatcher-Side CausesNext Action
502 spikemonitor_metrics, tail_logs, trace_requestrender timeout/routing mismatch, upstream instability indicators in logscompare failing vs healthy trace path; validate render/vhost config
403 increasetrace_request, tail_logsfilter-order regression, method/selector deny overlapmap matching rules and verify last-match behavior
MISS surgemonitor_metrics, inspect_cache, trace_requestcache rule bypass, invalidation blast radius too broad, docroot mismatchinspect cache object path and invalidation behavior
stale contentinspect_cache, trace_request, tail_logsflush/invalidation not applied, statfileslevel mismatch, stale headersverify invalidate path and stat file behavior
latency regressionmonitor_metrics, tail_logs, trace_requestredirect chains, increased backend dependency, reduced cacheabilitytrace hot URLs and compare stage behavior pre/post
wrong tier behavior (author/publish mismatch)trace_request, tail_logs, validatefarm ordering overlap, vhost-to-farm mismatch, tier variable driftcompare expected tier route vs actual farm match and fix overlap

Hypothesis discipline:

  1. Mark each hypothesis with confidence (low|medium|high).
  2. Attach at least one confirming or disconfirming check.
  3. Do not present hypothesis as root cause until corroborated.

skills

dispatcher

README.md

SKILL.md

README.md

tile.json