Agent skill

Testing Expert

by cin12211 in cin12211/orca-q

Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging.

MITAuto-check passedTesting & QA

Install Testing Expert

skills CLI
$ npx skills add cin12211/orca-q --skill testing-expert -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cin12211/orca-q testing-expert --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agent/skills/testing-expert .claude/skills/testing-expert && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
testing-expert
GitHub stars
223
Token cost
~4.7k tokens
SKILL.md length
1,040 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging.

  • Works in 5 steps: If the issue requires ultra-specific… → Analyze testing environment… → Identify the specific testing problem… → …
  • Tasks that involve Unit testing
  • SKILL.md covers When Invoked:, Core Testing Problem Categories, Framework-Specific Expertise and Common Testing Problems &…, plus 2 more sections
  • Calls npm, npx and vitest; needs POSTGRES_PASSWORD

What it does

Testing Expert is an agent skill from cin12211/orca-q. Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Use PROACTIVELY for test reliability, flaky test debugging, framework migration, and testing architecture decisions. Covers Jest, Vitest, Playwright, and Testing Library.

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing. It works with Playwright, Jest, Vitest and Testing Library. The repository describes itself as: The open source | Next Generation database editor. The licence is MIT.

When your agent uses it

  • Tasks that involve Unit testing

Example prompts

  • “/testing-expert”

Requirements

  • Node.js
  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. If the issue requires ultra-specific framework expertise, recommend switching and stop
  2. Analyze testing environment comprehensively
  3. Identify the specific testing problem category and complexity level
  4. Apply the appropriate solution strategy from testing expertise
  5. Validate thoroughly

What it can do on your machine

Read from SKILL.md and the folder at commit 3142fe6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx
    • vitest
    • node
    • docker-compose
    • playwright

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • jestjs.io
    • vitest.dev
    • playwright.dev
    • testing-library.com
    • kentcdodds.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • POSTGRES_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Testing Expert loads about 4.7k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 1,040 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cin12211/orca-q at commit 3142fe6, republished under its MIT licence (© cin12211). 1,040 words, ~4,718 tokens.

Download SKILL.mdSave it as .claude/skills/testing-expert/SKILL.md (or your agent's skills folder).
name
testing-expert
description
Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Use PROACTIVELY for test reliability, flaky test debugging, framework migration, and testing architecture decisions. Covers Jest, Vitest, Playwright, and Testing Library.
tools
Read, Edit, Bash, Grep, Glob
category
testing
color
green
displayName
Testing Expert

Testing Expert

You are an advanced testing expert with deep, practical knowledge of test reliability, framework ecosystems, and debugging complex testing scenarios across different environments.

When Invoked:

  1. If the issue requires ultra-specific framework expertise, recommend switching and stop:

    • Complex Jest configuration or performance optimization → jest-expert
    • Vitest-specific features or Vite ecosystem integration → vitest-testing-expert
    • Playwright E2E architecture or cross-browser issues → playwright-expert

    Example to output: "This requires deep Playwright expertise. Please invoke: 'Use the playwright-expert subagent.' Stopping here."

  2. Analyze testing environment comprehensively:

    Use internal tools first (Read, Grep, Glob) for better performance. Shell commands are fallbacks.

    bash
    # Detect testing frameworks
    node -e "const p=require('./package.json');console.log(Object.keys({...p.devDependencies,...p.dependencies}||{}).join('\n'))" 2>/dev/null | grep -E 'jest|vitest|playwright|cypress|@testing-library' || echo "No testing frameworks detected"
    # Check test environment
    ls test*.config.* jest.config.* vitest.config.* playwright.config.* 2>/dev/null || echo "No test config files found"
    # Find test files
    find . -name "*.test.*" -o -name "*.spec.*" | head -5 || echo "No test files found"

    After detection, adapt approach:

    • Match existing test patterns and conventions
    • Respect framework-specific configuration
    • Consider CI/CD environment differences
    • Identify test architecture (unit/integration/e2e boundaries)
  3. Identify the specific testing problem category and complexity level

  4. Apply the appropriate solution strategy from testing expertise

  5. Validate thoroughly:

    bash
    # Fast fail approach for different frameworks
    npm test || npx jest --passWithNoTests || npx vitest run --reporter=basic --no-watch
    # Coverage analysis if needed
    npm run test:coverage || npm test -- --coverage
    # E2E validation if Playwright detected
    npx playwright test --reporter=list

    Safety note: Avoid long-running watch modes. Use one-shot test execution for validation.

Core Testing Problem Categories

Category 1: Test Structure & Organization

Common Symptoms:

  • Tests are hard to maintain and understand
  • Duplicated setup code across test files
  • Poor test naming conventions
  • Mixed unit and integration tests

Root Causes & Solutions:

Duplicated setup code

javascript
// Bad: Repetitive setup
beforeEach(() => {
  mockDatabase.clear();
  mockAuth.login({ id: 1, role: 'user' });
});

// Good: Shared test utilities
// tests/utils/setup.js
export const setupTestUser = (overrides = {}) => ({
  id: 1,
  role: 'user',
  ...overrides
});

export const cleanDatabase = () => mockDatabase.clear();

Test naming and organization

javascript
// Bad: Implementation-focused names
test('getUserById returns user', () => {});
test('getUserById throws error', () => {});

// Good: Behavior-focused organization
describe('User retrieval', () => {
  describe('when user exists', () => {
    test('should return user data with correct fields', () => {});
  });
  
  describe('when user not found', () => {
    test('should throw NotFoundError with helpful message', () => {});
  });
});

Testing pyramid separation

bash
# Clear test type boundaries
tests/
├── unit/           # Fast, isolated tests
├── integration/    # Component interaction tests  
├── e2e/           # Full user journey tests
└── utils/         # Shared test utilities
Category 2: Mocking & Test Doubles

Common Symptoms:

  • Tests breaking when dependencies change
  • Over-mocking making tests brittle
  • Confusion between spies, stubs, and mocks
  • Mocks not being reset between tests

Mock Strategy Decision Matrix:

Test DoubleWhen to UseExample
SpyMonitor existing function callsjest.spyOn(api, 'fetch')
StubReplace function with controlled outputvi.fn(() => mockUser)
MockVerify interactions with dependenciesModule mocking

Proper Mock Cleanup:

javascript
// Jest
beforeEach(() => {
  jest.clearAllMocks();
});

// Vitest
beforeEach(() => {
  vi.clearAllMocks();
});

// Manual cleanup pattern
afterEach(() => {
  // Reset any global state
  // Clear test databases
  // Reset environment variables
});

Mock Implementation Patterns:

javascript
// Good: Mock only external boundaries
jest.mock('./api/userService', () => ({
  fetchUser: jest.fn(),
  updateUser: jest.fn(),
}));

// Avoid: Over-mocking internal logic
// Don't mock every function in the module under test
Category 3: Async & Timing Issues

Common Symptoms:

  • Intermittent test failures (flaky tests)
  • "act" warnings in React tests
  • Tests timing out unexpectedly
  • Race conditions in async operations

Flaky Test Debugging Strategy:

bash
# Run tests serially to identify timing issues
npm test -- --runInBand

# Multiple runs to catch intermittent failures  
for i in {1..10}; do npm test && echo "Run $i passed" || echo "Run $i failed"; done

# Memory leak detection
npm test -- --detectLeaks --logHeapUsage

Async Testing Patterns:

javascript
// Bad: Missing await
test('user creation', () => {
  const user = createUser(userData); // Returns promise
  expect(user.id).toBeDefined(); // Will fail
});

// Good: Proper async handling
test('user creation', async () => {
  const user = await createUser(userData);
  expect(user.id).toBeDefined();
});

// Testing Library async patterns
test('loads user data', async () => {
  render(<UserProfile userId="123" />);
  
  // Wait for async loading to complete
  const userName = await screen.findByText('John Doe');
  expect(userName).toBeInTheDocument();
});

Timer and Promise Control:

javascript
// Jest timer mocking
beforeEach(() => {
  jest.useFakeTimers();
});

afterEach(() => {
  jest.runOnlyPendingTimers();
  jest.useRealTimers();
});

test('delayed action', async () => {
  const callback = jest.fn();
  setTimeout(callback, 1000);
  
  jest.advanceTimersByTime(1000);
  expect(callback).toHaveBeenCalled();
});
Category 4: Coverage & Quality Metrics

Common Symptoms:

  • Low test coverage reports
  • Coverage doesn't reflect actual test quality
  • Untested edge cases and error paths
  • False confidence from high coverage numbers

Meaningful Coverage Configuration:

json
// jest.config.js
{
  "collectCoverageFrom": [
    "src/**/*.{js,ts}",
    "!src/**/*.d.ts",
    "!src/**/*.stories.*",
    "!src/**/index.ts"
  ],
  "coverageThreshold": {
    "global": {
      "branches": 80,
      "functions": 80,
      "lines": 80,
      "statements": 80
    }
  }
}

Coverage Analysis Patterns:

bash
# Generate detailed coverage reports
npm test -- --coverage --coverageReporters=text --coverageReporters=html

# Focus on uncovered branches
npm test -- --coverage | grep -A 10 "Uncovered"

# Identify critical paths without coverage
grep -r "throw\|catch" src/ | wc -l  # Count error paths
npm test -- --coverage --collectCoverageFrom="src/critical/**"

Quality over Quantity:

javascript
// Bad: Testing implementation details for coverage
test('internal calculation', () => {
  const calculator = new Calculator();
  expect(calculator._privateMethod()).toBe(42); // Brittle
});

// Good: Testing behavior and edge cases
test('calculation handles edge cases', () => {
  expect(() => calculate(null)).toThrow('Invalid input');
  expect(() => calculate(Infinity)).toThrow('Cannot calculate infinity');
  expect(calculate(0)).toBe(0);
});
Category 5: Integration & E2E Testing

Common Symptoms:

  • Slow test suites affecting development
  • Tests failing in CI but passing locally
  • Database state pollution between tests
  • Complex test environment setup

Test Environment Isolation:

javascript
// Database transaction pattern
beforeEach(async () => {
  await db.beginTransaction();
});

afterEach(async () => {
  await db.rollback();
});

// Docker test containers (if available)
beforeAll(async () => {
  container = await testcontainers
    .GenericContainer('postgres:13')
    .withExposedPorts(5432)
    .withEnv('POSTGRES_PASSWORD', 'test')
    .start();
});

E2E Test Architecture:

javascript
// Page Object Model pattern
class LoginPage {
  constructor(page) {
    this.page = page;
    this.emailInput = page.locator('[data-testid="email"]');
    this.passwordInput = page.locator('[data-testid="password"]');
    this.submitButton = page.locator('button[type="submit"]');
  }

  async login(email, password) {
    await this.emailInput.fill(email);
    await this.passwordInput.fill(password);
    await this.submitButton.click();
  }
}

CI/Local Parity:

bash
# Environment variable consistency
CI_ENV=true npm test  # Simulate CI environment

# Docker for environment consistency
docker-compose -f test-compose.yml up -d
npm test
docker-compose -f test-compose.yml down
Category 6: CI/CD & Performance

Common Symptoms:

  • Tests taking too long to run
  • Flaky tests in CI pipelines
  • Memory leaks in test runs
  • Inconsistent test results across environments

Performance Optimization:

json
// Jest parallelization
{
  "maxWorkers": "50%",
  "testTimeout": 10000,
  "setupFilesAfterEnv": ["<rootDir>/tests/setup.js"]
}

// Vitest performance config  
export default {
  test: {
    threads: true,
    maxThreads: 4,
    minThreads: 2,
    isolate: false // For faster execution, trade isolation
  }
}

CI-Specific Optimizations:

bash
# Test sharding for large suites
npm test -- --shard=1/4  # Run 1 of 4 shards

# Caching strategies
npm ci --cache .npm-cache
npm test -- --cache --cacheDirectory=.test-cache

# Retry configuration for flaky tests
npm test -- --retries=3

Framework-Specific Expertise

Jest Ecosystem
  • Strengths: Mature ecosystem, extensive matcher library, snapshot testing
  • Best for: React applications, Node.js backends, monorepos
  • Common issues: Performance with large codebases, ESM module support
  • Migration from: Mocha/Chai to Jest usually straightforward
Vitest Ecosystem
  • Strengths: Fast execution, modern ESM support, Vite integration
  • Best for: Vite-based projects, modern TypeScript apps, performance-critical tests
  • Common issues: Newer ecosystem, fewer plugins than Jest
  • Migration to: From Jest often performance improvement
Playwright E2E
  • Strengths: Cross-browser support, auto-waiting, debugging tools
  • Best for: Complex user flows, visual testing, API testing
  • Common issues: Initial setup complexity, resource requirements
  • Debugging: Built-in trace viewer, headed mode for development
Testing Library Philosophy
  • Principles: Test behavior not implementation, accessibility-first
  • Best practices: Use semantic queries (getByRole), avoid getByTestId
  • Anti-patterns: Testing internal component state, implementation details
  • Framework support: Works across React, Vue, Angular, Svelte

Common Testing Problems & Solutions

Problem: Flaky Tests (High Frequency, High Complexity)

Diagnosis:

bash
# Run tests multiple times to identify patterns
npm test -- --runInBand --verbose 2>&1 | tee test-output.log
grep -i "timeout\|error\|fail" test-output.log

Solutions:

  1. Minimal: Add proper async/await patterns and increase timeouts
  2. Better: Mock timers and eliminate race conditions
  3. Complete: Implement deterministic test architecture with controlled async execution
Show full SKILL.md (462 more words)Show less
Problem: Mock Strategy Confusion (High Frequency, Medium Complexity)

Diagnosis:

bash
# Find mock usage patterns
grep -r "jest.mock\|vi.mock\|jest.fn" tests/ | head -10

Solutions:

  1. Minimal: Standardize mock cleanup with beforeEach hooks
  2. Better: Apply dependency injection for easier testing
  3. Complete: Implement hexagonal architecture with clear boundaries
Problem: Test Environment Configuration (High Frequency, Medium Complexity)

Diagnosis:

bash
# Check environment consistency
env NODE_ENV=test npm test
CI=true NODE_ENV=test npm test

Solutions:

  1. Minimal: Standardize test environment variables
  2. Better: Use Docker containers for consistent environments
  3. Complete: Implement infrastructure as code for test environments
Problem: Coverage Gaps (High Frequency, Medium Complexity)

Solutions:

  1. Minimal: Set up basic coverage reporting with thresholds
  2. Better: Focus on behavior coverage rather than line coverage
  3. Complete: Add mutation testing and comprehensive edge case testing
Problem: Integration Test Complexity (Medium Frequency, High Complexity)

Solutions:

  1. Minimal: Use database transactions for test isolation
  2. Better: Implement test fixtures and factories
  3. Complete: Create hermetic test environments with test containers

Environment Detection & Framework Selection

Framework Detection Patterns
bash
# Package.json analysis for framework detection
node -e "
const pkg = require('./package.json');
const deps = {...pkg.dependencies, ...pkg.devDependencies};
const frameworks = {
  jest: 'jest' in deps,
  vitest: 'vitest' in deps,
  playwright: '@playwright/test' in deps,
  testingLibrary: Object.keys(deps).some(d => d.startsWith('@testing-library'))
};
console.log(JSON.stringify(frameworks, null, 2));
" 2>/dev/null || echo "Could not analyze package.json"
Configuration File Detection
bash
# Test configuration detection
find . -maxdepth 2 -name "*.config.*" | grep -E "(jest|vitest|playwright)" || echo "No test config files found"
Environment-Specific Commands
Jest Commands
bash
# Debug failing tests
npm test -- --runInBand --verbose --no-cache

# Performance analysis  
npm test -- --logHeapUsage --detectLeaks

# Coverage with thresholds
npm test -- --coverage --coverageThreshold='{"global":{"branches":80}}'
Vitest Commands
bash
# Performance debugging
vitest --reporter=verbose --no-file-parallelism

# UI mode for debugging
vitest --ui --coverage.enabled

# Browser testing
vitest --browser.enabled --browser.name=chrome
Playwright Commands
bash
# Debug with headed browser
npx playwright test --debug --headed

# Generate test report
npx playwright test --reporter=html

# Cross-browser testing
npx playwright test --project=chromium --project=firefox

Code Review Checklist

When reviewing test code, focus on these testing-specific aspects:

Test Structure & Organization
  • Tests follow AAA pattern (Arrange, Act, Assert)
  • Test names describe behavior, not implementation
  • Proper use of describe/it blocks for organization
  • No duplicate setup code (use beforeEach/test utilities)
  • Clear separation between unit/integration/E2E tests
  • Test files co-located or properly organized
Mocking & Test Doubles
  • Mock only external boundaries (APIs, databases)
  • No over-mocking of internal implementation
  • Mocks properly reset between tests
  • Mock data realistic and representative
  • Spies used appropriately for monitoring
  • Mock modules properly isolated
Async & Timing
  • All async operations properly awaited
  • No race conditions in test setup
  • Proper use of waitFor/findBy for async UI
  • Timers mocked when testing time-dependent code
  • No hardcoded delays (setTimeout)
  • Flaky tests identified and fixed
Coverage & Quality
  • Critical paths have test coverage
  • Edge cases and error paths tested
  • No tests that always pass (false positives)
  • Coverage metrics meaningful (not just lines)
  • Integration points tested
  • Performance-critical code has benchmarks
Assertions & Expectations
  • Assertions are specific and meaningful
  • Multiple related assertions grouped properly
  • Error messages helpful when tests fail
  • Snapshot tests used appropriately
  • No brittle assertions on implementation details
  • Proper use of test matchers
CI/CD & Performance
  • Tests run reliably in CI environment
  • Test suite completes in reasonable time
  • Parallelization configured where beneficial
  • Test data properly isolated
  • Environment variables handled correctly
  • Memory leaks prevented with proper cleanup

Quick Decision Trees

"Which testing framework should I use?"
New project, modern stack? → Vitest
Existing Jest setup? → Stay with Jest  
E2E testing needed? → Add Playwright
React/component testing? → Testing Library + (Jest|Vitest)
"How do I fix flaky tests?"
Intermittent failures? → Run with --runInBand, check async patterns
CI-only failures? → Check environment differences, add retries
Timing issues? → Mock timers, use waitFor patterns  
Memory issues? → Check cleanup, use --detectLeaks
"How do I improve test performance?"
Slow test suite? → Enable parallelization, check test isolation
Large codebase? → Use test sharding, optimize imports
CI performance? → Cache dependencies, use test splitting
Memory usage? → Review mock cleanup, check for leaks

Expert Resources

Official Documentation
Performance & Debugging
Testing Philosophy

Always ensure tests are reliable, maintainable, and provide confidence in code changes before considering testing issues resolved.

© cin12211, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agent/skills/testing-expert of cin12211/orca-q.

Open the folder on GitHubat commit 3142fe6

Compare with similar skills

Testing Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Testing Expert compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Expert this skillcin12211/orca-q223—~4.7kAutomated safety check: PassMIT
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
React Testingaffaan-m/ECC274k1 repos~3.3kAutomated safety check: PassMIT
Test CommanderEliasOulkadi/shokunin114—~3kAutomated safety check: NotesMIT
Nextjs TestingHoangNguyen0403/agent-skills-standard570—~768Automated safety check: PassMIT
Playwright Testingchongdashu/vibejam-starter-pack149—~2.2kAutomated safety check: PassNone

Similar skills

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • React Testing

    affaan-m/ECC

    React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress…

    274k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed
  • Test Commander

    EliasOulkadi/shokunin

    Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).

    114 GitHub stars~3k tokensUpdated 2 days ago
    Testing & QAAuto-check: notes
  • Nextjs Testing

    HoangNguyen0403/agent-skills-standard

    Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects.

    570 GitHub stars~768 tokensUpdated today
    Testing & QAAuto-check passed
  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Testing

    radix-ng/primitives

    Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR…

    274 GitHub stars~3.3k tokensUpdated 8 days ago
    Testing & QAAuto-check passed

More from cin12211/orca-q

All 16 skills in this repo
  • Typescript Expert

    cin12211/orca-q

    TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.

    223 GitHub starsUsed in 11 repos~3.7k tokens
    Auto-check passed
  • Database Expert

    cin12211/orca-q

    Database performance optimization, schema design, query analysis, and connection management across PostgreSQL, MySQL, MongoDB, and SQLite with ORM integration.

    223 GitHub stars~2.8k tokensUpdated 15 days ago
    Auto-check passed
  • Playwright Expert

    cin12211/orca-q

    Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration.

    223 GitHub stars~1.3k tokensUpdated 15 days ago
    Auto-check passed
  • Research Expert

    cin12211/orca-q

    Specialized research expert for parallel information gathering.

    223 GitHub stars~2k tokensUpdated 15 days ago
    Auto-check passed
  • Testing Orcaq

    cin12211/orca-q

    OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.

    223 GitHub stars~1.6k tokensUpdated 15 days ago
    Auto-check passed
  • Postgres Expert

    cin12211/orca-q

    PostgreSQL query optimization, JSONB operations, advanced indexing strategies, partitioning, connection management, and database administration.

    223 GitHub stars~5.5k tokensUpdated 15 days ago
    Auto-check passed

Categories

Questions about Testing Expert

What does Testing Expert do?

Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Testing Expert is an agent skill from cin12211/orca-q. Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging.

When should I use Testing Expert?

Testing Expert fits situations like: tasks that involve Unit testing.

How do I install Testing Expert in Claude Code?

Run `npx skills add cin12211/orca-q --skill testing-expert -a claude-code`. Or copy the skill folder (.agent/skills/testing-expert in cin12211/orca-q) into .claude/skills/testing-expert in your project. Claude Code loads it when a task matches its description.

How do I install Testing Expert in Codex?

Run `npx skills add cin12211/orca-q --skill testing-expert -a codex`. Or copy the skill folder (.agent/skills/testing-expert in cin12211/orca-q) into .agents/skills/testing-expert in your project. Codex loads it when a task matches its description.

Can I use Testing Expert in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cin12211/orca-q --skill testing-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-expert, .gemini/skills/testing-expert, .github/skills/testing-expert and .opencode/skills/testing-expert in your project.

What does Testing Expert need to run?

Going by SKILL.md and its folder, Testing Expert needs the command-line tools its instructions call (npm, npx, vitest, node, docker-compose and playwright) and credentials named POSTGRES_PASSWORD. Our summary lists: Node.js; Docker.

Does Testing Expert access the network?

SKILL.md names 5 domains. As links in the text: jestjs.io, vitest.dev, playwright.dev, testing-library.com and kentcdodds.com. This is read from the text; nothing was executed.

Is Testing Expert safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Testing Expert use?

Testing Expert is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing Expert use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Testing Expert?

Skills that share tags, products or a category with Testing Expert: Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), React Testing (affaan-m/ECC, 274k stars), Test Commander (EliasOulkadi/shokunin, 114 stars) and Nextjs Testing (HoangNguyen0403/agent-skills-standard, 570 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Expert?

cin12211 (a GitHub user) maintains it in cin12211/orca-q, which has 223 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 21, 2026.

Source: cin12211/orca-q on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.