This is a minimally informative description consisting of a single word. It fails on every dimension: it provides no concrete actions, no trigger terms, no guidance on when to use it, and is indistinguishable from any other data-related skill. It is essentially unusable for skill selection.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates and modifies database schemas, writes SQL queries, manages migrations, and optimizes indexes.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions databases, SQL, queries, tables, schemas, migrations, PostgreSQL, MySQL, SQLite, or .sql files.'

Include file types or technology names to improve distinctiveness, e.g., referencing specific database engines or ORM frameworks the skill supports.

Dimension	Reasoning	Score
Specificity	The description is a single word 'database' with no actions described whatsoever — no verbs, no concrete capabilities, purely abstract.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause or any functional description.	1 / 3
Trigger Term Quality	Only the generic term 'database' is present. No natural variations (e.g., SQL, query, schema, tables, migrations, .db) or user-facing keywords are included.	1 / 3
Distinctiveness Conflict Risk	The term 'database' is extremely generic and could conflict with any skill involving data storage, SQL, migrations, ORMs, or data analysis.	1 / 3
	Total	4 / 12 Passed

Implementation

22%

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

This skill is dangerously underspecified for production database operations. It lacks any concrete commands, SQL examples, tool names, validation steps, or safety checks for destructive operations like dropping tables and columns. The content reads more like a vague team wiki stub than an actionable skill for Claude.

Suggestions

Add concrete, executable examples: specific migration commands (e.g., `alembic upgrade head`), SQL for dropping columns with safety checks, and the actual tool names used.

Add explicit validation and rollback steps for destructive operations—e.g., verify no references exist before dropping a column, back up before migration, validate schema after changes.

Include a clear multi-step workflow with checkpoints, such as: 1) Check current schema state, 2) Run migration in staging, 3) Validate, 4) Apply to production, 5) Verify.

Specify how to access the team vault for credentials (e.g., a concrete command or path) rather than just mentioning it exists.

Dimension	Reasoning	Score
Conciseness	The content is short and doesn't over-explain concepts Claude already knows, but it's also so sparse that the tokens it does use don't convey much actionable value—phrases like 'Check with the backend team' and 'Coordinate with the team' are filler rather than useful instruction.	2 / 3
Actionability	The skill provides no concrete commands, code, tool names, or executable steps. Instructions like 'Run migrations using the team migration tool' and 'Remove tables and columns' are entirely vague with no specific commands, SQL examples, or tool invocations.	1 / 3
Workflow Clarity	There are no sequenced steps, no validation checkpoints, and no feedback loops for what are explicitly destructive database operations (removing tables/columns, running migrations). This is especially problematic given the scoring notes about destructive changes requiring validation.	1 / 3
Progressive Disclosure	The content is organized into clear sections (Migrations, Maintenance, Notes), which is reasonable structure. However, there are no references to supporting files, no links to migration tool docs or SQL examples, and no bundle files to support deeper content.	2 / 3
	Total	6 / 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
description_field	'description' is very short (8 chars), consider making it more detailed	Warning

	Total	10 / 11 Passed

Reviewed

about 16 hours ago

Table of Contents

Discovery Implementation Validation