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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A well-organized, token-efficient standards overview that correctly pushes executable detail into a single real reference file. Its main gap is that the body carries no executable code itself and lacks explicit validation checkpoints in its workflow.

Suggestions

Add a minimal inline Kotlin snippet (e.g. a suspend API interface or the json.asConverterFactory(MediaType) line) so the body is actionable without requiring a file open.

Add an explicit verification checkpoint in the workflow, such as 'Confirm endpoints are suspend and errors are handled in the Repository before merging', to lift workflow clarity.

Move or annotate the 'Retrofit 2' / 'OkHttp 4' version pins into a version/compat note so the core standards stay version-agnostic.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet-pointed standards list that never explains what Retrofit/OkHttp are and assumes Claude's competence; every line earns its place. The only mild concern is the hardcoded 'Retrofit 2' / 'OkHttp 4' version numbers, but these are stable major versions rather than rapidly-rotating time-sensitive data.	3 / 3
Actionability	Concrete directives are present ('Use Kotlinx Serialization with @SerialName', 'All API calls must suspend functions', 'cover 500, 401, 403 error cases'), but the body itself contains no executable code — the copy-paste-ready Kotlin lives one level deep in references/implementation.md. This fits the 'concrete guidance but incomplete / not copy-paste ready in-body' anchor rather than the fully-executable anchor.	2 / 3
Workflow Clarity	The three numbered sections (Configure HTTP Stack → Define API Endpoints → Add Cross-Cutting Concerns) give a clear sequence, but there are no explicit validation or verification checkpoints, which matches the 'steps listed but checkpoints missing' anchor rather than the validation-driven anchor.	2 / 3
Progressive Disclosure	The body is a concise overview that delegates all code to a single, well-signaled, one-level-deep reference ([setup & wrappers](references/implementation.md)), which exists as a real file with the expected setup/DTO/API content. Content is appropriately split and navigation is easy.	3 / 3
	Total	10 / 12 Passed

Description

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.

A strong, third-person description that concretely names its libraries and capability, provides explicit 'Use when' triggers, and occupies a distinct Android-networking niche. No significant weaknesses.

Dimension	Reasoning	Score
Specificity	It names three specific concrete libraries ('Retrofit, OkHttp, and Kotlinx Serialization') and a precise capability ('type-safe API communication'), matching the 'lists multiple specific concrete actions' anchor; it is not vague like 'Helps with documents'.	3 / 3
Completeness	It states what the skill does (integrate the three libraries for type-safe API communication) and includes an explicit 'Use when building API clients, adding interceptors, or configuring network security' trigger clause, satisfying both the what and the when.	3 / 3
Trigger Term Quality	It surfaces natural terms an Android developer would actually say — 'API clients', 'interceptors', 'network security', 'Retrofit', 'OkHttp' — giving good coverage of likely user phrasings rather than jargon-only language.	3 / 3
Distinctiveness Conflict Risk	The Android-specific Retrofit/OkHttp/Kotlinx Serialization niche with named-library triggers is clearly distinguishable and unlikely to fire for unrelated skills, 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
Commit: 611f52a

Reviewed: 4 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.