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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill validating-database-integrity75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
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 both the 'what' and 'when' aspects effectively. The description is focused on a distinct domain (database data validation) with appropriate technical terminology that users would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'validates data types, ranges, formats, referential integrity, and business rules' - these are clear, 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 distinct triggers like 'database integrity', 'data integrity constraints', 'referential integrity' - unlikely to conflict with general data processing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good organizational structure and progressive disclosure with clear references to external resources. However, it critically lacks actionability - a database validation skill with no actual SQL examples, constraint syntax, or executable code makes it nearly useless for practical implementation. The content describes what to do conceptually but never shows how to do it.
Suggestions
Add concrete SQL examples for each constraint type (CHECK, FOREIGN KEY, NOT NULL) with copy-paste ready syntax
Include at least one complete worked example showing a validation rule from definition through implementation
Add explicit validation checkpoints with specific commands (e.g., 'Run: SELECT COUNT(*) FROM table WHERE column NOT LIKE pattern')
Remove the empty Overview and Examples sections at the end that add no value
| 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 Overview and Examples sections at the end add no value. | 2 / 3 |
Actionability | Despite being a database validation skill, there are zero executable SQL examples, no concrete code snippets, and only abstract descriptions like 'Generate SQL constraints' without showing what those constraints look like. | 1 / 3 |
Workflow Clarity | Steps are clearly sequenced with 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 constraint failures during implementation. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections and well-signaled references to external resources (database-specific docs, templates, testing guidelines). References are one level deep and appropriately organized for discovery. | 3 / 3 |
Total | 8 / 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 | |
- 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.