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.
62
75%
Does it follow best practices?
Impact
—
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 well-crafted skill description that names specific technologies, concrete actions, and includes an explicit 'Use when...' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague. The description clearly carves out a distinct niche around Android networking with a specific tech stack.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Integrate Retrofit, OkHttp, and Kotlinx Serialization', 'type-safe API communication', 'building API clients', 'adding interceptors', 'configuring network security'. These are concrete, named technologies and actions. | 3 / 3 |
Completeness | Clearly answers both what ('Integrate Retrofit, OkHttp, and Kotlinx Serialization for type-safe API communication in Android') and when ('Use when building API clients, adding interceptors, or configuring network security') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Retrofit', 'OkHttp', 'Kotlinx Serialization', 'API clients', 'interceptors', 'network security', 'Android'. These are the exact terms developers use when working with Android networking. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific technology stack (Retrofit, OkHttp, Kotlinx Serialization) and Android platform focus. Unlikely to conflict with other skills unless there are multiple Android networking skills. | 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 concepts. However, it critically lacks any executable code examples in the body itself, making it purely descriptive rather than actionable. The referenced implementation file is not provided in the bundle, leaving the skill incomplete.
Suggestions
Add at least one concrete, executable code example in the body — e.g., a minimal Retrofit interface with a suspend function and Kotlinx Serialization DTO, so the skill is actionable even without the referenced file.
Include the referenced 'references/implementation.md' file in the bundle, or inline the most critical code snippets (OkHttp client setup with interceptors, certificate pinning config) directly in the SKILL.md.
Add a validation checkpoint for ProGuard/R8 rules — e.g., 'After enabling minification, verify API calls work in release build before shipping' — to improve workflow clarity for this destructive operation.
| 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 | There are no concrete code examples, executable commands, or copy-paste ready snippets anywhere in the body. All guidance is descriptive ('use X', 'implement Y') and defers actual implementation details to a referenced file that is not provided in the bundle. | 1 / 3 |
Workflow Clarity | The numbered sections (Configure, Define, Add) provide a reasonable sequence, but there are no validation checkpoints, no feedback loops for error recovery, and no explicit verification steps for operations like certificate pinning or ProGuard rule configuration. | 2 / 3 |
Progressive Disclosure | The skill references 'references/implementation.md' multiple times for detailed content, which is good structure. However, the bundle has no files provided, meaning the referenced file doesn't exist, and the same file is referenced for multiple distinct topics (DTOs, API examples, endpoint definitions) without clear section anchors. | 2 / 3 |
Total | 8 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
3df717f
- 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.