database-schema-visualizer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill database-schema-visualizerDatabase Schema Visualizer - Auto-activating skill for Visual Content. Triggers on: database schema visualizer, database schema visualizer Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or natural trigger terms. The repeated trigger term and generic category reference suggest this was auto-generated without meaningful content.
Suggestions
Add specific actions the skill performs, e.g., 'Generates entity-relationship diagrams from SQL schemas, visualizes table relationships, creates database documentation with cardinality notation'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to visualize database structure, create ERD diagrams, show table relationships, or generate schema documentation'
Add file type triggers users might mention: '.sql files', 'CREATE TABLE statements', 'database DDL', 'PostgreSQL/MySQL schemas'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Database Schema Visualizer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of generating diagrams, creating ERDs, parsing SQL, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name and doesn't describe actual use cases or scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database schema visualizer' repeated twice, which is the skill name itself. Missing natural user terms like 'ERD', 'entity relationship diagram', 'table relationships', 'database diagram', 'schema diagram', or 'visualize tables'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'database schema' provides some specificity that distinguishes it from general document or code skills, but 'Visual Content' category is vague and could overlap with other visualization skills. Without concrete actions, it's unclear how this differs from other database or diagramming tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance. It repeatedly references 'database schema visualizer' without ever explaining what tools to use (e.g., Mermaid, dbdiagram.io, PlantUML), providing syntax examples, or showing how to extract schema information from databases. The content fails on every dimension by describing capabilities without demonstrating them.
Suggestions
Add concrete code examples showing how to generate schema diagrams using specific tools (e.g., Mermaid ERD syntax, PlantUML database notation)
Include a workflow for extracting schema from actual databases (e.g., SQL queries to get table/column info, then transform to diagram syntax)
Provide at least one complete input-to-output example: given a database schema, show the exact diagram code produced
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual tool-specific instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually visualize a database schema. The content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for any database schema visualization task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to actual implementation details. | 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.