comparing-database-schemas

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill comparing-database-schemas

Process use when you need to work with schema comparison. This skill provides database schema diff and sync with comprehensive guidance and automation. Trigger with phrases like "compare schemas", "diff databases", or "sync database schemas".

51%

Overall

Validation — 81%

Implementation — 7%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

This skill is a generic template with no actual database diff/sync content. It describes a generic software development lifecycle that could apply to any task, completely failing to provide the schema comparison commands, diff tool usage, sync operations, or database-specific guidance promised in the description. The skill teaches Claude nothing it doesn't already know.

Suggestions

Replace generic lifecycle steps with actual database diff commands (e.g., `pg_dump --schema-only`, `mysqldiff`, or specific diff tool CLI usage)

Add concrete executable examples showing how to compare two schemas and interpret the diff output

Include specific validation steps for schema sync operations (e.g., dry-run commands, rollback procedures for failed migrations)

Remove all generic software development advice and focus only on database-diff-specific knowledge Claude wouldn't already have

Dimension	Reasoning	Score
Conciseness	Extremely verbose with generic boilerplate that applies to any task. Contains no database-diff-specific content - just generic software development lifecycle steps that Claude already knows. Every section could apply to literally any technical task.	1 / 3
Actionability	No concrete code, commands, or database-diff-specific guidance. Instructions like 'Review current configuration' and 'Execute implementation' are completely abstract with no executable examples, tool names, or actual diff commands.	1 / 3
Workflow Clarity	While steps are numbered, they are generic software lifecycle phases (assess, design, implement, validate, deploy) with no database schema comparison specifics. No actual diff workflow, no validation of schema differences, no sync commands or verification steps.	1 / 3
Progressive Disclosure	References external files in a structured Resources section with clear paths, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist, and the Overview/Examples sections at the end are empty placeholders.	2 / 3
	Total	5 / 12 Passed

Activation

90%

This description has strong trigger term coverage and completeness with explicit 'when to use' guidance. However, the specificity of capabilities is moderate - it mentions 'diff and sync' but doesn't detail what specific operations are performed (e.g., generate migration scripts, detect column changes, compare indexes). The awkward opening phrase 'Process use when you need to work with' is grammatically unclear.

Suggestions

Expand the capabilities section with specific concrete actions like 'detect table/column differences, generate migration scripts, compare indexes and constraints'

Fix the grammatically awkward opening 'Process use when you need to work with schema comparison' - consider 'Compares and synchronizes database schemas' instead

Dimension	Reasoning	Score
Specificity	Names the domain (database schema) and mentions actions like 'diff' and 'sync', but lacks specific concrete actions like what comparison outputs look like, what sync operations are performed, or what databases are supported.	2 / 3
Completeness	Clearly answers both what ('database schema diff and sync with comprehensive guidance and automation') and when ('Trigger with phrases like...'). Has explicit trigger guidance with example phrases.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases users would say: 'compare schemas', 'diff databases', 'sync database schemas'. These are realistic terms users would naturally use when needing this functionality.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on database schema comparison and synchronization. The specific trigger terms ('compare schemas', 'diff databases', 'sync database schemas') are distinct and unlikely to conflict with general database or document skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

13 days ago

Table of Contents

Validation Implementation Activation

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.