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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill database-test-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It provides only a skill name and category without describing any actual capabilities, use cases, or meaningful trigger terms. The description would be completely ineffective for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates test fixtures, seeds test databases, generates mock data, manages database state between tests')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when setting up test data, creating database fixtures, mocking database responses, or preparing test environments')
Add file types, frameworks, or technologies supported to distinguish from other testing skills (e.g., 'Works with PostgreSQL, MySQL, SQLite test databases and supports Jest, pytest, and RSpec frameworks')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Database Test Helper' is a name, not a capability description. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming a category. There is no 'Use when...' clause or explicit trigger guidance, and the 'when' is completely absent. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'database test helper' repeated twice, which is the skill name itself. No natural user language like 'test database', 'mock data', 'test fixtures', or 'database setup' is included. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Test Automation' and 'database test helper' could overlap with many testing-related skills. No specific niche or distinguishing features are defined. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what a database test helper skill might do but provides zero actionable guidance, code examples, or specific instructions for database testing. The content fails on all dimensions by being verbose yet empty of useful information.
Suggestions
Add concrete, executable code examples for common database testing patterns (e.g., setting up test databases, fixtures, mocking database connections)
Include specific step-by-step workflows for database test scenarios with validation checkpoints (e.g., setup -> seed data -> run tests -> cleanup)
Remove all generic boilerplate text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual guidance
Add framework-specific examples for Jest and pytest database testing as mentioned in the tags
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The entire skill describes what it could do rather than instructing how to do anything. There are no executable examples or specific database testing patterns. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for database testing tasks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. References to 'Related Skills' and tags exist but provide no navigable links or organized content hierarchy. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.