generating-orm-code

Execute use when you need to work with ORM code generation. This skill provides ORM model and code generation with comprehensive guidance and automation. Trigger with phrases like "generate ORM models", "create entity classes", or "scaffold database models".

Quality

70%

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 ./plugins/database/orm-code-generator/skills/generating-orm-code/SKILL.md

Quality

Content

50%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 content is a thorough, well-organized reference for ORM code generation with concrete commands and a clear step sequence. It is held back by verbosity, lack of complete executable code examples, a missing validation feedback loop, and failure to integrate the bundled script files.

Suggestions

Move per-ORM decorator specifics and the Error Handling table into reference files and link to them from a concise overview, then reference the bundled generate_model.py / generate_schema.py scripts in the relevant steps.

Add a complete executable code example for one ORM (e.g. a full generated Prisma schema block) so the core generation is copy-paste ready rather than only described.

Turn step 10 into an explicit feedback loop: validate the generated schema/migration, and if it fails, fix the model and re-run validation before proceeding.

Reconcile scripts/README with the actual bundle so it only lists files that exist (generate_model.py, generate_schema.py).

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concept-explanation padding Claude already knows, but it is long and could be tightened — the Output section restates what the Instructions already produce, and per-ORM decorator detail could move to references. It is mostly efficient but not maximally lean.	2 / 3
Actionability	It gives concrete SQL queries, type mappings, decorators, and executable migration commands (e.g. "npx prisma migrate dev --name init"), but the core model generation is described as steps rather than shown as complete executable code, and the bundled scripts (generate_model.py, generate_schema.py) are never referenced. This matches the incomplete-but-concrete anchor 2.	2 / 3
Workflow Clarity	The 10-step Instructions form a clear sequence with an explicit validation step (step 10) and an Error Handling recovery table. However, for database/migration operations the rubric caps workflow clarity at 2 when there is no explicit validate -> fix -> re-validate feedback loop woven into the sequence, which is missing here.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic: all type mappings, per-ORM decorators, the error table, and examples are inline, and the bundled scripts/assets are not referenced from the body. The scripts/README also lists files (validate_model.py, migration_generator.py) that do not exist in the bundle, signaling inconsistent structure rather than clean one-level references.	2 / 3
	Total	8 / 12 Passed

Description

90%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 strong: it covers what and when with explicit, natural trigger phrases in a distinct niche. Its only weakness is the abstract "comprehensive guidance and automation" phrasing in the capability sentence.

Suggestions

Replace "provides ORM model and code generation with comprehensive guidance and automation" with concrete actions, e.g. "Generate Prisma/TypeORM/SQLAlchemy/Drizzle models, migrations, and repository layers from a database schema."

Add a few more natural trigger variations (e.g. "ORM models", "Prisma schema", "database entities") to broaden coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and some actions ("ORM model and code generation") and lists concrete trigger actions, but the capability statement leans on abstract fluff ("comprehensive guidance and automation") rather than enumerating multiple specific concrete actions. It is above the vague anchor 1 but below the multi-action anchor 3.	2 / 3
Completeness	It states what the skill does ("ORM model and code generation") and explicitly gives when to use it ("Execute use when you need to work with ORM code generation" plus "Trigger with phrases like..."). The explicit trigger guidance satisfies the 'Use when...' requirement that would otherwise cap completeness at 2.	3 / 3
Trigger Term Quality	It provides several natural phrases users would say ("generate ORM models", "create entity classes", "scaffold database models"), which is better coverage than the single-phrase anchor 2 example. The terms are relevant and natural rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	ORM code generation is a clear niche with specific, distinct triggers unlikely to fire for unrelated skills. Although the generic phrase "code generation" could broadly overlap with other generators, the ORM qualifier and concrete trigger phrases make it clearly distinguishable.	3 / 3
	Total	11 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/orm-code-generator/skills/generating-orm-code/SKILL.md
Commit: c4eafaf

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.