android-networking
Integrate Retrofit, OkHttp, and Kotlinx Serialization for type-safe API communication in Android. Use when building API clients, adding interceptors, or configuring network security. (triggers: **/*Api.kt, **/*Service.kt, **/*Client.kt, Retrofit, OkHttpClient, @GET, @POST)
80
75%
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 ./skills/android/android-networking/SKILL.mdQuality
Discovery
100%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 skill description that clearly identifies the specific technology stack (Retrofit, OkHttp, Kotlinx Serialization), concrete use cases (API clients, interceptors, network security), and includes rich trigger terms covering file patterns and annotations. It follows third-person voice and provides both 'what' and 'when' guidance effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete technologies (Retrofit, OkHttp, Kotlinx Serialization) and actions (type-safe API communication, building API clients, adding interceptors, configuring network security). | 3 / 3 |
Completeness | Clearly answers 'what' (integrate Retrofit, OkHttp, Kotlinx Serialization for type-safe API communication) and 'when' (building API clients, adding interceptors, configuring network security) with explicit trigger patterns. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms including library names (Retrofit, OkHttpClient), file patterns (*Api.kt, *Service.kt, *Client.kt), and HTTP annotations (@GET, @POST) that users would naturally reference when working on Android networking. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Android-specific networking libraries and file patterns; unlikely to conflict with other skills due to the narrow focus on Retrofit/OkHttp/Kotlinx Serialization stack. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, correctly assuming Claude's familiarity with Android networking libraries. However, it critically lacks any executable code examples in the main file—all concrete guidance is deferred to a single reference file. The workflow is sequenced but missing validation checkpoints for security-sensitive operations like certificate pinning.
Suggestions
Add at least one minimal, executable code example inline (e.g., a basic Retrofit interface with a suspend function and OkHttpClient builder) so the skill is actionable without requiring the reference file.
Split the single reference link into distinct files or sections for different concerns (e.g., separate links for DTO examples, interceptor setup, certificate pinning, and testing with MockWebServer).
Add a validation/verification step for certificate pinning configuration and ProGuard rules, such as 'Test pinning by running against a staging server and verifying connection failures with wrong pins.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Retrofit, OkHttp, or Kotlinx Serialization are, assumes Claude's competence with these libraries, and every bullet point conveys a specific, non-obvious instruction. | 3 / 3 |
Actionability | The skill provides no concrete code examples, no executable snippets, and no specific commands. Everything is described at a high level ('use Retrofit 2 with OkHttp 4', 'implement Certificate Pinning') without showing how. All concrete guidance is deferred to a reference file. | 1 / 3 |
Workflow Clarity | The numbered sections (Configure, Define, Add Concerns) provide a reasonable sequence, but there are no validation checkpoints, no feedback loops for error recovery, and no explicit verification steps for security-sensitive operations like certificate pinning configuration. | 2 / 3 |
Progressive Disclosure | There is a reference file linked for implementation details, which is good progressive disclosure structure. However, the same reference file is linked for multiple different purposes (setup, DTOs, API examples, endpoint definitions), making navigation unclear. The main file also lacks any inline code to serve as a quick-start, forcing the reader to always follow the reference. | 2 / 3 |
Total | 8 / 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.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.