feat: improve android-coroutines skill score (59% → 90%)#938
Open
yogesh-tessl wants to merge 1 commit into
Open
feat: improve android-coroutines skill score (59% → 90%)#938yogesh-tessl wants to merge 1 commit into
yogesh-tessl wants to merge 1 commit into
Conversation
Hey @davidliu 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `android-coroutines`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | android-coroutines | 59% | 90% | +31% | | android-testing | 59% | 59% | — | | kotlin-concurrency-expert | 82% | 82% | — | | gradle-build-performance | 86% | 86% | — | | android-gradle-logic | 59% | 59% | — | I picked `android-coroutines` because it had the most improvement headroom among the core skills, and coroutines are central to the SDK's async real-time communication patterns. <details> <summary>Changes made to <code>android-coroutines</code></summary> - **Rewrote frontmatter description** with explicit "Use when..." clause and natural trigger terms (`suspend functions`, `Flow`, `StateFlow`, `GlobalScope`, `callbackFlow`, `repeatOnLifecycle`) so the skill gets selected reliably - **Added a 4-step implementation workflow** (Identify scope → Wire data layer → Connect UI → Verify) with concrete validation steps including `./gradlew test` and `./gradlew detektDebug`, plus a diagnostic checklist for common failure modes - **Removed meta-sections** ("Responsibilities" and "Applicability") that restated the description without adding actionable value — saves tokens without losing any guidance - **Tightened rule prose** — trimmed explanatory text Claude already knows (main-safety rationale, cooperative cancellation basics) while keeping all rules and code patterns intact Net result: 29 lines removed, 11 added — a smaller, sharper skill file. </details> I also stress-tested your `kotlin-concurrency-expert` skill against a few real-world task evals and it held up really well on diagnosing `CancellationException` swallowing in nested `runCatching` blocks. 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
MaxHeimbrock,
davidliu and
xianshijing-lk
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
2 participants
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 @davidliu 👋
ran your skills through
tessl skill reviewat work and found some targeted improvements forandroid-coroutines. Here's the before/after:picked
android-coroutinesbecause it had the most improvement headroom among the core skills, and coroutines are central to the SDK's async real-time communication patterns.Changes made to
android-coroutinessuspend functions,Flow,StateFlow,GlobalScope,callbackFlow,repeatOnLifecycle) so the skill gets selected reliably./gradlew testand./gradlew detektDebug, plus a diagnostic checklist for common failure modesNet result: 29 lines removed, 11 added - a smaller, sharper skill file.
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.