ent

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

Quality

79%

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 ./.agents/skills/ent/SKILL.md

Quality

Content

80%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 and well-structured, packing codebase-specific Ent gotchas and executable commands into a lean, self-contained reference. Its weakest point is workflow clarity: the regeneration/migration flow lacks an explicit validation checkpoint.

Suggestions

Add an explicit validation step after generation, e.g. verify the generated code compiles and run an Atlas migration diff check before running tests.

Tighten the longest Common Patterns bullets (upserts, SetOrClear, identifier length) by moving extended rationale into a short lead clause and keeping the concrete pattern first.

Include a brief feedback loop for migration-name collisions (generate -> check for truncated/colliding FK or index names -> shorten StorageKey -> regenerate).

Dimension	Reasoning	Score
Conciseness	The body is dense and codebase-specific with no introductory padding and assumes Go/Ent knowledge, but several Common Patterns bullets (upserts, SetOrClear, identifier length) are long enough to trim, keeping it below 5.	4 / 5
Actionability	It provides copy-paste-ready code patterns (field.Other with pq.StringArray, db.ParseLedgerDimensionFromSelectedValues, index.Fields(...).Unique()), exact commands (make generate, go generate ./openmeter/ent/...), and concrete file paths covering the common cases.	5 / 5
Workflow Clarity	The edit-schema -> make generate -> run-tests sequence is present but the only checkpoint ("before running tests") is implicit, and migration-related DB operations lack an explicit validation/feedback loop, which caps destructive/DB workflows at 3.	3 / 5
Progressive Disclosure	The body is under 50 lines with well-organized section headers and no need for external bundle files (references/scripts/assets are absent), so the simple-skill exception yields a 5; inline codebase paths are source pointers, not nested bundle references.	5 / 5
	Total	17 / 20 Passed

Description

78%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 cleanly answers both what and when with concrete, niche-specific trigger phrases for the Ent ORM. Its main weakness is a generic lead verb ("Work with") and missing synonyms/extensions that would round out trigger coverage.

Suggestions

Replace the generic "Work with Ent ORM schemas and generated code" with concrete verbs (e.g. "Modify Ent schemas, regenerate generated code, and debug Ent queries").

Add natural synonyms and file cues such as "ent ORM", "ent migrations", "ent generate", or ".go schema files" to broaden trigger coverage.

Tighten the "Postgres type mappings" trigger to an ent-specific framing to reduce overlap with generic Postgres/database skills.

Dimension	Reasoning	Score
Specificity	Names three concrete actions ("modifying ent schemas", "debugging ent query issues", "dealing with Postgres type mappings") though the lead "Work with" is generic; not comprehensive enough for 5 and beyond the 1-2 actions of 3.	4 / 5
Completeness	Both what ("Work with Ent ORM schemas and generated code") and when ("Use when modifying... debugging... dealing with...") are present with concrete triggers, but the "what" clause is generic ("Work with") unlike the 5-anchor's concrete action list.	4 / 5
Trigger Term Quality	"ent schemas", "ent query issues", and "Postgres type mappings" are natural phrases users would say, but synonyms and file extensions (e.g. "ent ORM", "ent migrations", ".go") are missing, so it falls short of 5.	4 / 5
Distinctiveness Conflict Risk	Ent ORM is a clear niche and the ent-prefixed triggers are distinct with minimal conflict risk; the "Postgres type mappings" trigger is the only mild overlap with generic DB skills but not enough to drop to 4.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: openmeterio/openmeter
Path: .agents/skills/ent/SKILL.md
Commit: 03a90ec

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