kotlin-exposed-patterns

JetBrains Exposed ORM patterns including DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern. Use when working with the Exposed ORM — DSL or DAO queries, transactions, pooling, or migrations.

Quality

72%

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

Quality

Content

57%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 — dense, executable, copy-paste-ready Kotlin covering the full range of Exposed usage — but pays for it in token efficiency and structure: significant example duplication, redundant explanation of library basics, and a ~720-line monolithic body with no progressive disclosure into reference files. Destructive/batch database operations also lack validation checkpoints, capping workflow clarity.

Suggestions

Move the full repository implementation, JSONB column-type detail, testing setup, and Gradle dependency list into references/ files (e.g., REPOSITORY.md, JSON_COLUMNS.md, TESTING.md) and keep SKILL.md as a concise overview with one small example per pattern.

Deduplicate the repeated snippets — the HikariCP config block, findUserById, and createUser each appear 2-3 times; keep one canonical version per pattern and drop the 'Examples' section that previews them again.

Add explicit validation guidance around destructive and batch operations (e.g., verify affected-row counts before/after deleteWhere/update, wrap batchInsert in error-retry handling) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the HikariCP configuration block is duplicated verbatim (Examples and Database Setup), findUserById appears three times and createUser twice, and the full repository implementation re-implements DSL queries already shown. The "How It Works" paragraph also explains what HikariCP pooling and Flyway migrations do — concepts Claude already knows. It sits above anchor 1 (most content is dense code, not prose padding) but clearly below anchor 3 due to systematic duplication.	2 / 5
Actionability	Nearly all guidance is complete, executable Kotlin: table definitions, CRUD, joins, aggregations, subqueries, escaped LIKE searches, pagination, batch insert, upsert, a working JSONB column type, an H2 test suite, and pinned Gradle dependency coordinates. This matches the anchor-5 copy-paste-ready standard covering the common cases.	5 / 5
Workflow Clarity	Sections loosely sequence setup → tables → queries → DAO → testing, and the startup snippet orders migrations before database creation, but there are no validation or verification checkpoints for destructive and batch operations (deleteWhere, update, batchInsert, upsert). The rubric's cap of 3 for database/batch operations without validation applies here.	3 / 5
Progressive Disclosure	The body is well-organized with clear headers, but ~720 lines are inlined in SKILL.md with no reference files at all — the full repository implementation, JSON-column detail, testing setup, and dependency list clearly belong in separate files. This lands between anchor 2 (inline content, but structure is good rather than minimal) and anchor 3, fitting anchor 3 better.	3 / 5
	Total	13 / 20 Passed

Description

87%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 strong: it enumerates specific, comprehensive capabilities, includes an explicit 'Use when' clause with concrete trigger phrases, and occupies a distinct niche (JetBrains Exposed) with minimal conflict risk. The only weakness is that capabilities are listed as noun-form topics rather than concrete actions, which slightly blunts specificity.

Dimension	Reasoning	Score
Specificity	"DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern" names several specific capabilities covering every section of the body. It falls just short of anchor 5 because these are noun-form topics rather than concrete actions (e.g., "write DSL queries", "configure HikariCP"), and clearly exceeds anchor 3's 1-2 actions.	4 / 5
Completeness	Both parts are explicit: what ("JetBrains Exposed ORM patterns including DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern") and when ("Use when working with the Exposed ORM — DSL or DAO queries, transactions, pooling, or migrations") with concrete trigger phrases, matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	"Use when working with the Exposed ORM — DSL or DAO queries, transactions, pooling, or migrations" provides good natural-term coverage a user would actually say. A few natural variants ("database access", "SQL queries", "schema") are missing, placing it between anchors 3 and 5 but noticeably above the midpoint.	4 / 5
Distinctiveness Conflict Risk	"JetBrains Exposed ORM" and "Use when working with the Exposed ORM" define a clear niche with distinct triggers; there is no meaningful overlap risk with generic SQL, JPA, or other database skills.	5 / 5
	Total	18 / 20 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: c70874f

Reviewed: 1 day 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.