tester

Quality assurance expert - writes comprehensive tests

Quality

28%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/tester/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides good actionable code examples with the AAA pattern and mocking best practices, but suffers from verbosity by explaining testing concepts Claude already knows (test types, philosophy). The content would benefit from splitting into overview + reference files and adding explicit validation/iteration workflows for test failures.

Suggestions

Remove or drastically reduce the 'Testing Philosophy' and 'Test Types' sections - Claude already understands these concepts

Split framework-specific details and mocking patterns into separate reference files (e.g., FRAMEWORKS.md, MOCKING.md) with clear links from the main skill

Add explicit feedback loop for test failures: what to check, how to debug, when to refactor tests vs code

Remove the closing quote and persona framing ('The Quality Guardian') which add no actionable value

Dimension	Reasoning	Score
Conciseness	Contains some unnecessary padding like the philosophy section and the closing quote. The framework lists and test type explanations describe concepts Claude already knows, but the code examples are valuable and reasonably efficient.	2 / 3
Actionability	Provides fully executable TypeScript code examples with the AAA pattern, complete mock setup, and specific assertion patterns. The test naming convention and mocking examples are copy-paste ready.	3 / 3
Workflow Clarity	The testing checklist provides a clear sequence, but lacks explicit validation checkpoints or feedback loops for when tests fail. No guidance on what to do when coverage goals aren't met or how to iterate on failing tests.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. Content like framework-specific details, test type explanations, and mocking patterns could be split into separate reference files for better organization.	1 / 3
	Total	8 / 12 Passed

Description

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 underdeveloped, providing only a vague role label without concrete capabilities, trigger terms, or usage guidance. It fails all dimensions by being too abstract to help Claude distinguish this skill from others or know when to apply it.

Suggestions

Add specific concrete actions: 'Writes unit tests, integration tests, and end-to-end tests. Creates test fixtures, mocks dependencies, and generates test data.'

Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks for tests, test coverage, TDD, unit tests, pytest, jest, or wants to verify code behavior.'

Specify the testing scope or languages supported to create distinctiveness: 'For Python projects using pytest and unittest frameworks' or 'For JavaScript/TypeScript with Jest and Vitest.'

Dimension	Reasoning	Score
Specificity	The description uses vague language ('comprehensive tests') without specifying concrete actions like 'write unit tests', 'create integration tests', 'generate test fixtures', or 'mock dependencies'.	1 / 3
Completeness	Only vaguely addresses 'what' (writes tests) and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains only generic terms ('quality assurance', 'tests') and misses natural user keywords like 'unit test', 'pytest', 'jest', 'test coverage', 'TDD', 'mock', or specific testing frameworks.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'writes comprehensive tests' could conflict with any coding skill, debugging skill, or code review skill. No clear niche or distinguishing characteristics.	1 / 3
	Total	4 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.