database-schema

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with executable examples and well-sequenced, validated workflows, but it is verbose and keeps multi-stack detail inline rather than splitting it into one-level-deep reference files.

Suggestions

Move the per-stack type-generation code (Drizzle/Prisma/Supabase/SQLAlchemy) into separate reference files (e.g., references/stacks/*.md) and link to them from a concise overview to improve progressive disclosure.

Trim the worked schema-reference.md example table and the duplicate checklists, keeping only the structure that Claude cannot infer.

Consolidate the overlapping Setup/Per-Task checklist and Anti-Patterns section to reduce redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body avoids teaching concepts Claude already knows, but ~370 lines with full inline code for four stacks, a worked schema-reference table, and overlapping checklists could be tightened to reduce token load.	2 / 3
Actionability	It provides fully executable, copy-paste-ready code and commands for Drizzle, Prisma, Supabase, and SQLAlchemy, plus concrete ✅/❌ type-safe query examples and exact generation commands.	3 / 3
Workflow Clarity	Multi-step workflows (Core Rule, Schema-Aware TDD, Migration) are clearly sequenced with explicit validation checkpoints and a fix-and-revalidate feedback loop appropriate for database operations.	3 / 3
Progressive Disclosure	Sections are well organized, but no bundle files exist and per-stack code that could live in separate reference files is presented inline in a single monolithic document.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 is specific and occupies a clear niche, but it is written in terse technical shorthand without an inline 'Use when...' trigger, leaving completeness and trigger-term naturalness below the top level.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when writing database queries, modifying schemas, or generating types') so the trigger is inline rather than only in when-to-use.

Replace outcome phrasing like 'prevent column errors' with concrete actions and add natural user terms such as 'database schema', 'columns', and 'schema file'.

Use third-person action verbs and list a few more concrete capabilities (e.g., 'verify column names and types, regenerate types after migrations') to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Schema awareness") and several actions ("read before coding, type generation, prevent column errors"), but "prevent column errors" is an outcome rather than a concrete action and the list is not comprehensive.	2 / 3
Completeness	It states what the skill does, but the description field itself lacks an explicit 'Use when...' trigger clause; the when-guidance lives in the separate when-to-use field rather than inline, capping completeness per the rubric guideline.	2 / 3
Trigger Term Quality	Terms like "schema", "type generation", and "database queries" are relevant, but it leans technical and misses common natural variations a user would say such as "columns", "schema file", or "database schema".	2 / 3
Distinctiveness Conflict Risk	The database/schema niche with column and type-generation triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 7 hours 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.