CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A tight, well-organized standards skill that delegates executable code to a single clearly-signaled reference file. The main improvement area is actionability, since the body itself contains no inline copy-paste code.

Suggestions

Add one short inline Retrofit setup snippet or a minimal suspend API interface example in the body so the skill is actionable without opening the reference.

Consider a one-line validation checkpoint for the R8/ProGuard and Certificate Pinning directives (e.g. how to confirm rules survive minification) to strengthen workflow clarity.

Optionally clarify the Retrofit 2 / OkHttp 4 version stance (pinned vs. minimum) to avoid a future time-sensitivity concern.

DimensionReasoningScore

Conciseness

Lean bullet structure with no concept re-explanation or padding—e.g. 'All API calls must suspend functions', 'No Raw Converter Factory: Explicitly set "application/json" MediaType'—every token earns its place and assumes Claude's competence.

5 / 5

Actionability

Concrete, specific directives (Retrofit 2/OkHttp 4, @SerialName, Bearer token interceptors, R8/ProGuard when isMinifyEnabled, MockWebServer covering 500/401/403), though copy-paste code is deferred to the reference rather than shown inline in the body.

4 / 5

Workflow Clarity

Sections are logically ordered (HTTP stack → endpoints → cross-cutting → anti-patterns) with unambiguous directives; as a standards/reference skill rather than a destructive or batch operation, no validation feedback loop is required, though it is checklist-style rather than an explicit sequenced workflow.

4 / 5

Progressive Disclosure

Body is a concise overview with well-signaled one-level-deep references to references/implementation.md (linked inline per section and again under References), and the referenced bundle file exists and holds the executable code appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 precise, well-scoped description that states concrete capabilities, gives explicit trigger guidance, and draws a clear boundary against test-setup skills. The only minor gap is a few missing natural phrasings/file triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across named libraries—'Integrate Retrofit, OkHttp, and Kotlinx Serialization', 'building API clients, adding interceptors, or configuring network security'—providing comprehensive coverage rather than generic language.

5 / 5

Completeness

Explicitly answers both 'what' (integrate the three libraries for type-safe API communication) and 'when' ('Use when building API clients, adding interceptors, or configuring network security'), plus an explicit exclusion boundary.

5 / 5

Trigger Term Quality

Strong natural terms developers actually say (Retrofit, OkHttp, API clients, interceptors, network security, MockWebServer), including library names as synonyms, but lacks file-extension-style triggers and a couple of common phrasings.

4 / 5

Distinctiveness Conflict Risk

A clearly defined Android-networking niche anchored on named libraries, with an explicit 'not standalone MockWebServer or API-test setup' carve-out that minimizes overlap with test-focused skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.