vkc-drizzle-schema-migration
Standardize Drizzle schema/migration/seed workflow for Viet K-Connect. Use when adding or changing DB tables, especially DB-driven visa rulesets and document templates (no hardcoding). (키워드= 드리즐, DB 스키마, 마이그레이션, seed, schema.ts, migrations)
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.codex/skills/vkc-drizzle-schema-migration/SKILL.mdQuality
Discovery
89%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 well-crafted skill description that clearly identifies its niche (Drizzle ORM workflow for a specific project), provides explicit 'Use when' guidance, and includes bilingual trigger keywords. The main weakness is that the specific actions could be more granular—listing discrete operations like 'create migration files, update schema definitions, generate seed data' rather than the broader 'standardize workflow' framing.
Suggestions
List more concrete discrete actions (e.g., 'create migration files, define table schemas, generate seed data, update enum types') instead of the umbrella term 'standardize workflow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Drizzle schema/migration/seed workflow) and some actions (adding or changing DB tables, visa rulesets, document templates), but doesn't list multiple concrete discrete actions like 'create migration files, generate seed data, update schema definitions'. | 2 / 3 |
Completeness | Clearly answers both 'what' (standardize Drizzle schema/migration/seed workflow, DB-driven visa rulesets and document templates) and 'when' ('Use when adding or changing DB tables, especially DB-driven visa rulesets and document templates') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords in both English and Korean: 'Drizzle', 'DB tables', 'schema', 'migration', 'seed', 'schema.ts', plus Korean keywords '드리즐, DB 스키마, 마이그레이션'. Also includes domain-specific terms like 'visa rulesets' and 'document templates' that users in this project would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to a particular project (Viet K-Connect) and a particular technology (Drizzle ORM) with a clear niche around DB schema management, migrations, and seeding. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that efficiently communicates the Drizzle workflow for the VKC project. Its main weaknesses are the lack of concrete code examples (e.g., a sample table definition for visa rulesets) and missing validation/error-recovery steps in the migration workflow. Adding these would elevate it from a good reference to a fully actionable guide.
Suggestions
Add a concrete, executable code example of a schema table definition (e.g., a visa rulesets table in Drizzle syntax) to improve actionability.
Add a validation checkpoint after step 3 (e.g., verify migration applied correctly by checking table existence or running a quick query) and error recovery guidance if migration fails.
Ensure the referenced file `.codex/skills/vkc-drizzle-schema-migration/references/drizzle-rules.md` exists in the bundle and contains the promised rules and examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose, no concepts are over-explained, and Claude's intelligence is respected throughout. No unnecessary preamble or explanation of what Drizzle is. | 3 / 3 |
Actionability | Provides specific file paths and npm commands (db:generate, db:migrate, db:seed), but lacks executable code examples for schema definitions. A concrete example of a table definition (e.g., visa rulesets table) would make this fully actionable. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (update schema → generate → apply → seed), but there are no validation checkpoints or error recovery steps. After applying a migration, there's no guidance on verifying success or handling failures, which is important for destructive DB operations. | 2 / 3 |
Progressive Disclosure | References a deeper file (drizzle-rules.md) for rules and examples, which is good structure. However, the bundle has no files provided, so the referenced path cannot be verified. The reference is one-level deep and clearly signaled, but only a single reference exists — an additional reference for common patterns or examples would improve navigation. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- LEE-SANG-BOK/VKC-2-
- Commit
4a5dcd1
- 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.