validating-database-integrity

Process use when you need to ensure database integrity through comprehensive data validation. This skill validates data types, ranges, formats, referential integrity, and business rules. Trigger with phrases like "validate database data", "implement data validation rules", "enforce data integrity constraints", or "validate data formats".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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 and lean, with a well-sequenced, validated workflow for destructive database operations. Its one weakness is progressive disclosure: bundled scripts and report templates exist but are never referenced or linked from SKILL.md, leaving actionable resources undiscoverable.

Suggestions

Reference the bundled scripts inline where relevant — e.g. under a 'Scripts' section, link to scripts/configure_validation_rules.py for rule setup and scripts/generate_validation_report.py for the report mentioned in step 10.

Point to assets/validation_report_template.html from the Output or Examples section so the report template is discoverable.

Consider moving the per-column regex validators or the error-handling table into a references/ file to keep SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no preamble explaining what CHECK constraints or foreign keys are, and every line is actionable SQL; not 2 because there is no unnecessary explanation to tighten.	3 / 3
Actionability	Provides fully executable, copy-paste-ready SQL throughout (e.g. 'ALTER TABLE products ADD CONSTRAINT chk_price_positive CHECK (price >= 0)' and the duplicate-detection query), plus concrete regex validators and trigger patterns; not 2 because it is complete executable code rather than pseudocode.	3 / 3
Workflow Clarity	Presents a clear 10-step sequence with explicit validation checkpoints and a safe two-phase constraint application ('Phase 1 ... Phase 2 ... NOT VALID ... VALIDATE CONSTRAINT'), complemented by an error-handling table giving recovery loops; not 2 because validation and feedback steps are explicit, not implicit.	3 / 3
Progressive Disclosure	Sections are well-organized (Overview, Instructions, Error Handling, Examples) but the body is a monolithic ~85 lines of inline SQL and never signals the existing bundle files (scripts/configure_validation_rules.py, scripts/generate_validation_report.py, assets/validation_report_template.html); not 3 because references are not clearly signaled from the body, and not 1 because it is not a disorganized wall of text.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 strong across all dimensions: it states concrete capabilities, includes explicit natural-language triggers, answers both what and when, and occupies a clear distinct niche. A minor grammatical roughness ('Process use when...') does not undermine its specificity or third-person voice.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'validates data types, ranges, formats, referential integrity, and business rules' — matching the comprehensive multi-action anchor; not 2 because coverage is broad rather than partial.	3 / 3
Completeness	Explicitly answers both what it does (validates data types, ranges, formats, referential integrity, business rules) and when to use it via the 'Trigger with phrases like' clause; not 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	Provides several natural trigger phrases users would say — 'validate database data', 'implement data validation rules', 'enforce data integrity constraints', 'validate data formats' — with good variation; not 2 because multiple natural keywords are present.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche (database integrity validation) with distinct, domain-specific triggers unlikely to fire for unrelated skills; not 2 because it is clearly distinguishable rather than overlapping.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

Reviewed: 1 day 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.