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.
41
11%
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
22%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 essentially a placeholder that relies entirely on the skill name without providing meaningful content. It lacks concrete actions, useful trigger terms beyond the skill name itself, and any guidance on when Claude should select this skill. The redundant trigger terms ('sequelize model creator' listed twice) suggest auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Sequelize model definitions with data types, validations, associations, and migration files'
Include a proper 'Use when...' clause with natural trigger terms like 'database model', 'ORM setup', 'define table schema', 'sequelize associations', or 'Node.js database'
Remove redundant trigger terms and add variations users would naturally say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Sequelize Model Creator' without describing any concrete actions. It doesn't explain what creating a Sequelize model involves (e.g., defining schemas, associations, migrations, validations). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | Includes 'sequelize model creator' as a trigger term, which is relevant but limited. Missing natural variations users might say like 'database model', 'ORM', 'define schema', 'create table', or 'sequelize migration'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'Sequelize' provides some specificity to this ORM, but 'model creator' is generic and could overlap with other database/ORM skills. The lack of specific capabilities makes it harder to distinguish from general backend or database skills. | 2 / 3 |
Total | 6 / 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 actual content about Sequelize model creation. It consists entirely of meta-descriptions about what the skill claims to do without providing any actionable guidance, code examples, or concrete instructions. The content would be completely useless for helping Claude create Sequelize models.
Suggestions
Add executable code examples showing how to define a Sequelize model with common field types, associations, and validations
Include a concrete workflow for creating models: define schema -> add associations -> run migrations -> validate
Provide specific patterns for common scenarios like one-to-many relationships, timestamps, soft deletes, and custom getters/setters
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about Sequelize models. | 1 / 3 |
Actionability | Contains zero executable code, no concrete commands, and no actual guidance on creating Sequelize models. The entire content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. There are no sequences, validation checkpoints, or any process to follow. | 1 / 3 |
Progressive Disclosure | No meaningful structure or references to additional resources. The sections are organizational theater with no actual content to disclose progressively. No links to examples, API references, or detailed documentation. | 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
994edc4
- 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.