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

78%

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%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 body is a thorough, highly actionable Exposed reference with executable code throughout, but it is a monolithic single-file document with duplicated blocks and lacks validation checkpoints for its batch/destructive operations.

Suggestions

Add an explicit validation step after destructive/batch operations (e.g., verify row counts after batchInsert, or run Flyway info/validate after migrate) to raise workflow_clarity.

Split large self-contained sections (Repository implementation, JSON column type, Testing setup) into one-level-deep reference files and link them from SKILL.md to improve progressive_disclosure.

Dedupe repeated blocks — the HikariCP config and findUserById examples each appear multiple times — keeping one canonical version.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable code, but it repeats content — HikariCP configuration appears twice (Examples and Database Setup) and findUserById appears three times — which could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste-ready Kotlin and SQL covering the common cases (CRUD, joins, pagination, batch insert, upsert, transactions, repositories, testing).	5 / 5
Workflow Clarity	Sections are well-organized, but destructive/batch operations (batch insert, deletes, Flyway migrations) lack explicit validation checkpoints or feedback loops, capping this dimension per the rubric.	3 / 5
Progressive Disclosure	The content is structured with clear section headers, but the entire ~700-line reference is inlined in SKILL.md with no one-level-deep references to split out large blocks (full repository impl, JSON column type, testing setup); no bundle files exist.	3 / 5
	Total	14 / 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 distinctive, clearly naming the domain and providing an explicit 'Use when' trigger. Minor synonym coverage in the trigger clause keeps trigger_term_quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern' — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both what it does and when to use it via 'Use when working with the Exposed ORM — ...' with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'when' clause names natural terms ('DSL or DAO queries, transactions, pooling, or migrations') that users would say, but omits synonyms and the 'Exposed ORM' variations beyond the primary name.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (JetBrains Exposed ORM) with distinct triggers, so it is unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 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: 06c5e11

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