agentsclimarketplace

Flaky test detector

Skill ComeOnOliver/skillshub/skills/jeremylongshore/claude-code-plugins-plus-skills/flaky-test-detector

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install
npx -y skills add ComeOnOliver/skillshub --skill flaky-test-detector

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Flaky Test Detector - Auto-activating skill for Test Automation. Triggers on: flaky test detector, flaky test detector Part of the Test Automation skill category.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.2 KB, 186 tokens by cl100k_base, as published. Nobody here has run it

Flaky Test Detector

Purpose

This skill provides automated assistance for flaky test detector tasks within the Test Automation domain.

When to Use

This skill activates automatically when you:

  • Mention "flaky test detector" in your request
  • Ask about flaky test detector patterns or best practices
  • Need help with test automation skills covering unit testing, integration testing, mocking, and test framework configuration.

Capabilities

  • Provides step-by-step guidance for flaky test detector
  • Follows industry best practices and patterns
  • Generates production-ready code and configurations
  • Validates outputs against common standards

Example Triggers

  • "Help me with flaky test detector"
  • "Set up flaky test detector"
  • "How do I implement flaky test detector?"

Related Skills

Part of the Test Automation skill category. Tags: testing, jest, pytest, mocking, tdd

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,132. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.