mirror of
https://github.com/adobe/skills.git
synced 2026-09-19 08:06:09 +08:00
yogesh-tessl
eb2d4f380d
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 🙏 Co-authored-by: Yogesh Rao <yogesh-tessl@users.noreply.github.com>