CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kotlin-exposed-patterns

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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 kotlin-exposed-patterns in affaan-m/ECC

SKILL.md
Quality
Evals
Security

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 highly actionable with complete, executable Kotlin examples across every major Exposed topic, but it is a monolithic single file with significant internal duplication and no validation/error-recovery guidance for database operations. Splitting advanced material into reference files and adding transaction failure-handling patterns would lift both conciseness and workflow clarity.

Suggestions

Remove the duplicated blocks: the Examples section repeats the HikariCP config, findUserById, and createUser verbatim, and the ExposedUserRepository re-implements CRUD already shown in DSL Queries — keep one canonical version of each.

Split advanced material into reference files (e.g. references/jsonb-columns.md, references/repository-pattern.md, references/testing.md) and keep SKILL.md as an overview with clearly signaled one-level-deep links.

Add validation and error-recovery patterns for database operations: transaction rollback examples, handling of constraint-violation exceptions on batchInsert/upsert, and a verify step after migrations run.

DimensionReasoningScore

Conciseness

The body is mostly dense, executable code with little teaching of known concepts, but it is noticeably padded by duplication: the HikariCP config, findUserById, createUser, search/pagination, and an ~80-line repository implementation each appear twice. This fits anchor 3 (could be tightened) better than 2 (no basic-concept explanation) or 4 (the duplicated sections are substantial).

3 / 5

Actionability

Fully executable, copy-paste-ready Kotlin covering setup, table definitions, CRUD, joins, aggregation, subqueries, pagination, batch insert/upsert, DAO entities, transactions, repository implementation, custom JSONB column type, tests, and Gradle dependencies. Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Content is coherently organized (dependencies → pooling → migrations → tables → queries → DAO → transactions → repository → testing), but there are no validation checkpoints or error-recovery guidance for database, batch, and destructive operations (no rollback, error handling, or verify steps). The rubric explicitly caps workflow clarity at 3 in this context.

3 / 5

Progressive Disclosure

Section headers are clear and well-ordered, but the skill is a ~720-line monolith with no bundle files: content such as the custom JSONB column type, the full repository implementation, and the testing guide belongs in separate reference files. This fits anchor 3 (content that should be separate is inline) better than 2 (structure is genuinely present) or 4 (nothing is split out).

3 / 5

Total

14

/

20

Passed

Description

66%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 and names a clear framework niche with six concrete capability areas, but it omits any 'Use when...' trigger guidance, capping its completeness. Adding an explicit trigger clause and the keywords 'Kotlin' and 'database' would raise it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when setting up database access in Kotlin with Exposed, writing Exposed DSL/DAO queries, or configuring HikariCP pooling and Flyway migrations."

Include the words 'Kotlin' and 'database' so users who say 'Kotlin database' or 'SQL in Kotlin' naturally match this skill.

Consider phrasing capabilities as actions (e.g. "Write DSL queries, manage DAO entities, run Flyway migrations") to sharpen specificity.

DimensionReasoningScore

Specificity

Lists six concrete capability areas ("DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern"), giving broad but not fully comprehensive coverage. It sits at anchor 4 rather than 5 because the items are topic nouns rather than parallel concrete actions and 'including' leaves coverage open-ended.

4 / 5

Completeness

The 'what' is clear (Exposed ORM patterns across six named areas), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is specific and substantive.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say ("ORM", "transactions", "connection pooling", "migrations", "repository pattern"). Below anchor 5 because common phrasings like 'Kotlin', 'database', and 'SQL' are missing, which users would naturally mention when needing this skill.

4 / 5

Distinctiveness Conflict Risk

"JetBrains Exposed ORM" names a specific framework, giving a clear niche with mostly distinct triggers. Minor overlap risk remains with closely related skills for HikariCP pooling or Flyway migrations, which are named in the description but are standalone tools.

4 / 5

Total

15

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (720 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/kotlin-exposed-patterns/SKILL.md

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.