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
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 title with boilerplate metadata and no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other backend/database skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs database schemas, defines table structures and relationships, generates SQL DDL statements, creates ERDs, and plans migrations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about database design, table creation, foreign keys, data modeling, SQL schema, ERD diagrams, or database migrations.'
Remove the duplicate trigger term ('database schema designer' is listed twice) and expand with varied natural language terms users would actually say, such as 'create tables', 'normalize database', 'define columns', 'primary key', 'indexes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Database Schema Designer') but provides no concrete actions. There is no mention of what the skill actually does—no verbs like 'creates tables', 'defines relationships', 'generates migrations', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks an explicit 'when should Claude use it' clause. There is no 'Use when...' guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database schema designer' repeated twice. It misses natural user phrases like 'create tables', 'define columns', 'foreign keys', 'ERD', 'migrations', 'SQL schema', 'data model', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'database schema designer' is somewhat specific to a niche (schema design), which provides some distinctiveness. However, without concrete actions or clear triggers, it could overlap with general database or backend development 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 placeholder with no substantive content. It repeats the phrase 'database schema designer' without providing any actual guidance, code examples, schema patterns, or workflows. It fails on every dimension because it contains zero actionable information about database schema design.
Suggestions
Add concrete, executable examples such as SQL CREATE TABLE statements demonstrating normalization, indexing strategies, and relationship patterns (1:1, 1:N, M:N).
Define a clear workflow for schema design: e.g., 1) Identify entities → 2) Define relationships → 3) Normalize → 4) Add indexes → 5) Validate with a migration tool.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with specific patterns like naming conventions, common anti-patterns to avoid, and migration strategies.
Include concrete examples for different databases (PostgreSQL, MySQL, SQLite) with copy-paste-ready DDL and reference files for advanced topics like partitioning or sharding.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'database schema designer' excessively, and provides zero actual technical content. Every section is padded with generic phrasing. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no schema examples, no SQL, no specific patterns. The skill describes what it could do rather than instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, no validation checkpoints, and no actual procedure for designing a database schema. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to disclose progressively. | 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.