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 fails on all dimensions: it describes no concrete actions, includes no natural trigger terms, lacks both 'what' and 'when' guidance, and is too generic to be distinguishable from other skills. It would be nearly useless for Claude to select appropriately from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates database test fixtures, creates mock data, sets up and tears down test databases, validates schema migrations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to write database tests, create test fixtures, mock database connections, generate test data, or set up test databases.'
Remove the redundant duplicate trigger term ('database test helper' listed twice) and replace with diverse natural keywords users would actually say, such as 'DB tests', 'test data setup', 'database mocking', 'integration tests', 'SQL test fixtures'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Database Test Helper') and its category ('Test Automation') without describing what it actually does—no verbs like 'generates', 'validates', 'creates', or any specific capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the 'what' is entirely absent beyond the skill name. The description is essentially metadata without substance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database test helper' repeated twice, which is not a natural phrase users would say. It misses common variations like 'database testing', 'test fixtures', 'mock database', 'test data', 'SQL tests', 'DB setup', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from any other testing-related or database-related skill. 'Database Test Helper' and 'Test Automation' are broad categories that could overlap with many other 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/placeholder with no actual instructional content. It repeatedly references 'database test helper' without ever defining what that means, how to do it, or providing any code, commands, or concrete guidance. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable code examples showing database test setup (e.g., in-memory SQLite for pytest, test containers, Jest with Prisma/Knex) with teardown and fixture patterns.
Define a clear workflow: 1) Set up test database, 2) Seed test data, 3) Run tests, 4) Validate results, 5) Clean up—with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual technical instructions and patterns.
Add references to specific frameworks (pytest fixtures with database sessions, Jest beforeAll/afterAll patterns) with copy-paste ready code snippets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('database test helper') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of database test setup, teardown, fixtures, or mocking. The content describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without delivering any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed materials, no links to examples or related files, and no meaningful structural organization beyond boilerplate headings. | 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
3076d78
- 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.