kotlin-exposed-patterns

JetBrains Exposed ORM patterns including DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

Quality

Content

65%

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

A highly actionable, code-rich reference with broad coverage of Exposed patterns, but it is verbose with duplicated blocks, lacks validation checkpoints for batch/destructive operations, and is monolithic with no progressive disclosure into separate files.

Suggestions

Remove duplicated blocks (HikariCP config, UsersTable, ResultRow.toUser, createUser/findUserByEmail) and trim the conceptual "How It Works" paragraph to assume Claude's knowledge of Exposed/HikariCP/Flyway.

Add explicit validation/verification steps after batch and destructive operations (e.g., verify affected row counts, re-query to confirm state) so workflow clarity can reach 3.

Split the large reference into bundle files (e.g., references/repository.md, references/json-columns.md, references/testing.md) and link to them one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly code-driven and efficient, but includes explanatory prose Claude already knows (the "How It Works" paragraph on DSL/DAO/HikariCP/Flyway) and duplicates blocks verbatim (HikariCP config, UsersTable, row mappers, createUser/findUserByEmail appear twice), which is unnecessary padding.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Kotlin across DSL, DAO, repository, transactions, JSON columns, migrations, testing, and Gradle deps — concrete and complete rather than pseudocode.	3 / 3
Workflow Clarity	Sections are well organized but batch operations (batchInsert, upsert) and destructive operations (delete) lack validation/verification checkpoints or feedback loops, which per the scoring notes caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), so all content is inline in a ~710-line monolithic SKILL.md; sections are clearly headed, but substantial material that could be split (full repository impl, JSON custom type, test harness) lives inline.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, well-targeted description that names concrete Exposed capabilities and uses third-person voice, but it omits an explicit "Use when..." trigger clause, capping completeness at 2.

Suggestions

Append a "Use when..." clause naming the user situations that should trigger this skill (e.g., setting up Exposed, writing DSL/DAO queries, configuring HikariCP, or adding Flyway migrations).

Include natural trigger phrasing a user might say, such as "Use when working with JetBrains Exposed, configuring database access in Kotlin, or setting up connection pooling and migrations."

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern" — matching the anchor for enumerating several specific actions.	3 / 3
Completeness	It clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms a Kotlin developer would actually say are well covered: "JetBrains Exposed ORM", "DSL queries", "DAO pattern", "HikariCP", "Flyway migrations", "repository pattern".	3 / 3
Distinctiveness Conflict Risk	The Exposed-ORM niche is specific and unlikely to trigger for unrelated skills; the named stack (HikariCP, Flyway, DAO) further narrows its scope.	3 / 3
	Total	11 / 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
skill_md_line_count	SKILL.md is long (721 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/kotlin-exposed-patterns/SKILL.md
Commit: 754b8dd

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