test-case-documentation
Writes documentation for test cases — names, docstrings, and comments that explain what behavior is being tested and why, so a failing test tells you what broke without reading the assertion. Use when test names are test_1 through test_47, when tests fail and nobody knows what they mean, or when onboarding needs a readable test suite.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill test-case-documentation100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%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 is an excellent skill description that clearly articulates what the skill does (writes test documentation including names, docstrings, and comments), why it matters (so failing tests are self-explanatory), and when to use it (with vivid, relatable trigger scenarios). The description uses proper third-person voice and includes natural language triggers that users would actually say when facing poorly documented tests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'names, docstrings, and comments that explain what behavior is being tested and why' - clearly describes the deliverables and their purpose. | 3 / 3 |
Completeness | Clearly answers both what ('Writes documentation for test cases — names, docstrings, and comments') and when ('Use when test names are test_1 through test_47, when tests fail and nobody knows what they mean, or when onboarding needs a readable test suite'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'test names', 'test_1 through test_47', 'tests fail', 'readable test suite', 'onboarding', 'docstrings', 'comments' - covers both problem descriptions and technical terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche focused on test documentation specifically, with distinct triggers like 'test_1 through test_47' and 'failing test tells you what broke' - unlikely to conflict with general documentation or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates mastery of the format. It's concise yet comprehensive, with concrete examples at every turn. The before/after worked example is particularly effective, and the 'Do not' section prevents common mistakes without being preachy. The output format provides clear structure for Claude's deliverables.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with concrete examples and actionable patterns. No explanation of what tests are or how testing frameworks work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides concrete before/after code examples, specific naming patterns, clear tables showing bad vs good names, and executable Python code. The worked example is copy-paste ready and demonstrates the exact transformation expected. | 3 / 3 |
Workflow Clarity | Clear decision tree: try renaming first, then add docstring only if needed. The 'when a docstring earns its place' table provides explicit criteria. The output format gives a structured checklist for the review process. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from naming → docstrings → inline comments → anti-patterns → output format. Content is appropriately sized for a single file with no need for external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.