database-schema-designer

Quick Review

The skill has acceptable structural organization but severely lacks substantive content. The description is repetitive and generic, failing to explain what database schema design capabilities are actually provided. There is no concrete task knowledge—no methodology for analyzing requirements, generating schemas, normalizing tables, defining relationships, or choosing data types. The skill reads more like a template than a functional resource. A CLI agent would not know HOW to design a database schema from this documentation. To be useful, it needs: (1) clear explanation of schema design capabilities (ERD generation, normalization guidance, indexing strategies), (2) concrete steps or scripts for common tasks (e.g., converting requirements to tables, generating migration files), and (3) examples of actual schema designs with rationale. Currently provides negligible value over a generic LLM.