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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill database-schema-designerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a placeholder than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or explicit usage guidance. The only distinguishing element is the domain mention ('database schema'), but without specifics, Claude would struggle to select this skill appropriately from a larger skill set.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Design database tables, define relationships and foreign keys, create indexes, generate SQL DDL statements, normalize data structures'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks about database design, creating tables, data modeling, ERD diagrams, SQL schema, or database structure'
Add common file types or technologies: 'Works with PostgreSQL, MySQL, SQLite schemas, .sql files, migration files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Database Schema Designer') without describing any concrete actions. There are no specific capabilities listed like 'create tables', 'define relationships', 'generate migrations', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or trigger guidance beyond the redundant trigger terms). | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'database schema designer' repeated twice - no natural variations users would say like 'create tables', 'design database', 'ERD', 'data model', 'SQL schema', or 'database structure'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'database schema' is somewhat specific to a domain, the lack of concrete actions means it could overlap with general database skills, SQL skills, or backend development skills. The category mention provides some context but doesn't clearly distinguish it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about database schema design. It contains only meta-descriptions of what a skill should do without any concrete guidance, examples, code, or workflows. The content would provide zero value to Claude when performing database schema design tasks.
Suggestions
Add concrete examples of schema design patterns (e.g., one-to-many relationships, junction tables, indexing strategies) with actual SQL DDL code
Include a workflow for schema design: requirements analysis → entity identification → normalization → indexing → validation steps
Provide specific guidance for common scenarios: user authentication tables, audit logging, soft deletes, versioning patterns
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actionable, specific instructions
| 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 | Contains zero concrete guidance, no code examples, no specific commands, and no actual instructions for database schema design. The entire content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. Database schema design involves multiple decisions (normalization, indexing, relationships) that are completely unaddressed. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no examples, no links to schema patterns or templates. The content is a shallow placeholder with nothing to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.