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—not standalone MockWebServer or API-test setup.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized standards overview that delegates implementation to a single one-level-deep reference. Its main weakness is actionability and workflow clarity: the body states what to do without in-body executable patterns or validation checkpoints, leaning on the reference for the how.

Suggestions

Add a minimal executable snippet or two in the body (e.g., a suspend API interface signature and an OkHttp interceptor skeleton) so the core pattern is copy-paste ready without opening the reference.

Add a validation/checkpoint step to the setup workflow (e.g., 'Verify the client builds and a sample call resolves against MockWebServer before merging') to lift workflow clarity above 2.

Inline the concrete R8/ProGuard rules or certificate-pinning config (or a link to the exact section) rather than only naming the requirement, so the guidance is complete in itself.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point standards with no padding or explanation of concepts Claude already knows (no 'what Retrofit is' prose); every token earns its place, matching the lean-and-efficient anchor.	3 / 3
Actionability	Directives name concrete libraries and conditions ('@SerialName', 'isMinifyEnabled = true', 'cover 500, 401, 403') but the body contains no executable code and delegates key implementation details (interceptor setup, pinning config, R8 rule content) to the reference, fitting the 'some concrete guidance but incomplete / missing key details' anchor rather than the copy-paste-ready anchor.	2 / 3
Workflow Clarity	A numbered sequence (Configure Stack, Define Endpoints, Cross-Cutting Concerns) is present, but there are no validation checkpoints or error-recovery feedback loops, matching the 'steps listed but checkpoints missing or implicit' anchor rather than the explicit-validation anchor.	2 / 3
Progressive Disclosure	The body is a concise overview with well-signaled, one-level-deep references to a real references/implementation.md (verified present) for DTO/API examples, with content appropriately split and easy to navigate, matching the clear-overview anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is specific, complete, and distinctive, naming concrete actions, natural trigger terms, an explicit 'Use when' clause, and a negative carve-out to avoid overlap. It is a strong example of a well-scoped skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Integrate Retrofit, OkHttp, and Kotlinx Serialization', 'building API clients, adding interceptors, or configuring network security' — matching the multiple-specific-actions anchor; imperative voice avoids the first/second-person penalty.	3 / 3
Completeness	Explicitly answers both 'what' (type-safe API communication via Retrofit/OkHttp/Kotlinx Serialization) and 'when' via an explicit 'Use when ...' clause, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Natural developer-facing terms ('API clients', 'interceptors', 'network security', Retrofit, OkHttp) give good coverage of what a user would actually say, matching the good-coverage anchor rather than the jargon-only or partial-variation anchors.	3 / 3
Distinctiveness Conflict Risk	A clear Android networking niche plus an explicit negative carve-out ('not standalone MockWebServer or API-test setup') makes conflict with adjacent skills unlikely, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/android/android-networking/SKILL.md
Commit: 9f695e8

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.