CtrlK
BlogDocsLog inGet started
Tessl Logo

ent

Work with Ent ORM schemas and generated code. Use when modifying ent schemas, debugging ent query issues, or dealing with Postgres type mappings.

75

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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 lean, highly actionable reference packed with project-specific Ent guidance, well organized into clear sections. Its only gap is the lack of an explicit validation/feedback loop around the schema-change regeneration workflow, which is material because it touches database operations.

Suggestions

Add an explicit validation checkpoint after regeneration for schema changes (e.g. run the migration diff / atlas validate, then tests) with a fix-and-retry loop, since schema and migration work is a database operation where feedback loops matter.

Make the regenerate-before-tests sequence a numbered workflow with a clear pass/fail gate so the validation gap is closed rather than implied.

State what to check if generated code or migrations fail to apply (e.g. identifier-length collisions, jsonb-vs-text[] drift) so Claude can recover without re-reading the whole skill.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious project-specific detail — exact paths, API calls, and gotchas — and assumes Claude's competence without explaining what an ORM or Postgres is, so every token earns its place rather than padding.

3 / 3

Actionability

Guidance is concrete and copy-paste ready, e.g. 'field.Other(..., pq.StringArray{}).SchemaType(...)', 'db.ParseLedgerDimensionFromSelectedValues("dimension_", row.Value)', 'make generate', and 'go generate ./openmeter/ent/...', matching the fully-executable anchor.

3 / 3

Workflow Clarity

The schema-change sequence is present with a stated checkpoint ('regenerate with make generate before running tests'), but for database/migration work there is no explicit validation or validate->fix->retry feedback loop on the generated output, which caps it below the top level.

2 / 3

Progressive Disclosure

At under 50 lines with no bundle files and no need for external references, the well-organized sections (Schema Location, Postgres Array Columns, Custom Selects & Joins, Common Patterns, Regeneration) satisfy the simple-skill allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 distinct: it names concrete actions, gives an explicit 'Use when' trigger covering the natural problem phrasings, and occupies a clear niche unlikely to conflict. It is a strong, concise trigger description.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions — 'Work with Ent ORM schemas and generated code', 'modifying ent schemas', 'debugging ent query issues', 'dealing with Postgres type mappings' — matching the multiple-specific-actions anchor rather than the some-actions level below.

3 / 3

Completeness

It states both what ('Work with Ent ORM schemas and generated code') and an explicit when ('Use when modifying ent schemas, debugging ent query issues, or dealing with Postgres type mappings'), so the when is explicit rather than merely implied.

3 / 3

Trigger Term Quality

Triggers like 'ent schemas', 'ent query issues', and 'Postgres type mappings' are the natural phrasings a developer would use when reaching for this skill, giving good domain coverage rather than just some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

The Ent-ORM-plus-Postgres-type-mapping niche has distinct triggers unlikely to fire for unrelated skills, fitting the clear-niche anchor instead of the could-overlap level below.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
openmeterio/openmeter
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.