feat: improve replication skill score from 52% to 87%#136
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @trieloff 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for the Cloud Service replication skill. Here's the before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | replication (cloud-service) | 52% | 87% | +35% | I picked this skill because it had the most room to grow across the repo — the baseline was 52%, lowest alongside `replication-orchestrator` (6.5 LTS). Since Cloud Service is the forward-looking runtime, it felt like the highest-signal place to contribute. <details> <summary>Changes made</summary> **Description improvements (biggest impact — 40% → 100%):** - Rewrote frontmatter description from a generic 2-line summary to a specific, action-oriented description listing concrete capabilities (publish, deactivate, delete, bulk activation, preview-tier targeting, sync/async, status checks, permissions, workflow steps, event handling) - Added explicit "Use when..." clause with seven trigger scenarios covering natural language terms users would say ("publish pages", "activate content", "check replication status") - Switched description from YAML block scalar to quoted string format - Added metadata.category field **Content improvements (42% → 73%):** - Removed "Architecture: How Replication Works in Cloud Service" section — Claude already understands AEM's Sling Content Distribution pipeline - Removed ReplicationActionType values table — these are self-evident from the linked Javadoc and the code examples - Moved Common Patterns (auto-publish on Content Fragment save, external cache purge after publication) to references/patterns.md for progressive disclosure, reducing the main SKILL.md by ~100 lines - Added a Service User setup pattern to the reference file for completeness - Condensed Best Practices section — removed verbose exception handling example, consolidated service user guidance into a concise paragraph with a link to the reference file - Net result: SKILL.md dropped from 744 to 592 lines with better structure **Unchanged skills:** - All other 88 skills left untouched — many are already scoring well (replicate-content at 100%, workflow-development at 99%, best-practices at 94%) </details> I also stress-tested your replication skill against a few real-world task evals and it held up really well on bulk content activation with automatic transactional bucketing above the 100-path threshold. Kudos for that. Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch — just saw room for improvement and wanted to contribute. Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide (https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me — @yogesh-tessl (https://github.com/yogesh-tessl) — if you hit any snags. Thanks in advance 🙏
yogesh-tessl
requested review from
Himanich,
abhishekgarg18,
akankshajain18,
pkumargaddam and
rombert
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey @trieloff 👋
you're already running tessl skill review as a quality gate, which is great to see. The depth across AEM, App Builder, and Creative Cloud with proper plugin manifests for each makes this one of the most complete skill collections out there.
ran your skills through
tessl skill reviewat work and found some targeted improvements for the Cloud Service replication skill. Here's the before/after:picked this skill because it had the most room to grow across the repo, the baseline was 52%, lowest alongside
replication-orchestrator(6.5 LTS). Since Cloud Service is the forward-looking runtime, it felt like the highest-signal place to contribute.Changes made
Description improvements (biggest impact - 40% → 100%):
Content improvements (42% → 73%):
Unchanged skills:
quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.
if you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.