Tessl • The management layer for AI agent skills

SkillPublic

typeorm-starter

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

Quality

75%

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.

A dense, largely executable reference whose code quality and conciseness are strong. The main deficits are a never-defined Profile entity that breaks self-contained executability, missing validation checkpoints around destructive migration operations, and a monolithic single-file layout that inlines full entity source that would sit better in reference files.

Suggestions

Add validation checkpoints to the migration workflow (e.g., 'Run npx typeorm migration:show -d src/data-source.ts before and after migration:run to verify state; never run schema:drop without confirming the target database').

Define the missing Profile entity (or remove the OneToOne relation and transaction example that references it) and make the schema:sync command consistent by always including the -d flag.

Move the full entity, subscriber, and transaction source listings into a references/ file (e.g., references/entities.md), keeping SKILL.md to the structure map, key conventions, and one compact example per pattern.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable code with almost no explanation of concepts Claude already knows; the only fat is minor duplication — the opening blockquote restates the frontmatter description, and the migration generate/run/schema:sync commands appear in both 'Database Initialization' and 'Common Commands'.	4 / 5
Actionability	Nearly everything is copy-paste ready (install commands, tsconfig flags, DataSource config, entities, repository functions, subscriber, transaction), but there are concrete gaps: the User entity and transaction example import a 'Profile' entity that is never defined or listed in the project structure, 'npx typeorm schema:sync' appears once without the required '-d' flag, and the install line hardcodes the 'pg' driver despite advertising MySQL/SQLite support.	4 / 5
Workflow Clarity	The scaffold-to-migration sequence is implicit in the section ordering and commands exist, but workflows involving destructive/batch database operations (schema:sync, schema:drop, migration:run) lack explicit validation checkpoints such as 'run migration:show to verify state before/after' — the missing-feedback-loop guideline caps this at 3. It is not a 2 because the commands themselves are correct and well-ordered.	3 / 5
Progressive Disclosure	Sections are clearly organized with headers and a project-structure map, but the ~250 lines of complete entity/repository/subscriber source code are inline reference material in a single SKILL.md with no bundle files, fitting the 'content that should be separate is inline' anchor rather than the well-split 4.	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.

A highly specific, well-scoped description that names the exact technology and its concrete capabilities. Its only real weakness is the complete absence of a 'when to use' trigger clause, which both caps completeness and leaves invocation guidance implicit.

Suggestions

Append an explicit trigger clause such as 'Use when starting a new TypeORM project, adding entities or migrations to an existing one, or when the user mentions TypeORM, DataSource, or typeorm migrations.'

Add one or two natural synonyms or environment terms (e.g., 'ORM', 'PostgreSQL/MySQL/SQLite') to broaden keyword coverage for users who don't name TypeORM directly.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — 'Scaffold a TypeORM 0.3+ project with TypeScript, entities with decorators, CLI migrations, repositories, DataSource configuration, relations, query builder, and subscribers' — giving comprehensive, specific coverage of the skill's scope, matching the top anchor.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 4 because 'when' is not even weakly implied, and not a 2 because the 'what' is fully explicit.	3 / 5
Trigger Term Quality	Terms like 'TypeORM', 'entities', 'CLI migrations', 'repositories', 'DataSource', 'query builder', and 'subscribers' are exactly what a user working with this ORM would say, but common variations such as 'ORM', 'PostgreSQL/MySQL/SQLite', or 'database' are absent, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Naming a specific ORM ('TypeORM 0.3+') with its concrete artifacts (migrations, DataSource, subscribers) carves out a clear niche with minimal conflict risk; only another TypeORM skill would overlap, which is the correct trigger.	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
Revision: 181fcbc

Reviewed: 7 days ago

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.

typeorm-starter

Table of Contents

Is this your skill?