Expert guidance on setting up and using Retrofit for type-safe HTTP networking in Android. Covers service definitions, coroutines, OkHttp configuration, and Hilt integration.
Install with Tessl CLI
npx tessl i github:new-silvermoon/awesome-android-agent-skills --skill android-retrofit67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
54%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 effectively identifies its technical niche with good keyword coverage for the Retrofit/Android ecosystem, making it distinctive. However, it reads more like a topic list than actionable guidance, and critically lacks any 'Use when...' clause to help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Retrofit setup, API client configuration, or type-safe HTTP calls in Android'
Convert topic areas into concrete actions: instead of 'Covers service definitions', use 'Define API service interfaces, configure interceptors, handle API responses'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Retrofit, Android HTTP networking) and mentions several areas (service definitions, coroutines, OkHttp configuration, Hilt integration), but these are topic areas rather than concrete actions. Missing action verbs like 'create', 'configure', 'debug'. | 2 / 3 |
Completeness | Describes what it covers but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'Retrofit', 'HTTP networking', 'Android', 'coroutines', 'OkHttp', 'Hilt' are all terms developers would naturally use when seeking help with this technology stack. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Retrofit specifically for Android. The combination of Retrofit + Android + specific integrations (Hilt, OkHttp, coroutines) creates a clear, distinct trigger profile unlikely to conflict with general Android or networking skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill with excellent actionable code examples covering Retrofit's key features. The main weaknesses are minor verbosity in explanatory text and lack of a clear sequential workflow for setting up networking from scratch. The checklist is a good addition but doesn't compensate for missing integration guidance.
Suggestions
Remove explanatory sentences like 'Retrofit allows dynamic URL updates' and 'You can send objects as JSON bodies' - lead directly with the annotations/patterns
Add a brief 'Setup Order' section at the top showing the recommended sequence: 1) Add dependencies, 2) Define service interfaces, 3) Configure Hilt module, 4) Inject into repository
Consider splitting detailed error handling patterns and multipart upload examples into a separate ADVANCED.md file with clear links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient but includes some explanatory text Claude already knows (e.g., 'Retrofit allows dynamic URL updates', 'You can send objects as JSON bodies'). The bullet point explanations before code blocks add minor verbosity. | 2 / 3 |
Actionability | Provides fully executable Kotlin code examples that are copy-paste ready. Each section includes concrete, working code with proper annotations, types, and realistic implementations. | 3 / 3 |
Workflow Clarity | Content is organized by topic rather than workflow sequence. The checklist at the end helps, but there's no clear step-by-step setup process or validation checkpoints for integrating Retrofit into a project. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one file. For a skill of this length (~120 lines), advanced topics like error handling patterns or multipart uploads could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.