jbvc/database-architect
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and re-architecture of existing systems. Use PROACTIVELY for database architecture, technology selection, or data modeling decisions.
46
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description covers the domain well and includes an explicit 'Use when' clause, which is a strength. However, it relies heavily on buzzword-laden language ('Expert database architect', 'Masters', 'performance-first design') and uses first/third person inconsistently. The trigger terms could be more natural and cover more user-facing variations of how someone would ask for database help.
Suggestions
Replace marketing-style language ('Expert database architect', 'Masters') with third-person action verbs describing concrete capabilities (e.g., 'Designs database schemas, selects between SQL/NoSQL/TimeSeries technologies, plans migrations').
Add more natural trigger terms users would actually say, such as 'database design', 'which database to use', 'table structure', 'indexes', 'ERD', 'database schema', or 'data storage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database architecture) and several actions (technology selection, schema modeling, migration planning, normalization strategies), but many terms are broad categories rather than concrete discrete actions like 'create ER diagrams' or 'write migration scripts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (data layer design, technology selection, schema modeling, scalable architectures, migration planning) and 'when' ('Use PROACTIVELY for database architecture, technology selection, or data modeling decisions'), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'database architecture', 'schema modeling', 'SQL/NoSQL/TimeSeries', 'data modeling', and 'migration planning', but misses common user phrasings like 'database design', 'which database should I use', 'table structure', 'indexes', 'ORM', or 'database schema'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on database architecture and technology selection is fairly distinct, but broad terms like 'data layer design', 'scalable architectures', and 'performance-first design' could overlap with general backend architecture or system design skills. | 2 / 3 |
Total | 9 / 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 exhaustive but largely useless enumeration of database concepts, technologies, and patterns that Claude already knows. It contains no executable code, no concrete examples, no validation workflows, and no progressive disclosure structure. The content would be more effective at 10% of its current length with actual actionable guidance, specific decision frameworks, and concrete output templates.
Suggestions
Replace the massive 'Capabilities' enumeration with a concise decision framework (e.g., a table mapping access patterns to recommended database types with specific rationale).
Add concrete, executable examples: a sample schema design output, a Mermaid ERD example, a migration script template, and a technology selection matrix with actual decision criteria.
Add explicit validation checkpoints to the workflow, especially for migration planning (e.g., 'Validate migration plan against checklist: rollback tested? staging verified? data integrity checks defined?').
Extract the detailed technology lists and pattern catalogs into separate reference files (e.g., TECHNOLOGY_MATRIX.md, MIGRATION_PATTERNS.md) and keep SKILL.md as a focused overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive bullet-point lists cataloging technologies, concepts, and patterns that Claude already knows. The 'Capabilities' section alone is a massive enumeration of database concepts (normalization levels, index types, isolation levels, etc.) that adds no actionable value beyond what Claude inherently understands. The content reads like a textbook table of contents rather than a focused skill. | 1 / 3 |
Actionability | Despite its length, the skill contains zero executable code, no concrete commands, no specific examples with inputs/outputs, and no copy-paste ready guidance. Everything is abstract description ('Design schemas, indexes, and lifecycle policies') rather than concrete instruction. The 'Example Interactions' section lists prompts but provides no example responses or outputs. | 1 / 3 |
Workflow Clarity | The 4-step 'Instructions' workflow is extremely vague ('Choose the database model and architecture pattern') with no validation checkpoints, no feedback loops, and no concrete sequencing. The 'Response Approach' 10-step list is similarly abstract. For an architecture skill involving migrations and destructive changes, the absence of explicit validation steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files. Massive sections like the full capabilities enumeration (covering 15+ sub-categories with dozens of bullet points each) should be split into separate reference files. There is no navigation structure or clear hierarchy beyond flat H3 headings under a single document. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents