database-schema-visualizer
Database Schema Visualizer - Auto-activating skill for Visual Content. Triggers on: database schema visualizer, database schema visualizer Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/database-schema-visualizer/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 weak, essentially just restating the skill name with no substantive content. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The repeated trigger term and boilerplate category mention provide almost no useful information for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates entity-relationship diagrams, visualizes table structures, renders foreign key relationships, and maps database schemas as visual diagrams.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to visualize a database schema, create an ER diagram, map table relationships, or generate a visual representation of database tables, columns, and foreign keys.'
Include common file/format references users might mention, such as 'SQL DDL', '.sql files', 'CREATE TABLE statements', 'Mermaid diagrams', or 'ERD'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Database Schema Visualizer') without describing any concrete actions. There are no specific capabilities listed such as 'generates ER diagrams', 'visualizes table relationships', or 'renders foreign key connections'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is limited to a redundant trigger phrase. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database schema visualizer' repeated twice, which is the skill's own name rather than natural keywords users would say. Missing terms like 'ER diagram', 'table relationships', 'schema diagram', 'database visualization', 'entity relationship'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'database schema' provides some domain specificity that distinguishes it from generic visualization skills, but the lack of concrete actions and the vague 'Visual Content' category could cause overlap with other database or visualization tools. | 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/placeholder with no actual instructional content. It repeatedly names the skill topic ('database schema visualizer') without ever teaching Claude how to perform the task—no Mermaid ER diagram syntax, no SQL-to-diagram workflows, no code examples, no tool references. It provides zero value beyond what Claude already knows.
Suggestions
Add concrete, executable examples of database schema visualization (e.g., Mermaid ER diagram syntax from SQL DDL input, with a complete input→output example).
Define a clear workflow: e.g., 1) Parse schema source (SQL DDL, ORM models, or live DB), 2) Generate Mermaid/DOT diagram code, 3) Validate relationships and cardinality, 4) Render or output the diagram.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching the actual task.
Include at least one copy-paste-ready code block showing how to convert a sample CREATE TABLE statement into a Mermaid ER diagram.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'database schema visualizer' excessively, and contains no substantive information about how to actually visualize database schemas. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of actual schema visualization (e.g., Mermaid ER diagrams, SQL DDL parsing, or any tool usage). Every section is vague and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints—just abstract claims like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content across sections. | 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
3a2d27d
- 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.