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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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 a clear, validated two-phase workflow and executable SQL throughout, but it is somewhat verbose and fails to wire its existing bundle scripts into the body for navigation. Tightening the examples and referencing the report-generation script would raise the weaker dimensions.

Suggestions

Reference the bundled generate_validation_report.py and configure_validation_rules.py scripts from the Instructions or Output sections so the bundle is discoverable and progressive disclosure improves.

Tighten the Examples section and condense the Error Handling table to reduce verbosity while preserving the actionable SQL.

Reconcile the scripts README with the actual bundle: validate_data.py is listed but absent — either add it or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable SQL and no concept tutorials, but it is long and the Examples section plus the verbose error-handling table add illustrative padding that could be tightened, matching the score-2 'mostly efficient but could be tightened' anchor rather than the lean score-3.	2 / 3
Actionability	Provides fully executable, copy-paste-ready SQL for auditing, referential checks, regex validation, CHECK/FK constraints, triggers, and a two-phase NOT VALID application, matching the score-3 fully-executable anchor.	3 / 3
Workflow Clarity	A 10-step sequence with an explicit two-phase approach (find violations + cleanup, then apply constraints with NOT VALID and validate) and an error-handling table providing feedback loops matches the score-3 anchor with explicit validation checkpoints for these database operations.	3 / 3
Progressive Disclosure	Bundle scripts exist (configure_validation_rules.py, generate_validation_report.py) and a referenced validate_data.py is missing, but the body never links to or signals any bundle file, leaving the instructions as an inline monolith — matching the score-2 anchor of references present but not signaled and inline content that should be separate.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, complete, and distinct, clearly stating both what the skill does and when to trigger it with natural phrases. The only weakness is the awkward opening wording 'Process use when' which is grammatically broken but remains third-person and does not materially reduce the scores.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'validates data types, ranges, formats, referential integrity, and business rules' — matching the score-3 anchor for multiple specific concrete actions rather than the partial score-2.	3 / 3
Completeness	Explicitly answers both 'what' (validation of types, ranges, formats, referential integrity, business rules) and 'when' ('Trigger with phrases like ...'), satisfying the score-3 anchor for both what and when.	3 / 3
Trigger Term Quality	Provides natural user phrases ('validate database data', 'implement data validation rules', 'enforce data integrity constraints', 'validate data formats') with good coverage, matching the score-3 anchor rather than the partial score-2.	3 / 3
Distinctiveness Conflict Risk	The database-integrity niche with distinct validation/enforcement triggers is clearly separated from unrelated skills and unlikely to conflict, matching the score-3 clear-niche anchor.	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
Path: plugins/database/data-validation-engine/skills/validating-database-integrity/SKILL.md
Commit: 4c47e33

Reviewed: 2 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.