android-retrofit

Expert guidance on setting up and using Retrofit for type-safe HTTP networking in Android. Covers service definitions, coroutines, OkHttp configuration, and Hilt integration.

Quality

67%

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 ./.github/skills/concurrency_and_networking/android-retrofit/SKILL.md

Quality

Content

68%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 well-structured, actionable Retrofit reference with concrete executable Kotlin examples and a closing checklist. Its main weakness is that it reads as a topical manual rather than a sequenced workflow with validation checkpoints.

Suggestions

Tighten the section-intro sentences so they add rationale rather than restating the code that follows, pushing conciseness toward 5.

Define or stub the GitHubService used in the repository error-handling example (or note it as illustrative) so the actionability is fully self-contained.

Consider framing a short end-to-end workflow (define service -> configure OkHttp/Hilt -> call from repository -> handle errors) with an explicit validation checkpoint before the checklist to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence (no explaining of what coroutines/Hilt are), but several one-line section intros like 'Retrofit allows dynamic URL updates through replacement blocks and query parameters' partly restate what the immediately-following code already shows.	4 / 5
Actionability	Six complete, copy-paste-ready Kotlin blocks (service interfaces, Hilt module, repository) cover the common Retrofit cases, but the repository example references an undefined GitHubService.listRepos and domain types are assumed, leaving a minor gap.	4 / 5
Workflow Clarity	The content is organized as a topical reference (URL, body, headers, response, config, errors) rather than a sequenced multi-step workflow, and the only checkpoint is the trailing checklist; there are no explicit validation/feedback loops.	3 / 5
Progressive Disclosure	It is a single self-contained file with seven well-organized numbered sections and no nested or buried references; good structure with only minor organization gaps, though the ~140-line reference could arguably split annotation/API detail into a separate file.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly and specifically states what the skill covers using natural Android-networking terminology, but it omits any 'when to use this' trigger guidance, which caps completeness. It is otherwise well-targeted and largely distinct from sibling skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up or refactoring an Android network layer with Retrofit, or when the user mentions Retrofit, OkHttp, or Hilt networking.'

Consider naming the additional concrete capabilities (error handling, interceptors, JSON converters) to push specificity toward comprehensive coverage.

Include a common synonym such as 'REST client' or 'API layer' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete coverage areas ('service definitions, coroutines, OkHttp configuration, and Hilt integration') alongside 'setting up and using Retrofit for type-safe HTTP networking', which is more than 1-2 actions but not fully comprehensive (error handling, interceptors, converters not enumerated).	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	'Retrofit', 'Android', 'OkHttp', 'Hilt', and 'coroutines' are exactly the technical terms a developer would naturally say, giving good keyword coverage; a few natural synonyms (e.g., 'REST client', 'network layer', 'API calls') are missing.	4 / 5
Distinctiveness Conflict Risk	'Retrofit for type-safe HTTP networking in Android' is a clearly distinct niche with the 'Retrofit' trigger, but there is minor overlap risk with closely related sibling skills (OkHttp, Ktor, Volley, general Android networking).	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: new-silvermoon/awesome-android-agent-skills
Path: .github/skills/concurrency_and_networking/android-retrofit/SKILL.md
Commit: 82900ea

Reviewed: 1 day 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.