CtrlK
BlogDocsLog inGet started
Tessl Logo

testing-patterns

Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/testing-patterns/SKILL.md

The canonical home for this skill is testing-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%Scale 1-5

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

This is a solid pattern catalog for Jest/React Native testing with good executable examples and useful anti-patterns. Its main weaknesses are verbosity in the philosophy section (explaining concepts Claude already knows), lack of a concrete TDD walkthrough demonstrating the red-green-refactor cycle, and a monolithic structure that could benefit from splitting into overview + reference files. The factory and mocking examples are the strongest parts.

Suggestions

Remove or drastically shorten the 'Testing Philosophy' section—Claude already understands TDD, BDD, and DRY principles. Keep only project-specific conventions.

Add a concrete TDD walkthrough showing the full red-green-refactor cycle with a small example (write failing test → show it fails → implement → show it passes → refactor).

Split detailed patterns (mocking, factories, query patterns) into a separate PATTERNS.md reference file and keep SKILL.md as a concise overview with links.

Remove the 'Best Practices' bullet list at the end since it repeats guidance already demonstrated in the examples above.

DimensionReasoningScore

Conciseness

The skill contains some unnecessary philosophical preamble (Testing Philosophy section explains TDD and behavior-driven testing concepts Claude already knows well). The code examples themselves are efficient, but the 'Best Practices' section at the end largely repeats guidance already given earlier. The anti-patterns section adds value but could be tighter.

3 / 5

Actionability

The skill provides concrete, executable TypeScript code examples for factories, mocking, rendering utilities, queries, and user interactions. Minor gaps exist—for example, the test structure section uses empty function bodies rather than complete examples, and some patterns lack import statements—but overall the guidance is copy-paste ready.

4 / 5

Workflow Clarity

The TDD workflow (red-green-refactor) is mentioned but not demonstrated with a concrete step-by-step example showing the cycle in action. The skill is more of a pattern catalog than a sequenced workflow. For a non-destructive skill this is acceptable, but the TDD cycle description would benefit from an explicit worked example with validation checkpoints (e.g., confirming the test fails before writing code).

3 / 5

Progressive Disclosure

The content is reasonably structured with clear section headers, but at ~200 lines it could benefit from splitting detailed patterns (mocking, factories, query patterns) into separate reference files. The 'Integration with Other Skills' section references other skills but doesn't link to them. No bundle files exist to offload detail, so everything is inlined in one file.

3 / 5

Total

13

/

20

Passed

Description

83%Scale 1-5

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 a solid skill description that clearly communicates both purpose and trigger conditions. It names the specific testing framework (Jest) and methodology (TDD) which aids selection. Minor improvements could include more concrete action verbs and additional trigger term synonyms.

DimensionReasoningScore

Specificity

Lists several specific concepts (Jest testing patterns, factory functions, mocking strategies, TDD workflow) but doesn't elaborate on concrete actions like 'create mock implementations' or 'generate test boilerplate'.

4 / 5

Completeness

Clearly answers both 'what' (Jest testing patterns, factory functions, mocking strategies, TDD workflow) and 'when' (writing unit tests, creating test factories, following TDD red-green-refactor cycle) with explicit trigger phrases.

5 / 5

Trigger Term Quality

Includes good natural keywords like 'unit tests', 'test factories', 'TDD', 'red-green-refactor', 'mocking', and 'Jest'. Missing some variations like '.test.js', 'spec files', 'test doubles', or 'assertions'.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct with Jest-specific focus and TDD workflow, though could overlap with general testing skills or JavaScript development skills. The mention of factory functions and mocking strategies helps narrow the niche.

4 / 5

Total

17

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.