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".
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/database/orm-code-generator/skills/generating-orm-code/SKILL.mdQuality
Discovery
67%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 adequately communicates the skill's purpose and includes explicit trigger guidance, which is a strength. However, the core capability description relies on vague language ('comprehensive guidance and automation') rather than listing specific concrete actions. The trigger terms cover some natural phrases but miss common ORM framework names and related terminology that users would likely mention.
Suggestions
Replace 'comprehensive guidance and automation' with specific concrete actions, e.g., 'Generates ORM entity classes, repository layers, migration files, and relationship mappings'.
Expand trigger terms to include specific ORM frameworks (e.g., SQLAlchemy, Hibernate, Prisma, TypeORM) and related terms like 'database schema to code', 'data models', 'ORM mapping'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (ORM code generation) and mentions some actions like 'generate ORM models', 'create entity classes', 'scaffold database models', but the core description 'provides ORM model and code generation with comprehensive guidance and automation' is vague and doesn't list specific concrete actions beyond the trigger phrases. | 2 / 3 |
Completeness | It answers both 'what' (ORM model and code generation) and 'when' (explicit trigger phrases and a 'Use when' clause specifying when to activate). The trigger guidance is explicit with example phrases. | 3 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases like 'generate ORM models', 'create entity classes', 'scaffold database models', but misses common variations users might say such as specific ORM frameworks (SQLAlchemy, Hibernate, Prisma), 'database schema', 'migration', 'data models', or 'ORM mapping'. | 2 / 3 |
Distinctiveness Conflict Risk | ORM code generation is a reasonably specific niche, but 'code generation' could overlap with other code generation skills, and 'entity classes' or 'database models' could conflict with database schema design or general code scaffolding skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill attempts to cover too much ground—6 different ORMs with full generation pipelines—in a single monolithic file without executable code examples. While the workflow steps and error handling table show thoughtful structure, the lack of concrete code snippets, the verbose explanations of concepts Claude already knows, and the absence of any progressive disclosure significantly reduce its effectiveness. The skill would be far more useful if narrowed in scope or split into per-ORM guides with actual executable examples.
Suggestions
Add concrete, executable code examples: show an actual SQL introspection query, a complete generated Prisma schema block, or a TypeORM entity class rather than describing them in prose.
Split per-ORM guidance into separate referenced files (e.g., PRISMA.md, TYPEORM.md, SQLALCHEMY.md) and keep SKILL.md as a concise overview with navigation links.
Remove explanations of concepts Claude already knows—type mappings, what decorators are, how relationships work—and focus only on project-specific conventions or non-obvious decisions.
Add explicit validation feedback loops with concrete commands: e.g., 'Run `npx prisma validate`; if errors, fix the schema and re-run before proceeding to migration.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose, covering 6 different ORMs simultaneously with extensive explanations Claude already knows. The type mapping table, relationship detection logic, and general ORM concepts are all things Claude is deeply familiar with. The examples section describes scenarios in prose rather than showing code, adding length without value. | 1 / 3 |
Actionability | The instructions provide a clear sequence of steps and mention specific commands (e.g., `npx prisma migrate dev`, `alembic revision --autogenerate`), but there are no executable code examples—no actual generated model code, no SQL introspection queries, no complete snippets. The examples section describes what would be generated in prose rather than showing concrete output. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced and step 10 mentions validation, but the validation step is vague ('running a test migration against a temporary database or by comparing with a diff tool') without specifying concrete commands or a feedback loop for fixing issues. For a code generation workflow that could produce broken migrations, the validation/recovery guidance is insufficient. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic document with no bundle files and no references to supplementary materials. Given the breadth (6 ORMs, multiple output types, error handling, examples), this content would greatly benefit from being split into per-ORM guides or separate reference files. Everything is inlined in a single long document. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.