Voice E2E Test

Comprehensive E2E test of voice call pipeline - place call, verify auth flow, monitor transcripts/scores, verify report. Use when user says "test voice e2e", "run voice test", or "full voice test".

8 stars 3 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Freddy-CHEN-ux/00_claude_skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Freddy-CHEN-ux/00_claude_skills --skill voice-e2e-test
Manual install
git clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/voice-e2e-test ~/.claude/skills/voice-e2e-test

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Voice E2E Test Skill

End-to-end test of the complete voice call pipeline.

**What this tests:**
- Call initiation and confirmation link generation
- Auth flow (localStorage token storage)
- "We're both here" button functionality
- Real-time transcript creation
- Score updates during call
- Report generation after call ends

---

## Prerequisites

- Docker compose services running locally
- Playwright installed (`pip install playwright && playwright install chromium`)

---

## Step Timing (MANDATORY)

Every step MUST output timing in this exact format:

```
[STEP X] START: HH:MM:SS
... command output ...
[STEP X] END: HH:MM:SS
```

**Wrap every command like this:**
```bash
echo "[STEP 1a] START: $(date +%H:%M:%S)" && \
<actual command here> && \
echo "[STEP 1a] END: $(date +%H:%M:%S)"
```

**Example output:**
```
[STEP 1a] START: 16:20:44
2025-12-23T19:20:45.073422+00:00
[STEP 1a] END: 16:20:45
```

⛔ **No timing output = step not executed properly.** The report timing data comes ONLY from this output. If you don't see `[STEP X] START/END` in your execution results, you cannot report timing for that step.

---

## Dynamic Script Generation

Generate complete Playwright scripts inline for each test step. Don't use pre-written script files.

**Pattern:** Use bash heredoc to write and run a complete Python script:
Read the full skill on GitHub

Details

Skill name
voice-e2e-test
Path
skills/voice-e2e-test/SKILL.md
Repo updated
10 January 2026

FAQ

What does the Voice E2E Test skill do?

Comprehensive E2E test of voice call pipeline - place call, verify auth flow, monitor transcripts/scores, verify report. Use when user says "test voice e2e", "run voice test", or "full voice test".

How do I install the Voice E2E Test skill?

Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Voice E2E Test popular?

It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.

Related skills

Add Integration

8

Freddy-CHEN-ux/00_claude_skills

Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.

Software Development

AI Agents

8

Freddy-CHEN-ux/00_claude_skills

Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)

AI, LLMs & Agents

AI LLM

8

Freddy-CHEN-ux/00_claude_skills

Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.

AI, LLMs & Agents

Xunit Test Patterns

5

vnovakovits/claude-skills

Apply Gerard Meszaros's "xUnit Test Patterns — Refactoring Test Code" (2007) — the canonical catalogue of test-automation patterns, the test-double taxonomy (Dummy, Stub, Spy, Mock, Fake), test smells, fixture strategies, and result-verification patterns. Use when writing or refactoring test code; diagnosing brittle, slow, erratic, or obscure tests; choosing and naming a test double; designing fixtures (fresh vs shared, Object Mother, Test Data Builder, setup styles); structuring the four-phase test; deciding where to draw the test boundary (subcutaneous / layer / round-trip); faking out-of-pr

Testing & QA

Verification Before Completion

8

Freddy-CHEN-ux/00_claude_skills

Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documentation updated.

Testing & QA

Data Result Validation

5

eshmith7/claude-skills-library

An honest read on whether a change, test or campaign actually worked, covering effect size, sample adequacy and the traps. Use for A/B tests, before and after comparisons or pilots.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.