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 essentially a placeholder that repeats the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
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 an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for ER diagrams, database visualization, schema diagrams, table relationship maps, or wants to see database structure visually.'
Remove the duplicate trigger term and replace with varied natural keywords users would actually say, such as 'ER diagram', 'database diagram', 'table relationships', 'schema visualization', '.sql visualization'.
| 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 both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful 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 visualization or database-related 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 shell—a template placeholder with no substantive content. It contains only meta-descriptions of what the skill would do without any actual instructions, code examples, tool references, or workflows for database schema visualization. It provides no value to Claude beyond what the skill's title already conveys.
Suggestions
Add concrete, executable code examples for generating database schema diagrams (e.g., Mermaid ER diagram syntax, dbdiagram.io DSL, or Python-based visualization with graphviz/sqlalchemy)
Define a clear workflow: e.g., 1) Extract schema from SQL/ORM, 2) Generate diagram markup, 3) Validate relationships, 4) Render output
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly instead of teaching how to do the task
Add specific examples showing input (e.g., a CREATE TABLE statement) and expected output (e.g., a Mermaid ER diagram block)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete examples, no schemas, no tool usage. The 'Capabilities' section lists abstract promises ('provides step-by-step guidance') without delivering any actual steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 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
b8a3b3e
- 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.