backend-kotlin

Kotlin Developer Agent. Kotlin 기반 백엔드 개발을 담당합니다. Coroutines, Ktor, Spring Boot + Kotlin 전문.

Quality

23%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/backend-kotlin/SKILL.md

Quality

Discovery

32%

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 identifies a clear technology stack (Kotlin with Coroutines, Ktor, Spring Boot) but fails to specify concrete actions or provide explicit trigger guidance. It reads more like a job title than an actionable skill description, lacking the 'Use when...' clause critical for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Kotlin backend development, Ktor APIs, Spring Boot Kotlin projects, or coroutine-based async code'

Replace vague '담당합니다' (handles) with specific actions like 'Creates REST APIs, implements coroutine-based async handlers, configures Spring Boot Kotlin applications'

Include natural language variations users might say: 'Kotlin server', 'async Kotlin', 'suspend functions', '.kt files', 'Kotlin microservices'

Dimension	Reasoning	Score
Specificity	Names the domain (Kotlin backend development) and mentions specific technologies (Coroutines, Ktor, Spring Boot + Kotlin), but doesn't list concrete actions like 'create APIs', 'implement async handlers', or 'configure dependency injection'.	2 / 3
Completeness	Describes what domain it covers but completely lacks a 'Use when...' clause or any explicit trigger guidance. The 'when' is entirely missing, which per rubric guidelines caps this at maximum 2, but since even the 'what' is vague ('담당합니다' = 'handles'), this scores 1.	1 / 3
Trigger Term Quality	Includes relevant technical keywords (Kotlin, Coroutines, Ktor, Spring Boot) that developers would use, but missing common variations like 'backend API', 'server-side Kotlin', 'async programming', or file extensions like '.kt'.	2 / 3
Distinctiveness Conflict Risk	The Kotlin + specific frameworks (Ktor, Spring Boot) provide some distinctiveness from generic backend skills, but could overlap with general 'Spring Boot' or 'backend development' skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

14%

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

This skill content is essentially a role description rather than actionable guidance. It lists Kotlin-related topics and keywords but provides no concrete instructions, code examples, or workflows that would help Claude perform Kotlin development tasks. The content describes what the agent should know rather than how to do anything.

Suggestions

Add executable code examples for common Kotlin patterns (e.g., coroutine usage, Spring Boot controller with Kotlin, Ktor route definition)

Define specific workflows for common tasks like 'setting up a Kotlin Spring Boot project' or 'implementing async operations with coroutines'

Include concrete guidance on when to use each technology (Ktor vs Spring Boot) with decision criteria

Add references to detailed documentation files for each specialty area (e.g., COROUTINES.md, KTOR.md) if more depth is needed

Dimension	Reasoning	Score
Conciseness	The content is brief but consists mostly of lists without actionable value. While not verbose, it doesn't provide information Claude doesn't already know about Kotlin features.	2 / 3
Actionability	No concrete code examples, commands, or executable guidance provided. The content only lists concepts and keywords without any instructions on how to actually perform tasks.	1 / 3
Workflow Clarity	No workflow, process steps, or sequences are defined. The skill describes what the agent knows but not how to accomplish any specific task.	1 / 3
Progressive Disclosure	Content is a flat list with no structure for navigation, no references to detailed materials, and no organization beyond basic headers listing topics.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

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