sequelize-model-creator
Sequelize Model Creator - Auto-activating skill for Backend Development. Triggers on: sequelize model creator, sequelize model creator Part of the Backend Development skill category.
36
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/sequelize-model-creator/SKILL.mdQuality
Discovery
7%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 is extremely thin and template-like, providing almost no useful information beyond the skill name. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. The repeated trigger term and boilerplate category mention add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Sequelize model definitions with field types, validations, associations, and migration files for Node.js applications.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks to create a Sequelize model, define database tables, set up ORM schemas, generate migrations, or work with Sequelize in a Node.js/Express project.'
Include common keyword variations users might say: 'database model', 'ORM', 'schema definition', 'model associations', 'Sequelize migration', '.sequelizerc'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Sequelize Model Creator') and mentions 'Backend Development' but does not describe any concrete actions like creating model files, defining associations, generating migrations, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line is just a repeated label, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'sequelize model creator' repeated twice. It misses natural user phrases like 'create a Sequelize model', 'define database schema', 'ORM model', 'database model', 'Node.js model', or 'sequelize migration'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Sequelize' provides some specificity to a particular ORM framework, which helps distinguish it from generic backend or database skills. However, the lack of detail about what it actually does could still cause overlap with other model-generation or database skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It contains zero actionable information about creating Sequelize models — no code examples, no model definition patterns, no migration guidance, no association examples, and no workflow. It reads as auto-generated boilerplate that would provide no value to Claude.
Suggestions
Add executable Sequelize model code examples showing `sequelize.define()` or class-based model definitions with common field types, validations, and associations.
Include a concrete workflow: 1) Define model, 2) Create migration, 3) Run migration, 4) Validate with `sequelize db:migrate:status`, with specific CLI commands.
Provide a quick-reference section covering common patterns like associations (hasMany, belongsTo, belongsToMany), hooks, scopes, and indexes with copy-paste ready code.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual instructional content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'sequelize model creator' excessively, and contains zero substantive information about actually creating Sequelize models. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples of Sequelize model definitions, migrations, or configurations. The content only describes what the skill could do in abstract terms without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- 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.