auto-write-test-rules
Use when adding or proposing a new test ONLY if the test rules are not present
44
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%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 severely incomplete - it only specifies a conditional trigger without explaining what the skill actually does. The phrase 'test rules' is undefined and confusing, and there's no indication of what actions or outputs the skill provides. Users and Claude cannot make informed decisions about when to use this skill.
Suggestions
Add a clear 'what' statement explaining the skill's concrete actions (e.g., 'Generates test files following project conventions' or 'Creates unit tests with proper structure and assertions').
Define what 'test rules' means - is this referring to testing conventions, a specific file, or project guidelines?
Include natural trigger terms users would say, such as 'unit test', 'test case', 'spec', 'write tests', or specific framework names like 'jest', 'pytest', 'rspec'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('adding or proposing a new test') without specifying concrete actions like what kind of tests, what format, or what the skill actually does beyond checking for 'test rules'. | 1 / 3 |
Completeness | The description only provides a 'when' clause but completely fails to explain 'what' the skill actually does. It's unclear what actions the skill performs or what 'test rules' means. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('test', 'new test') that users might say, but lacks common variations like 'unit test', 'integration test', 'spec', 'test case', or specific testing frameworks. | 2 / 3 |
Distinctiveness Conflict Risk | The conditional 'ONLY if the test rules are not present' provides some specificity, but 'adding a new test' is generic enough to potentially conflict with other testing-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a redirect with no substantive content. While it's concise, it fails to provide any actionable guidance on how to add or propose tests. The entire skill body is a single line pointing to another file without explaining what that file contains or how to apply it.
Suggestions
Add a brief summary of the key test rules or at minimum describe what guidance the referenced file provides
Include at least one concrete example of how to add or propose a test following the rules
Define the basic workflow steps: when to add tests, how to structure them, and how to validate they follow the rules
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely brief at one line, assumes Claude knows what testing rules are and how to use them. No unnecessary explanation. | 3 / 3 |
Actionability | Provides no concrete guidance on what to do - just references another file without explaining how to add/propose tests, what format to use, or any executable steps. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill doesn't explain the process for adding or proposing tests, just points to another file without context. | 1 / 3 |
Progressive Disclosure | References an external file which is appropriate, but the reference is the entire content with no overview or context about what the referenced file contains or how to use it. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.