database-test-helper
Database Test Helper - Auto-activating skill for Test Automation. Triggers on: database test helper, database test helper Part of the Test Automation skill category.
33
0%
Does it follow best practices?
Impact
96%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/database-test-helper/SKILL.mdQuality
Discovery
0%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 description is essentially a placeholder with no substantive content. It provides only a skill name and category label without describing any capabilities, actions, or usage triggers. Claude would have no basis for selecting this skill appropriately from a skill library.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Generates test fixtures, creates mock database connections, validates SQL queries against test schemas').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when setting up database tests, creating test data, mocking SQL queries, or writing integration tests for data layers').
Remove the redundant trigger term repetition and replace with varied, natural keywords like 'test fixtures', 'mock data', 'database mocking', 'SQL testing', 'integration tests'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Database Test Helper' is a name, not a capability description. There are no verbs describing what the skill actually does (e.g., generate test data, mock queries, validate schemas). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the skill name and category without any functional description or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database test helper' repeated twice, which is the skill's own name rather than natural keywords users would say. Missing terms like 'test data', 'mock database', 'SQL tests', 'fixtures', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic. 'Database Test Helper' and 'Test Automation' could overlap with many testing-related skills. Without specific capabilities or triggers, Claude cannot distinguish when to use this over other testing or database skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It describes what a database test helper skill should do without providing any concrete guidance, code examples, or actionable instructions for database testing. The content is entirely meta-description rather than useful instruction.
Suggestions
Add concrete code examples for common database testing patterns (e.g., test fixtures, database mocking, transaction rollback patterns)
Include specific setup instructions for database test frameworks (pytest-django, jest with database mocks, etc.)
Provide executable examples showing how to create test databases, seed data, and clean up after tests
Replace the generic 'Capabilities' section with actual step-by-step workflows for database test scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual database testing guidance. It explains what the skill does in abstract terms without providing any concrete information Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any steps or examples. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for database testing tasks. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no examples, and no navigation to related content despite mentioning 'Related Skills'. | 1 / 3 |
Total | 4 / 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
e9f9c93
- 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.