drizzle-starter
Scaffold a Drizzle ORM project with TypeScript, schema definition (pgTable/mysqlTable), migrations via drizzle-kit, query builder, relations, Drizzle Studio, and type-safe queries.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
82%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, listing concrete Drizzle ORM features and technology-specific terms that make it easily identifiable. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill over others in a large skill library.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when setting up Drizzle ORM, creating database schemas with Drizzle, or when the user mentions drizzle-kit, pgTable, or type-safe database queries'.
Consider adding common user phrasings like 'database setup', 'ORM configuration', or 'PostgreSQL/MySQL schema' to capture broader intent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold a Drizzle ORM project', 'schema definition (pgTable/mysqlTable)', 'migrations via drizzle-kit', 'query builder', 'relations', 'Drizzle Studio', and 'type-safe queries'. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Drizzle ORM', 'TypeScript', 'pgTable', 'mysqlTable', 'drizzle-kit', 'migrations', 'Drizzle Studio', 'type-safe queries', 'schema definition'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology references (Drizzle ORM, drizzle-kit, Drizzle Studio, pgTable/mysqlTable) that clearly differentiate it from other ORM or database skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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, actionable skill with comprehensive, executable code examples covering the full Drizzle ORM workflow. The main weaknesses are the lack of explicit validation/verification steps in the migration workflow and the monolithic structure that could benefit from splitting detailed schema examples into separate reference files.
Suggestions
Add explicit validation checkpoints to the migration workflow, e.g., 'After generate, review the SQL in drizzle/migrations/ before running migrate' and error recovery steps for common migration failures.
Consider splitting the detailed schema examples (users.ts, posts.ts, tags.ts, relations.ts, repositories) into a separate EXAMPLES.md or SCHEMAS.md file, keeping SKILL.md as a concise overview with one minimal example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a purpose with executable code examples and no unnecessary padding. | 3 / 3 |
Actionability | Fully executable code throughout - complete TypeScript examples for schemas, repositories, transactions, and migrations. All commands are copy-paste ready with real-world patterns including pagination, filtering, and relations. | 3 / 3 |
Workflow Clarity | Commands are listed clearly but lack explicit validation checkpoints. The migration workflow (generate -> migrate) doesn't include verification steps or error recovery guidance for when migrations fail or schema conflicts occur. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic file with ~300 lines of code examples that could be split into separate reference files. The Integration Notes mention other skills but don't provide clear navigation to detailed materials. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
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.