managing-database-testing
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-testingThis skill manages database testing by generating test data, wrapping tests in transactions, and validating database schemas. It is used to create robust and reliable database interactions. Claude uses this skill when the user requests database testing utilities, including test data generation, transaction management, schema validation, or migration testing. Trigger this skill by mentioning "database testing," "test data factories," "transaction rollback," "schema validation," or using the `/db-test` or `/dbt` commands.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is largely descriptive rather than instructive. It explains what database testing involves but fails to provide any executable code, concrete commands, or specific implementation details. The content reads like documentation about a feature rather than actionable guidance Claude can use to actually perform database testing tasks.
Suggestions
Replace abstract descriptions with executable Python code examples showing actual test data factories using Faker and SQLAlchemy
Add concrete transaction wrapper code with pytest fixtures demonstrating automatic rollback patterns
Include specific schema validation commands or scripts with example output and error handling
Remove the 'How It Works' and 'When to Use' sections entirely - Claude doesn't need to be told when to use its own skills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Verbose and padded with unnecessary context. Explains obvious concepts like 'what transactions do' and 'what schema validation means' that Claude already knows. The 'How It Works' and 'When to Use' sections repeat information Claude doesn't need. | 1 / 3 |
Actionability | No executable code provided despite being a database testing skill. Examples describe what 'the skill will do' abstractly rather than providing concrete, copy-paste ready code for test data generation, transaction wrapping, or schema validation. | 1 / 3 |
Workflow Clarity | No clear step-by-step workflows with validation checkpoints. The examples say 'the skill will generate code' but don't show the actual workflow or validation steps. Missing feedback loops for database operations which are inherently risky. | 1 / 3 |
Progressive Disclosure | Content is organized into logical sections (Overview, How It Works, Examples, Best Practices), but everything is inline in one file. No references to external files for detailed implementations, API references, or extended examples that would be appropriate for a database testing skill. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche in database testing that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generating test data', 'wrapping tests in transactions', 'validating database schemas', and mentions 'migration testing'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (manages database testing via test data generation, transactions, schema validation) AND when (explicit 'Use when' equivalent with 'Claude uses this skill when...' and 'Trigger this skill by mentioning...' clauses). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'database testing', 'test data factories', 'transaction rollback', 'schema validation', plus command shortcuts '/db-test' and '/dbt'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on database testing utilities with distinct triggers like 'test data factories', 'transaction rollback', 'schema validation', and dedicated commands. Unlikely to conflict with general database or general testing 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.