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.

54

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/kotlin-ktor-patterns/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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, with comprehensive executable Ktor code across all major topics, but it is over-long and monolithic: it reproduces standard Ktor knowledge inline with no progressive disclosure or reference files, and lacks sequenced workflows with validation checkpoints for build/test operations.

Suggestions

Split the body into a lean overview plus one-level-deep reference files (e.g. reference/authentication.md, reference/testing.md) and link to them so the SKILL.md stays a concise index.

Tighten or remove code that restates Ktor basics Claude already knows (standard routing idioms, generic CORS/serialization setup) to improve token efficiency.

Add an explicit build -> configure -> test workflow with validation checkpoints (e.g. run testApplication, assert status, fix, re-run) for the integration-testing process.

DimensionReasoningScore

Conciseness

The body is dense with complete, executable Kotlin but is also very long (~680 lines) and largely restates Ktor knowledge Claude already has (standard routing, serialization, CORS, Koin setup); it could be tightened into leaner reference snippets rather than full reproductions.

2 / 3

Actionability

Provides copy-paste-ready, executable Kotlin for routing, auth, StatusPages, CORS, Koin, WebSockets, and testApplication tests with concrete configuration values, matching the 'fully executable code, copy-paste ready' anchor.

3 / 3

Workflow Clarity

It organizes patterns by topic with a 'When to Activate' list and a quick-reference table, but presents them as a catalog rather than a sequenced workflow; for the build/deploy/test process there are no explicit validation checkpoints or feedback loops, fitting the 'sequence present but checkpoints missing' anchor.

2 / 3

Progressive Disclosure

No bundle files exist and the SKILL.md is a monolithic ~680-line wall of code covering every topic inline with no offloaded references, matching the 'monolithic wall of text; poor organization' anchor rather than a lean overview pointing to detail files.

1 / 3

Total

8

/

12

Passed

Description

67%

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 and distinctive, clearly scoped to Ktor server development with a good list of concrete capability areas. It is weak on completeness because it omits an explicit 'Use when' trigger, and its trigger terms mix natural phrasing with library-specific jargon.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or configuring Ktor HTTP servers, plugins, auth, or Ktor integration tests.'

Soften jargon-only trigger terms (e.g. 'kotlinx.serialization', 'testApplication') with natural phrasings a user would actually say, such as 'JSON serialization' and 'Ktor testing'.

DimensionReasoningScore

Specificity

Names the Ktor server domain and enumerates multiple concrete capability areas ("routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing"), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill covers but provides no explicit "Use when..." trigger clause, so 'when' is only implied; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes several natural terms users would say ("Ktor", "authentication", "WebSockets", "plugins"), but leans on technical jargon ("kotlinx.serialization", "Koin DI", "testApplication testing") and omits common variations a user might phrase, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The Ktor-specific scope ("Ktor server patterns", "Koin DI", "testApplication") is a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

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.