CtrlK
BlogDocsLog inGet started
Tessl Logo

kotlin-ktor-patterns

Ktor server patterns including routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing. Use when building a Ktor server — routing, plugins, auth, DI, serialization, or tests.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is tdg-personal/kotlin-ktor-patterns

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is highly actionable and largely concise, dominated by executable code across Ktor's main concerns. Its weaknesses are structure-related: a monolithic file with no progressive disclosure and no validation checkpoints since it is a reference catalog rather than a sequenced workflow.

Suggestions

Split large sections (e.g., Authentication, WebSockets, testApplication) into separate reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Where multi-step risky operations exist (e.g., JWT secret/config setup, WebSocket connection lifecycle), add explicit validation or verification checkpoints to raise workflow clarity.

Tighten the opening line and any redundant inline comments to push conciseness toward fully lean.

DimensionReasoningScore

Conciseness

Body is mostly executable code with brief section intros and assumes Claude's knowledge of Kotlin/Ktor; only minor instances of over-explanation (e.g., 'Comprehensive Ktor patterns for building robust, maintainable HTTP servers with Kotlin coroutines') could be trimmed.

4 / 5

Actionability

Extensive copy-paste-ready code covering routing, serialization, JWT auth, StatusPages, CORS, Koin DI, validation, WebSockets, and testApplication, fully executable across common cases.

5 / 5

Workflow Clarity

The skill is a patterns catalog rather than a multi-step destructive workflow; project layout and Application.module() ordering give some sequence, but there are no explicit validation checkpoints or feedback loops for risky operations.

3 / 5

Progressive Disclosure

Content is well-organized under clear section headers but is a single monolithic ~690-line file with no bundle files or external references; material that could live in separate files (e.g., WebSocket/auth deep-dives) is inlined.

3 / 5

Total

15

/

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.

The description is specific, complete, and clearly distinct, naming concrete capabilities and an explicit 'Use when' trigger. Trigger term quality is strong but slightly leans on framework jargon over plain synonyms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing' — giving comprehensive coverage of the skill's actions.

5 / 5

Completeness

Explicitly answers both what ('Ktor server patterns including...') and when ('Use when building a Ktor server — ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger terms ('building a Ktor server', 'routing, plugins, auth, DI, serialization, or tests'), though 'testApplication' and 'kotlinx.serialization' are framework-specific jargon and a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Ktor server framework specifically) with distinct triggers and minimal overlap risk with other 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

skill_md_line_count

SKILL.md is long (691 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.