CtrlK
BlogDocsLog inGet started
Tessl Logo

troubleshoot-replication

Diagnose and fix common AEM 6.5 LTS replication issues including blocked queues, connectivity failures, and content distribution problems

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/aem/6.5-lts/skills/aem-replication/troubleshoot-replication/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete commands and paths and a clear diagnostic workflow, but it is a monolithic, verbose wall of text with redundant boilerplate and lacks progressive disclosure into separate reference files.

Suggestions

Add explicit validate-before/after checkpoints around destructive operations (rm -rf cache clear, clearing /var/replication/data, deleting /bin/replicate nodes) to strengthen feedback loops.

Split the per-issue deep-dives and Advanced Troubleshooting into reference files (e.g., references/common-issues.md, references/advanced.md) and keep SKILL.md as an overview with one-level-deep links.

Reduce repeated Symptoms/Diagnosis/Root-Causes/Solutions boilerplate and merge overlapping Preventive Measures, Best Practices, and Success Criteria sections to tighten the token budget.

DimensionReasoningScore

Conciseness

The ~1060-line body is concrete reference material rather than concept explanation, but it is padded with repeated Symptoms/Diagnosis/Solutions boilerplate across 12 issues and overlapping Preventive/Best-Practices/Success-Criteria sections, fitting the score-2 anchor of mostly efficient but could be tightened.

2 / 3

Actionability

It provides copy-paste-ready commands (curl, telnet, nc, keytool, grep), exact bundle names, exact repository paths and URIs, and XPath queries, matching the score-3 anchor for fully executable guidance.

3 / 3

Workflow Clarity

A clear 8-step diagnostic workflow, checklist, and per-issue diagnosis flow exist with verification in some places, but several destructive operations (rm -rf cache, clearing /var/replication/data, deleting /bin/replicate nodes) lack consistent validate-before/after checkpoints, capping workflow clarity at 2 per the destructive-operations guideline.

2 / 3

Progressive Disclosure

No bundle files exist and all 12 issues plus advanced/preventive/escalation material sit inline in a monolithic ~1060-line document with content that should be split into separate files, matching the score-2 anchor of structure present but inline content that should be separate.

2 / 3

Total

9

/

12

Passed

Description

67%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-scoped to a distinct AEM niche, but it lacks an explicit "Use when..." trigger clause and omits several common user phrasings, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when replication queues are stuck, content is missing on Publish, agents show red status, or you see 401/timeout errors.'

Include natural user phrasings like 'replication stuck', 'content not publishing', 'agent red/error', and '401 Unauthorized' to broaden trigger-term coverage.

Tighten 'content distribution problems' toward language users actually say, such as 'content not appearing on Publish'.

DimensionReasoningScore

Specificity

"Diagnose and fix common AEM 6.5 LTS replication issues including blocked queues, connectivity failures, and content distribution problems" names the domain plus multiple specific concrete issue types, matching the score-3 anchor for listing several specific actions.

3 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 with the "when" only implied.

2 / 3

Trigger Term Quality

It includes relevant natural terms like "replication", "blocked queues", and "connectivity failures", but misses common user phrasings ("replication stuck", "content not publishing", "agent red", "401"), fitting the score-2 anchor of partial coverage.

2 / 3

Distinctiveness Conflict Risk

"AEM 6.5 LTS replication" is a tightly scoped niche with distinct triggers unlikely to overlap with unrelated skills, matching the score-3 anchor for a clear niche.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1067 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
adobe/skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.