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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill test-organization-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 fails to explain what the skill does, provides no natural trigger terms users would actually say, and offers no guidance on when to use it. The repeated trigger term and boilerplate category mention provide zero value for skill selection.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Organizes test files into logical directories, groups related test cases, creates test suites from scattered tests').
Include a 'Use when...' clause with natural trigger terms like 'organize tests', 'group test cases', 'restructure test files', 'test suite organization'.
Specify the types of tests or frameworks supported to distinguish from other testing skills (e.g., 'for Jest, pytest, or JUnit test files').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Test Organization Helper' and category 'Test Automation' with no explanation of what it actually does. | 1 / 3 |
Completeness | Missing both 'what' and 'when' - there's no explanation of what the skill does or when Claude should use it beyond the unhelpful auto-generated trigger phrase. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('test organization helper, test organization helper'), which is redundant and not natural language users would say when needing help organizing tests. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Test Automation' could overlap with many testing-related skills, and there's nothing distinguishing this from other test organization or automation tools. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes capabilities in abstract terms without providing any actual guidance, code examples, or concrete instructions for test organization. The content would be completely unhelpful for Claude attempting to assist with test organization tasks.
Suggestions
Add concrete code examples showing test file structure, naming conventions, and organization patterns (e.g., grouping by feature vs. by type)
Include specific guidance for test frameworks mentioned in tags (Jest, pytest) with executable configuration snippets
Define a clear workflow for organizing existing tests or setting up new test suites with validation steps
Replace abstract capability descriptions with actionable instructions like directory structures, describe/it block patterns, or fixture organization
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The entire skill describes what it does abstractly without any executable examples or actual instructions for test organization. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps or processes for organizing tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no references to detailed materials, no links to examples, and no structured navigation to actual implementation details. | 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.