typeorm-starter

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

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 ./database/typeorm-starter/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body is highly actionable and mostly concise, with executable examples across the core TypeORM patterns, but it inlines a large amount of content that could be split into reference files and provides no validation checkpoints for its destructive database operations.

Suggestions

Add explicit validation/recovery steps around migrations and schema commands (e.g. run `migration:show` after `migration:run`, and warn/confirm before `schema:drop`).

Define the missing Profile entity and add it to the project structure, or remove references to it.

Move the full entity/repo/subscriber/transaction code into reference files (e.g. references/entities.md) and keep SKILL.md as an overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly lean, code-forward content that does not re-explain TypeORM basics, but the prerequisites are duplicated (frontmatter vs body) and the migration commands repeat across "Database Initialization" and "Common Commands" sections.	4 / 5
Actionability	Provides complete, copy-paste-ready TypeScript for DataSource, entities, repository, subscriber, and transactions, but references a Profile entity that is never defined and absent from the project structure listing.	4 / 5
Workflow Clarity	Scaffold/init/migration commands are sequenced, but destructive operations (schema:sync, schema:drop) and migrations lack explicit validation checkpoints or feedback loops, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Sections are clearly headed and well-organized, but at ~380 lines everything is inlined in SKILL.md with no reference files; entity/repo/subscriber examples that belong in separate files are kept inline.	3 / 5
	Total	14 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 specific and distinct, naming the target library and a comprehensive list of capabilities, but it omits any explicit "when to use" trigger guidance, which caps its completeness. Adding a Use-when clause would lift it into the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or migrating to a TypeORM 0.3+ project with TypeScript."

Include a natural-language synonym or two (e.g. "TypeORM ORM", "TypeScript ORM") to broaden trigger coverage beyond pure jargon.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("entities with decorators, CLI migrations, repositories, DataSource configuration, relations, query builder, and subscribers"), giving comprehensive coverage of the scaffolding scope.	5 / 5
Completeness	The "what" is clearly stated but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"TypeORM" is the natural term a user would say, but the description relies on technical jargon and lacks synonyms or file-extension variants, so it sits just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Naming the specific library "TypeORM 0.3+" gives it a clear, distinct niche with minimal overlap risk against other ORM/database skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: database/typeorm-starter/SKILL.md
Commit: 181fcbc

Reviewed: 1 day 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.