generating-orm-code

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

54%

Overall

Validation — 81%

Implementation — 20%

Activation — 82%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill is a generic template with no ORM-specific content whatsoever. It reads like a find-and-replace of 'orm-code-generator' into a boilerplate document. There are no code examples for generating models, no database schema patterns, no entity class templates, and no guidance on specific ORM frameworks (SQLAlchemy, TypeORM, Hibernate, etc.).

Suggestions

Add concrete, executable code examples showing ORM model generation for at least one framework (e.g., SQLAlchemy model from a table schema)

Replace generic steps with ORM-specific workflow: analyze schema → generate models → validate relationships → test migrations

Remove all generic software development advice (backup data, monitor resources, etc.) that Claude already knows

Include specific input/output examples: given this database schema, generate these entity classes with these decorators/annotations

Dimension	Reasoning	Score
Conciseness	Extremely verbose with generic boilerplate that applies to any task. Contains no ORM-specific content - just template text like 'Review current configuration, setup, and baseline metrics' that Claude already knows. Every section is padded with unnecessary generic guidance.	1 / 3
Actionability	No concrete code, commands, or ORM-specific examples. Instructions like 'Execute implementation in non-production environment first' are completely abstract. No actual ORM model generation code, no schema examples, no entity class templates - nothing executable.	1 / 3
Workflow Clarity	Steps are numbered and sequenced, but they're generic software development steps that could apply to any task. No ORM-specific validation checkpoints like 'validate generated models compile' or 'test database migrations'. The workflow structure exists but lacks domain-specific substance.	2 / 3
Progressive Disclosure	References external files in Resources section with clear paths, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths like '{baseDir}/templates/orm-code-generator/' which may not exist. No clear quick-start section that gets to ORM generation immediately.	2 / 3
	Total	6 / 12 Passed

Activation

82%

This description is functional with good trigger terms and explicit usage guidance, making it reasonably complete. However, it lacks specificity about concrete capabilities beyond generic phrases like 'comprehensive guidance and automation', and the ORM domain could potentially overlap with other code generation or database skills.

Suggestions

Replace vague phrase 'comprehensive guidance and automation' with specific concrete actions (e.g., 'generates model classes, migration scripts, repository patterns, and relationship mappings')

Add specific ORM frameworks or technologies supported to increase distinctiveness (e.g., 'for SQLAlchemy, Entity Framework, Hibernate')

Dimension	Reasoning	Score
Specificity	Names the domain (ORM code generation) and mentions some actions like 'generate ORM models', 'create entity classes', 'scaffold database models', but lacks comprehensive detail about what specific capabilities are provided beyond generic 'comprehensive guidance and automation'.	2 / 3
Completeness	Explicitly answers both what ('ORM model and code generation with comprehensive guidance and automation') and when ('Trigger with phrases like...' provides clear trigger guidance). Has explicit 'Use when' equivalent clause.	3 / 3
Trigger Term Quality	Includes good natural trigger terms users would say: 'generate ORM models', 'create entity classes', 'scaffold database models'. These are realistic phrases developers would use when needing this functionality.	3 / 3
Distinctiveness Conflict Risk	Reasonably specific to ORM domain but could overlap with general code generation skills or database-related skills. The trigger terms help distinguish it, but 'code generation' is fairly broad.	2 / 3
	Total	10 / 12 Passed

Reviewed

13 days ago

Table of Contents

Validation Implementation Activation

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.