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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, reasonably actionable body that falls short on executable completeness and feedback-loop wiring, and that ignores its own bundled scripts and assets. Every dimension lands at the midpoint because guidance is concrete but not fully executable or loop-closed.

Suggestions

Replace the arrow-notation type mapping and prose Examples with one or two complete, copy-paste-ready generated model files (e.g., a full schema.prisma and a TypeORM entity) to lift actionability.

Wire an explicit validation feedback loop into the numbered workflow (e.g., 'if the schema diff shows drift, regenerate and re-validate') instead of a single terminal validation step plus a separate error table.

Reference the bundled scripts and assets from the body (e.g., link to scripts/generate_model.py and assets/examples/ecommerce_database_schema.sql) so detailed logic lives in the bundle and SKILL.md stays an overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and decorators, but the prose Examples section ('Introspect 15 tables including users, orders...') is narrative rather than executable and the basic type-mapping table (varchar->String) re-states what Claude already knows.	2 / 3
Actionability	Concrete commands (npx prisma migrate dev, alembic revision --autogenerate) and specific decorators are present, but the type mapping uses arrow notation rather than executable code and the Examples are descriptive prose with no complete copy-paste-ready model file.	2 / 3
Workflow Clarity	A clear 10-step sequence with a validation step (step 10) and an error-handling table, but there is no explicit validate->fix->retry feedback loop wired into the workflow; for a database operation the rubric caps this at 2.	2 / 3
Progressive Disclosure	The body is well-organized into sections, but it never references the bundled scripts (generate_model.py, generate_schema.py) or assets (example SQL schema, TypeORM model) that exist, so content that could live in the bundle is duplicated inline and navigation to the bundle is missing.	2 / 3
	Total	8 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit use-when clause and natural trigger phrases covering a well-defined niche. It loses a point on specificity for second-person voice and a touch of buzzword padding ('comprehensive guidance and automation').

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('generate ORM models', 'create entity classes', 'scaffold database models') but the main clause 'ORM model and code generation with comprehensive guidance and automation' is partly fluff, and the description uses second-person voice ('when you need to work with', 'Trigger with phrases like'), which incurs the -1 penalty.	2 / 3
Completeness	It states what the skill does ('ORM model and code generation...') and includes an explicit 'use when' clause plus concrete trigger phrases, clearly answering both what and when.	3 / 3
Trigger Term Quality	Three natural phrases a user would actually say ('generate ORM models', 'create entity classes', 'scaffold database models') give good coverage of the triggering space, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	ORM code generation is a clear niche with distinct, specific triggers unlikely to fire for unrelated skills.	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
Commit: 2cafb23

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