android-networking-retrofit-okhttp
Build Android networking stacks with Retrofit, OkHttp, interceptors, API contracts, and resilient error handling.
61
52%
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-networking-retrofit-okhttp/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and trigger term coverage, naming concrete Android networking technologies that developers would naturally reference. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The domain is distinctive enough to avoid conflicts with other skills.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Android networking, REST API integration, Retrofit setup, OkHttp configuration, or network error handling in Android apps.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'Retrofit, OkHttp, interceptors, API contracts, and resilient error handling' — these are all concrete, named capabilities within the Android networking domain. | 3 / 3 |
Completeness | The 'what' is clearly answered (build Android networking stacks with specific technologies), but there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'Retrofit', 'OkHttp', 'interceptors', 'API contracts', 'error handling', 'Android', 'networking'. These are terms developers naturally mention when seeking help with Android networking. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Android-specific networking libraries (Retrofit, OkHttp) and related concepts (interceptors, API contracts) creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a generic template that was minimally customized for Android networking with Retrofit/OkHttp. It lacks any concrete code examples, specific Retrofit annotations, OkHttp interceptor implementations, or actionable configuration guidance. The workflow, guardrails, and anti-patterns are so abstract they could apply to nearly any Android data layer topic, providing little value for the specific task of building Retrofit/OkHttp networking stacks.
Suggestions
Add concrete, executable code examples: a Retrofit interface definition with annotations, an OkHttp client builder with interceptors, and an error-handling/mapping implementation.
Replace the generic workflow with Retrofit/OkHttp-specific steps: define API interface → configure OkHttpClient with interceptors → build Retrofit instance → implement error mapping → write integration test, with explicit validation at each step.
Remove or replace the Volley reference (irrelevant to Retrofit/OkHttp) and add links to Square's official Retrofit and OkHttp documentation.
Include a concrete example of an interceptor (e.g., auth token injection, logging, retry) with copy-paste-ready Kotlin code rather than just referencing test commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content avoids explaining basic concepts Claude already knows, but includes generic boilerplate sections (Guardrails, Anti-Patterns) that are largely common knowledge for Android development and don't add Retrofit/OkHttp-specific value. The workflow steps are abstract and could apply to almost any Android data layer skill. | 2 / 3 |
Actionability | Despite being about building networking stacks with Retrofit and OkHttp, there is zero executable code—no Retrofit interface definitions, no OkHttp interceptor examples, no dependency declarations, no concrete API contract modeling. The guidance is entirely abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | The workflow steps are vague and generic ('Model contracts explicitly', 'Apply the recommended pattern') with no specific sequencing for Retrofit/OkHttp setup, no validation checkpoints for network configuration, and no feedback loops for error recovery. The example commands reference project directories but don't explain what they validate or how to interpret results. | 1 / 3 |
Progressive Disclosure | The skill references handoff skills and official references, providing some structure. However, there are no linked detail files for advanced topics like interceptor chains, error mapping strategies, or serialization configuration. The references include Volley documentation which seems misplaced for a Retrofit/OkHttp skill. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- krutikJain/android-agent-skills
- Commit
c5bf673
- 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.