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
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 repeats the skill name as its only trigger term, provides zero concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be indistinguishable from any other test-related skill in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Reorganizes test files into logical directories, splits large test files by feature, groups related test cases, and generates test index files.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to organize tests, restructure test directories, group test cases, split test files, or improve test file structure.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users would actually say, such as 'organize tests', 'test structure', 'test file layout', 'group tests', 'test directory'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Test Organization Helper' is a name, not a description of capabilities. There are no specific actions like 'reorganizes test files', 'groups tests by feature', or 'creates test directories'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states the skill name, a redundant trigger, and a category label. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('test organization helper'). No natural user language is included—users would more likely say things like 'organize my tests', 'restructure test files', 'group test cases', or 'test folder structure'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Test Automation' and 'test organization' could overlap with any number of testing-related skills. Without specific capabilities or file types, it would be nearly impossible to distinguish this from other test-related 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 placeholder that provides no actual instruction on test organization. It repeatedly names the skill without ever defining what test organization means, how to do it, or providing any concrete code, commands, or patterns. It fails on every dimension of the rubric.
Suggestions
Replace the abstract descriptions with concrete, executable examples of test organization patterns (e.g., directory structures, naming conventions, pytest/jest configuration snippets).
Add a clear workflow for organizing tests in a project, such as: 1) Assess current test structure, 2) Group tests by type (unit/integration/e2e), 3) Apply naming conventions, 4) Validate with a test runner.
Include specific code examples for at least one framework (e.g., pytest fixtures organization, jest describe/it nesting patterns) that are copy-paste ready.
Remove all meta-description content ('This skill provides automated assistance...') and replace with actionable technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It repeatedly restates the skill name without providing any actual technical content. Every section describes what the skill could do rather than doing it. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns, no examples of test organization. The content is entirely abstract and descriptive, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered content, and the sections are superficial headers over vacuous 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
c8a915c
- 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.