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.
59
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/android-retrofit/SKILL.mdQuality
Discovery
32%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 identifies a clear technical domain (Retrofit for Android) and lists relevant topics, but fails to provide explicit trigger guidance for when Claude should select this skill. It uses passive 'covers' language rather than active verbs describing concrete actions, and misses common user terms like 'API calls' or 'REST client'.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about making API calls in Android, setting up REST clients, or configuring network layers with Retrofit'
Include common user terms and variations: 'API calls', 'REST', 'network requests', 'web service', 'API client'
Replace 'Expert guidance on' and 'Covers' with active verbs describing concrete actions: 'Creates Retrofit service interfaces, configures OkHttp interceptors, integrates with Hilt dependency injection'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Retrofit, Android HTTP networking) and mentions several areas covered (service definitions, coroutines, OkHttp configuration, Hilt integration), but uses 'covers' and 'guidance' rather than listing concrete actions like 'create service interfaces' or 'configure interceptors'. | 2 / 3 |
Completeness | Describes what the skill covers but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms users might search for (Retrofit, HTTP, Android, coroutines, OkHttp, Hilt), but missing common variations like 'API calls', 'REST', 'network requests', 'API client', or 'web service'. | 2 / 3 |
Distinctiveness Conflict Risk | Retrofit is a specific library which helps distinguish it, but 'HTTP networking in Android' could overlap with other networking skills (Ktor, Volley, etc.). The Retrofit focus provides some distinctiveness but lacks explicit differentiating triggers. | 2 / 3 |
Total | 7 / 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 skill provides solid, actionable Retrofit guidance with excellent executable code examples covering common use cases. However, it could be more concise by removing explanatory preambles Claude doesn't need, and would benefit from a clearer setup workflow with validation steps rather than topic-based organization.
Suggestions
Remove explanatory sentences before code blocks (e.g., 'Retrofit allows dynamic URL updates') - the code examples are self-explanatory
Add a quick-start workflow section showing the sequence: 1) Add dependencies, 2) Create service interface, 3) Configure Hilt module, 4) Verify with a test call
Consider splitting advanced topics (interceptors, multipart uploads, error handling patterns) into separate reference files with clear links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient but includes some explanatory text that 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 throughout, covering service definitions, Hilt modules, and repository patterns. All code is copy-paste ready with proper annotations and syntax. | 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 process for setting up a complete networking layer, and no validation/verification steps for testing the implementation. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document with no references to external files for advanced topics like error handling strategies, testing, or interceptor patterns that could be split out. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
3f68e39
- Reviewed
Table of Contents
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.