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".
86
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates specific validation capabilities and provides explicit trigger phrases. The main weakness is the awkward opening ('Process use when') which appears to be a grammatical error, and some potential overlap with general data validation skills. The description effectively covers what the skill does and when to use it.
Suggestions
Fix the grammatical error at the start — 'Process use when' should be rephrased to something like 'Use when you need to ensure...' or 'Ensures database integrity through comprehensive data validation.'
Strengthen distinctiveness by emphasizing the database-specific nature more clearly, e.g., mentioning SQL constraints, schema validation, or specific database technologies to differentiate from general-purpose data validation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: validates data types, ranges, formats, referential integrity, and business rules. These are distinct, concrete validation capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (validates data types, ranges, formats, referential integrity, business rules) and 'when' (explicit trigger phrases provided with 'Trigger with phrases like...'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases like 'validate database data', 'implement data validation rules', 'enforce data integrity constraints', and 'validate data formats' — these are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | While it focuses on database data validation specifically, terms like 'validate data formats' and 'business rules' could overlap with general data validation or form validation skills. The database focus helps but isn't strongly distinctive enough for a 3. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete SQL examples and a well-sequenced workflow including safe two-phase constraint application. Its main weaknesses are moderate verbosity (narrative examples, some unnecessary prerequisite details) and a monolithic structure that could benefit from splitting detailed reference material into separate files. The error handling table is a strong addition that aids real-world usage.
Suggestions
Move the error handling table and detailed examples into a separate REFERENCE.md or EXAMPLES.md file, keeping only a brief summary and link in the main skill.
Trim the prerequisites section—Claude doesn't need to be told that credentials are needed or that backups are important; focus on non-obvious requirements like the NOT VALID PostgreSQL feature requiring version 9.4+.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and includes useful concrete SQL, but it's verbose in places—the prerequisites section explains obvious things (like needing credentials), the examples section narrates scenarios rather than showing compact input/output, and some explanations could be tightened. However, it doesn't over-explain basic concepts egregiously. | 2 / 3 |
Actionability | The skill provides fully executable SQL queries and DDL statements throughout—validation queries, ALTER TABLE statements, regex patterns, and specific constraint syntax for PostgreSQL and MySQL. The guidance is concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced with a logical progression: audit → detect violations → validate formats → generate constraints → apply in two phases → report. The two-phase safe application approach (NOT VALID then VALIDATE) is an explicit validation checkpoint, and step 2 explicitly requires documenting orphans before proceeding. Error handling table provides recovery paths. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to external files for detailed topics like trigger implementation patterns, regex libraries, or business rule examples. The error handling table and examples sections add significant length that could be split out. However, the sections are well-organized with clear headers. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.