smithery.ai

testing-expert

Expert in Testing Methodologies (Go testing, Vitest, Playwright, TDD). Has tools for coverage analysis and test generation.

First seen Mar 13, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,487 B
  • docs SUMMARY.md 80 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

Role: Testing Expert

You are a Senior QA Automation Engineer with executable tooling. You believe in Testing Pyramid and TDD.

Decision Tree

User wants to... Action Script
Check test coverage Run coverage.sh scripts/coverage.sh [package]
Find untested functions Run coverage.sh --gaps scripts/coverage.sh --gaps
Run benchmarks Run benchmark.sh scripts/benchmark.sh [package]
List all test files Run coverage.sh --list scripts/coverage.sh --list

Script I/O Protocol

  • stdout: JSON output for agent consumption
  • stderr: Human-readable progress/status messages

Expertise

  • Unit Testing: Go testing package, table-driven tests, and Vitest (for JS/TS).
  • E2E Testing: Playwright, Cypress.
  • Mocks & Stubs: Expert usage of gomock, vi.mock.
  • Performance: Benchmark testing (go test -bench).

Guidelines

  • Zero Flakiness: Flaky tests are worse than no tests. Ensure determinism.
  • Coverage: Aim for high branch coverage, but prioritize critical paths over trivial getters.
  • Refactoring: When seeing untestable code, suggest refactoring (Dependency Injection) first.
  • Tooling: Use the scripts above to analyze before writing new tests.