validating-database-integrity
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill validating-database-integrityProcess 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".
Validation
81%| 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
42%This skill has good organizational structure and progressive disclosure but critically lacks actionability - there are no executable SQL examples, constraint syntax, or concrete validation queries despite being a database validation skill. The content describes what to do at a high level but doesn't show how to do it, making it more of a process checklist than a practical skill guide.
Suggestions
Add concrete SQL examples for each constraint type (CHECK, FOREIGN KEY, NOT NULL) with copy-paste ready syntax
Include example validation queries to identify constraint violations (e.g., SELECT statements that find invalid data)
Provide a specific data cleanup script example showing UPDATE/DELETE patterns for common violation fixes
Remove the empty Overview and Examples sections at the end, or populate them with actual executable examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes unnecessary padding like 'This skill provides automated assistance for data validation engine tasks' and generic sections. The step-by-step instructions could be more concise, and the Overview/Examples sections at the end add no value. | 2 / 3 |
Actionability | Despite detailed steps, there is no executable code - no SQL examples, no actual constraint syntax, no concrete validation queries. Instructions like 'Generate SQL constraints' and 'Create validation rule definitions' describe rather than demonstrate. | 1 / 3 |
Workflow Clarity | Steps are clearly sequenced with a logical progression (analyze → define → implement → validate → apply), and there's mention of staging-first deployment. However, validation checkpoints are implicit rather than explicit, and there's no clear feedback loop for the constraint application process itself. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections and well-organized references to external resources (database-specific docs, templates, testing guidelines). References are one level deep and clearly signaled with file paths. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
100%This is a well-crafted skill description that clearly articulates specific validation capabilities and provides explicit trigger phrases. It uses proper third-person voice and covers the database integrity domain comprehensively. The only minor issue is the awkward 'Process use when' opening phrase which appears to be a typo or grammatical error.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'validates data types, ranges, formats, referential integrity, and business rules' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('validates data types, ranges, formats, referential integrity, and business rules') and when ('Trigger with phrases like...' provides explicit trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'validate database data', 'implement data validation rules', 'enforce data integrity constraints', 'validate data formats' - good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on database data validation with specific triggers around 'database', 'integrity constraints', and 'data validation rules' - unlikely to conflict with general document or code skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
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.