typeorm-starter

Scaffold a TypeORM 0.3+ project with TypeScript, entities with decorators, CLI migrations, repositories, DataSource configuration, relations, query builder, and subscribers.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./database/typeorm-starter/SKILL.md

Quality

Content

79%

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

This is a high-quality TypeORM starter skill with excellent actionability and conciseness. The code examples are comprehensive, executable, and cover all major TypeORM patterns. The main weaknesses are the lack of explicit validation checkpoints in workflows (especially around migrations) and the monolithic structure that could benefit from progressive disclosure to separate files.

Suggestions

Add explicit validation steps to the migration workflow, e.g., 'Run migration:show to verify pending migrations before running, then verify again after to confirm success'

Consider splitting detailed entity examples and query builder patterns into a separate PATTERNS.md or EXAMPLES.md file, keeping SKILL.md as a concise overview with references

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing only essential information without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides fully executable, copy-paste ready code examples throughout - from DataSource configuration to entities, repositories, subscribers, and transactions. All code is complete TypeScript with proper imports and types.	3 / 3
Workflow Clarity	Commands are listed clearly but lack explicit validation checkpoints. The migration workflow doesn't include verification steps (e.g., checking migration status after running, validating schema changes). The warning about synchronize in production is good but feedback loops are missing.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic file with ~250 lines of code examples that could benefit from splitting into separate reference files. The Integration Notes mention other skills but the main content could be better structured with external references.	2 / 3
	Total	10 / 12 Passed

Description

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.

This description excels at specificity and distinctiveness by naming concrete TypeORM 0.3+ features and concepts. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords beyond technical jargon. The description assumes users already know they want TypeORM rather than helping Claude identify when this skill applies.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when setting up a new TypeORM project, configuring database connections, or when the user mentions TypeORM, ORM setup, or database entities'

Include more natural user terms like 'database setup', 'ORM', 'Node.js database', 'PostgreSQL/MySQL with TypeScript' to capture users who may not explicitly say 'TypeORM'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: scaffold project, entities with decorators, CLI migrations, repositories, DataSource configuration, relations, query builder, and subscribers. These are all concrete TypeORM concepts.	3 / 3
Completeness	Clearly answers 'what' with comprehensive capability list, but lacks explicit 'Use when...' clause or trigger guidance. Users would need to infer when to use this skill.	2 / 3
Trigger Term Quality	Includes relevant technical terms like 'TypeORM', 'TypeScript', 'entities', 'migrations', 'repositories', but missing common user variations like 'ORM', 'database setup', 'Node.js database', or file extensions.	2 / 3
Distinctiveness Conflict Risk	Very specific to TypeORM 0.3+ with distinct terminology (DataSource, decorators, query builder). Unlikely to conflict with other database or ORM skills due to explicit version and framework naming.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

Reviewed: 3 months 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.