typeorm

Use when defining TypeORM entities, writing migrations, or building repository/query-builder code in TypeScript. Covers entity and relation decorators, the Data Mapper pattern, migrations, the query builder, transactions, and multi-database configuration.

Quality

74%

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

Quality

Content

61%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 skill provides a solid overview of TypeORM setup with executable entity and data source examples, and appropriately defers detailed API content to a reference file. Its main weaknesses are unnecessary introductory explanations Claude doesn't need (supported databases, platforms), and a significant gap in workflow clarity — particularly around migrations and transactions, which are core to the skill's stated purpose but lack step-by-step workflows with validation checkpoints.

Suggestions

Add a concrete migration workflow with validation steps: generate migration, review SQL, run migration, verify schema — with commands and a feedback loop for failures.

Remove the 'Core Principles' bullet list — Claude already knows what databases and platforms TypeORM supports; this wastes tokens.

Add a brief inline transaction example showing QueryRunner acquire/commit/rollback/release pattern, since transactions are listed as a core skill topic.

Trim the tsconfig explanation to just the JSON block — Claude knows what experimentalDecorators does.

Dimension	Reasoning	Score
Conciseness	The opening lines explaining what TypeORM supports (databases, platforms, patterns) are things Claude already knows. The tsconfig explanation that decorators 'won't compile' is also unnecessary. However, the entity example and data source config are reasonably tight, and the quick guidance section is efficient.	3 / 5
Actionability	Provides executable entity definition, full data source configuration, and concrete tsconfig settings. The quick guidance section gives specific method names and patterns. However, repository usage, query builder, migrations, and transactions are deferred entirely to reference.md with no inline examples, leaving gaps for common operations.	4 / 5
Workflow Clarity	The skill mentions migrations and warns against synchronize in production, but provides no migration workflow steps (generate, review, run, verify). There are no validation checkpoints for schema changes or database operations. The quick guidance about releasing QueryRunners hints at error handling but doesn't show a workflow. For a skill covering migrations and transactions, the lack of explicit validation/feedback loops is a notable gap.	3 / 5
Progressive Disclosure	Good structure with clear references to reference.md for detailed API content, and scripts for scaffolding. The SKILL.md serves as an overview with well-signaled pointers. However, no bundle files were provided, so we can't verify the referenced files exist. The inline data source config block is somewhat long but arguably belongs in the overview.	4 / 5
	Total	14 / 20 Passed

Description

87%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.

This is a strong skill description that clearly identifies both what the skill covers and when to use it. It provides specific TypeORM concepts and patterns, uses natural trigger terms that developers would use, and is highly distinctive from other potential database or ORM skills. Minor improvements could include additional synonym coverage for broader trigger matching.

Dimension	Reasoning	Score
Specificity	Lists several specific actions and concepts: defining entities, writing migrations, building repository/query-builder code, entity and relation decorators, Data Mapper pattern, transactions, and multi-database configuration. Minor gaps exist (e.g., no mention of subscribers, listeners, or specific CRUD operations), but coverage is strong.	4 / 5
Completeness	Explicitly answers both 'what' (covers entity/relation decorators, Data Mapper pattern, migrations, query builder, transactions, multi-database configuration) and 'when' (use when defining TypeORM entities, writing migrations, or building repository/query-builder code). The 'Use when' clause is concrete and specific with clear trigger phrases.	5 / 5
Trigger Term Quality	Includes strong natural keywords like 'TypeORM', 'entities', 'migrations', 'query builder', 'transactions', 'TypeScript', 'repository', and 'decorators'. Missing some synonyms or related terms users might say like 'ORM', 'database schema', 'relations', 'foreign key', or 'column decorators'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive with clear niche targeting TypeORM specifically in TypeScript. The combination of TypeORM-specific terminology (entity decorators, Data Mapper pattern, query builder) makes it very unlikely to conflict with general database, SQL, or other ORM skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: whimzyLive/nightshift-ai
Path: skills/typeorm/SKILL.md
Commit: 7741177

Reviewed: 10 days 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.