android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/android/android-concurrency/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The body is a concise, well-structured overview that correctly offloads executable code to a single one-level reference. Its main weakness is the absence of a sequenced workflow with validation checkpoints and the unfinished anchor section.

Suggestions

Inline one short executable snippet (e.g., a viewModelScope.launch with DispatcherProvider) so the body provides copy-paste-ready guidance without forcing a file read for the common case.

Remove or fill in the near-empty 'Canonical response anchors' section ('Additional task-grounded exact anchors: hardcode'), which currently reads as a stub and adds noise.

If a multi-step flow applies (e.g., diagnose scope/dispatcher misuse then validate), sequence it with explicit steps and a validation checkpoint to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge, but a couple of phrasings ('INJECT Dispatchers ... not hardcode') are slightly untight and the near-empty 'Canonical response anchors' section adds noise, keeping it just below the leanest anchor.	4 / 5
Actionability	The body gives concrete imperative rules but defers all executable code to references/implementation.md, so the body itself lacks copy-paste-ready code; it sits between high-level hints and fully executable guidance.	3 / 5
Workflow Clarity	Guidance is organized into clear categories (Structured Concurrency, Flow usage, Anti-Patterns) but there is no sequenced multi-step workflow or validation checkpoint, matching the anchor for steps present but checkpoints missing.	3 / 5
Progressive Disclosure	The body serves as an overview with a well-signaled one-level reference to references/implementation.md (a real file), and content is appropriately split; the stub 'Canonical response anchors' section is a minor organization gap.	4 / 5
	Total	14 / 20 Passed

Description

92%Weight 40%Scale 1-5

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, action-oriented, and clearly distinguishes this skill from related Android skills via explicit deferral language. It fully answers both what and when with natural trigger phrases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'coroutine scopes, lifecycle collection, and dispatcher injection' — with comprehensive coverage of the Android concurrency domain, matching the anchor for several specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ('Write correct coroutine scopes, lifecycle collection, and dispatcher injection') and when ('Use for suspend functions, coroutine scopes, and dispatcher mechanics'), with concrete trigger phrases and deferral guidance.	5 / 5
Trigger Term Quality	Strong natural terms ('suspend functions, coroutine scopes, and dispatcher mechanics') users would say, but lacks some synonyms and file extensions, stopping short of the comprehensive coverage anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Android-concurrency niche and explicitly defers overlapping concerns (ViewModel StateFlow/LiveData, Fragment lifecycle, persistence, unit tests) to other skills, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/android/android-concurrency/SKILL.md
Commit: 405cdd5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.