database-schema

Schema awareness - read before coding, type generation, prevent column errors

Quality

35%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/database-schema/SKILL.md

Quality

Discovery

14%

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 a terse, fragmented list of abstract concepts rather than a well-formed skill description. It fails to explain what concrete actions the skill performs, what technology or domain it targets specifically, and when Claude should select it. The lack of a 'Use when...' clause and the vague language make it poorly suited for skill selection among multiple options.

Suggestions

Add a clear 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks about database schemas, needs to inspect table structures before writing queries, or wants to generate types from a database.'

Replace the fragmented phrases with concrete action descriptions, e.g., 'Reads database schema definitions to understand table structures, generates TypeScript/language types from schema columns, and validates queries against schema to prevent column name errors.'

Specify the technology domain (e.g., SQL databases, PostgreSQL, Prisma, etc.) to reduce conflict risk with other schema-related skills.

Dimension	Reasoning	Score
Specificity	The description uses vague, fragmented phrases like 'read before coding', 'type generation', and 'prevent column errors' without explaining concrete actions. It reads more like a list of abstract goals than specific capabilities.	1 / 3
Completeness	The 'what' is only vaguely implied through fragments, and there is no 'when' clause or explicit trigger guidance whatsoever. Both components are very weak.	1 / 3
Trigger Term Quality	Terms like 'schema', 'type generation', and 'column errors' are somewhat relevant keywords a developer might use, but the description lacks common variations and natural phrasing users would actually say (e.g., 'database schema', 'SQL', 'ORM', 'migrations', 'table structure').	2 / 3
Distinctiveness Conflict Risk	'Schema awareness' and 'type generation' are broad concepts that could overlap with database skills, API schema skills, TypeScript type generation, ORM tools, and many other skills. There is no clear niche established.	1 / 3
	Total	5 / 12 Passed

Implementation

55%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with excellent workflow clarity, providing concrete executable examples and well-sequenced multi-step processes with validation checkpoints. However, it is severely bloated—full ORM schema definitions for four stacks, repetitive checklists, and extensive boilerplate that Claude already knows inflate the token cost significantly. The content desperately needs progressive disclosure, splitting stack-specific examples into separate reference files.

Suggestions

Cut the content by ~60%: remove full ORM model definitions (Claude knows how to write Drizzle/Prisma/SQLAlchemy schemas) and keep only the type inference/generation patterns that are the actual value-add.

Split stack-specific examples into separate files (e.g., `drizzle-schema.md`, `prisma-schema.md`) and reference them from a concise overview table in SKILL.md.

Consolidate the three overlapping checklists (Pre-Code Checklist, Setup/Per-Task Checklist, Anti-Patterns) into a single compact checklist to eliminate redundancy.

Remove the schema reference template example or move it to a separate template file—it's useful but takes up significant space inline.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Provides full ORM schema examples for 4 different stacks (Drizzle, Prisma, Supabase, SQLAlchemy) that Claude already knows how to write. The schema reference template, multiple ASCII box diagrams, and repetitive checklists (setup checklist, per-task checklist, pre-code checklist, anti-patterns list) all cover overlapping ground. Much of this could be condensed to 1/3 the length.	1 / 3
Actionability	Provides fully executable code examples across multiple stacks, specific CLI commands for type generation and migrations, concrete type-safe query examples showing correct vs incorrect usage, and a clear schema reference template. Everything is copy-paste ready.	3 / 3
Workflow Clarity	Multi-step workflows (TDD workflow, migration workflow, session start protocol) are clearly sequenced with explicit validation checkpoints. The migration workflow includes type-checking as a validation step, and the TDD workflow has a clear feedback loop where type errors catch schema drift before runtime.	3 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files despite having content that clearly should be split out (e.g., per-stack ORM examples could be in separate files, the schema reference template could be a standalone file). Everything is inlined in one massive document with no bundle files to support it.	1 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 65efb33

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.