test-organization-helper
Test Organization Helper - Auto-activating skill for Test Automation. Triggers on: test organization helper, test organization helper Part of the Test Automation skill category.
32
Quality
0%
Does it follow best practices?
Impact
91%
1.01xAverage 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/test-organization-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 lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The only information provided is the skill name and a generic category, making it impossible for Claude to effectively select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions describing what the skill does, e.g., 'Organizes test files into logical directories, groups related tests into suites, generates test index files, and restructures test hierarchies'
Include a 'Use when...' clause with natural trigger terms like 'organize tests', 'restructure test files', 'group tests', 'test folder structure', 'test suite organization'
Remove the duplicate trigger term and replace with varied natural language phrases users would actually say when needing this functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Test Organization Helper' and category 'Test Automation'. There are no specific capabilities like 'organizes test files', 'groups tests by feature', or 'creates test suites'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('test organization helper, test organization helper'). No natural user keywords like 'organize tests', 'test structure', 'test folders', 'group tests', or 'test suites' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Test Automation' could overlap with many testing-related skills. Without specific actions or clear triggers, this would conflict with any other test-related skill. | 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 a placeholder template with no actual content. It describes capabilities in abstract terms but provides zero actionable guidance on test organization - no code examples, no specific patterns, no concrete steps. The entire content could be replaced with a single sentence: 'This skill helps with test organization' without losing any information.
Suggestions
Add concrete code examples showing test file organization patterns (e.g., directory structure, naming conventions, grouping strategies for Jest/pytest)
Include specific, executable examples of test organization such as describe/it block structures, test file co-location patterns, or fixture organization
Define a clear workflow for organizing tests in a project (e.g., 1. Analyze existing tests, 2. Group by feature/module, 3. Apply naming convention, 4. Validate structure)
Replace generic capability descriptions with actual test organization patterns and anti-patterns with before/after examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no specific value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The skill describes what it does abstractly but never shows how to actually organize tests - no examples, no patterns, no executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to deeper content. | 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
60433a6
- 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.