testing-anti-patterns

testing-anti-patterns is a skill in rohitg00/skillkit, last changed 6 Mar 2026. It is instructions only: no scripts, no named hosts and no pre-approved tools. Our pattern check flagged nothing at commit d2e5c34 on 27 Oct 2026.

Pattern check: nothing flagged · commit d2e5c34 · 27 Oct 2026

Install
From the author
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
Licence
Apache 2.0
Repo stars
1.6k
Publisher
rohitg00
Files
1 file
Checked
d2e5c34 (opens in a new tab) · 27 Oct 2026

Install

Each tab says whether it installs commit d2e5c34, the one we checked, or the latest version.

No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity, and Claude Code for Cline. Kiro needs the folder copied by hand.

Pinned to commit d2e5c34, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&
  git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rohitg00/skillkit.git "$tmp" &&
  git -C "$tmp" fetch -q --depth 1 origin d2e5c346f73325c326820efd3188dcf2b6eb704f &&
  git -C "$tmp" sparse-checkout set -- packages/core/src/methodology/packs/testing/anti-patterns &&
  git -C "$tmp" checkout -q d2e5c346f73325c326820efd3188dcf2b6eb704f &&
  mkdir -p .claude/skills &&
  mkdir .claude/skills/testing-anti-patterns &&
  cp -R "$tmp"/packages/core/src/methodology/packs/testing/anti-patterns/. .claude/skills/testing-anti-patterns/ &&
  rm -rf "$tmp"

If Claude Code was already running and this created the skills folder, run /reload-skills.

Claude Code docs (opens in a new tab)

What it can touch

From the files and frontmatter at commit d2e5c34. This is how much a skill can do, not whether it is risky.

What it can touch: Instructions only

It is instructions only: no scripts, no named hosts and no pre-approved tools.

Pattern check

Pattern check: nothing flagged · commit d2e5c34 · 27 Oct 2026

We checked every text file in this skill, at commit d2e5c34 on 27 Oct 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

  • Agent Skills specFails

    The open format from agentskills.io, held to what the strictest agents enforce, so one folder loads everywhere.

    • Error

      The name "testing-anti-patterns" doesn't match its folder "anti-patterns". The spec requires them to match. N4

      Fix: Set name: anti-patterns, or rename the folder to testing-anti-patterns.

    • Warning

      Fields outside the spec: version, triggers, tags, difficulty, estimatedTime and relatedSkills. Uploads to the Claude apps and API, and the spec's validator, reject the file; most agents ignore these fields. O1

      Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.

    • Note

      There is no license field, so readers can't tell whether they may reuse the skill. O2

      Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.

  • Claude CodePasses

    Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

    • Note

      The name "testing-anti-patterns" doesn't match its folder "anti-patterns". Claude Code shows the skill as /testing-anti-patterns, and the folder name also invokes it. N4

      Fix: Set name: anti-patterns, or rename the folder to testing-anti-patterns.

    • Note

      Claude Code ignores fields it doesn't know: version, triggers, tags, difficulty, estimatedTime and relatedSkills. O1

      Fix: Check the spelling against Claude Code's field list, or delete them.

  • Claude apps & API uploadFails

    Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

    • Error

      The name "testing-anti-patterns" doesn't match its folder "anti-patterns". claude.ai refuses an upload whose folder name doesn't match the skill name. N4

      Fix: Set name: anti-patterns, or rename the folder to testing-anti-patterns.

    • Error

      Upload and packaging fail on fields outside the spec: version, triggers, tags, difficulty, estimatedTime and relatedSkills. O1

      Fix: Delete them, and keep your own data under metadata as text values.

    • Note

      The description is 486 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

      Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

  • OpenAI (Codex & API)Passes with warnings

    Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.

    • Warning

      The name "testing-anti-patterns" doesn't match its folder "anti-patterns". OpenAI's own upload example uses a differently named folder, but the spec it follows says they must match. N4

      Fix: Set name: anti-patterns, or rename the folder to testing-anti-patterns.

    • Warning

      Fields outside the spec: version, triggers, tags, difficulty, estimatedTime and relatedSkills. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1

      Fix: Delete them, or move your own data under metadata as text values.

  • VS Code & CopilotPasses with warnings

    VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.

    • Warning

      The name "testing-anti-patterns" doesn't match its folder "anti-patterns". VS Code uses the folder name, anti-patterns, instead. N4

      Fix: Set name: anti-patterns, or rename the folder to testing-anti-patterns.

    • Note

      VS Code ignores fields it doesn't support: version, triggers, tags, difficulty, estimatedTime and relatedSkills. O1

      Fix: Delete them unless another agent you target reads them.

SKILL.md

Files

More from rohitg00/skillkit

  • design-first

    rohitg00/skillkit

    Guides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off analyses. Use when the user asks to plan a feature, architect a system, design an API, explore implementation approaches, or requests a technical design or spec before coding — especially for complex features involving multiple components, ambiguous requirements, or significant architectural changes.

    • Instructions only
    Pattern check: Nothing flagged

    Apache 2.0 · 1.6k repo stars · Updated 6 Mar 2026

  • find-skills

    rohitg00/skillkit

    Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI. Supports browsing official partner collections (Anthropic, Vercel, Supabase, Stripe, and more) and community repositories, searching by domain or technology, and installing specific skills from GitHub. Use when the user wants to find, browse, or install new agent skills, plugins, extensions, or add-ons; asks 'is there a skill for X' or 'find a skill for X'; wants to explore a skill store or marketplace; needs to extend agent capabilities in areas like React, testing, DevOps, security, or APIs; or says 'browse skills', 'search skill marketplace', 'install a skill', or 'what skills are available'.

    • Runs shell commands
    • Names web addresses
    Pattern check: Nothing flagged

    Apache 2.0 · 1.6k repo stars · Updated 10 Mar 2026

  • handoff-protocols

    rohitg00/skillkit

    Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or agent; brief a colleague taking over; prepare a shift change summary; or onboard someone mid-task. Produces ready-to-use handoff documents covering current status, next steps, known issues, technical context, and communication templates for both planned and unplanned transfers.

    • Runs shell commands
    • Reaches the network
    Pattern check: Nothing flagged

    Apache 2.0 · 1.6k repo stars · Updated 6 Mar 2026

  • hypothesis-testing

    rohitg00/skillkit

    Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or they're trying to figure out what's causing an issue. Concrete actions include isolating failing components, forming and testing hypotheses, analyzing error messages, tracing execution paths, and interpreting test results to narrow down root causes.

    • Instructions only
    Pattern check: Nothing flagged

    Apache 2.0 · 1.6k repo stars · Updated 6 Mar 2026

  • parallel-investigation

    rohitg00/skillkit

    Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.

    • Instructions only
    Pattern check: Nothing flagged

    Apache 2.0 · 1.6k repo stars · Updated 6 Mar 2026

  • red-green-refactor

    rohitg00/skillkit

    Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.

    • Instructions only
    Pattern check: Nothing flagged

    Apache 2.0 · 1.6k repo stars · Updated 6 Mar 2026

All skills in rohitg00/skillkit