database-schema-designer
Database Schema Designer - Auto-activating skill for Backend Development. Triggers on: database schema designer, database schema designer Part of the Backend Development skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage 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/database-schema-designer/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 essentially a placeholder with no substantive content. It fails to describe what the skill does, provides no natural trigger terms beyond the skill name repeated, and offers no guidance on when Claude should select it. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Designs database schemas, creates table definitions, establishes relationships between entities, generates SQL DDL statements, and normalizes data structures.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions database design, table creation, ERD, data modeling, foreign keys, schema migration, or SQL table structure.'
Remove the redundant trigger term ('database schema designer' appears twice) and replace with varied natural language users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Database Schema Designer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating tables, defining relationships, generating migrations, or any other specific database design activities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states it's an auto-activating skill for backend development with no explanation of capabilities or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database schema designer' repeated twice, which is the skill name itself. Missing natural user phrases like 'create tables', 'define columns', 'foreign keys', 'ERD', 'data model', 'SQL schema', or 'database design'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'database schema' is somewhat specific to a domain, the lack of detail means it could overlap with general database skills, SQL skills, or ORM-related skills. The category 'Backend Development' is too broad to provide distinctiveness. | 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 content is essentially a placeholder template with no actual substance. It repeatedly references 'database schema designer' without providing any concrete guidance on schema design patterns, normalization, relationships, indexing strategies, or any other actionable database design knowledge. The content fails on all dimensions by being verbose yet empty of useful information.
Suggestions
Add concrete code examples showing actual database schema definitions (e.g., SQL CREATE TABLE statements, ORM model definitions for Node.js/Python/Go)
Include specific schema design patterns with examples: normalization levels, relationship types (1:1, 1:N, M:N), indexing strategies
Provide a clear workflow for schema design: requirements analysis -> entity identification -> relationship mapping -> normalization -> indexing -> validation
Replace generic capability claims with actual techniques: 'For many-to-many relationships, use junction tables: CREATE TABLE user_roles (user_id INT REFERENCES users, role_id INT REFERENCES roles, PRIMARY KEY (user_id, role_id))'
| 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. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual database schema design patterns or techniques. The content describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for database schema design tasks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or related documentation. There's no structure that would help navigate to actual useful content. | 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.