regression-test

Create, update, test, and attach Synthflow agent actions over MCP — custom HTTP actions, information extractors, transfers, SMS, real-time booking (Cal.com, GoHighLevel), IVR navigation, custom evaluations, and call-summary emails. Use this whenever the user wants to give an agent a new capability, connect it to an API or CRM, extract data from calls, add a transfer or SMS, set up booking, change an action's URL, body, or variables, or fix an action that isn't firing or is failing. Trigger on phrases like "add an action", "call my API during the call", "extract the caller's email", "set up a transfer", "connect booking", "update the webhook URL", or "the action isn't working".

Build a call-volume and outcome report for a Synthflow agent, workspace, or agency — counts, durations, statuses, end-call reasons, call reasons from information extractors, transfer and booking results, and trends over a period. Use this whenever the user wants a daily, weekly, or monthly report, a call-reason breakdown, KPIs for a customer, an operations dashboard dataset, or numbers like "how many calls did we get", "what are people calling about", or "what share of calls were transferred". For a quality audit of individual calls, use the call-review skill instead.

Review the last 100 calls for an agent and surface problems. Use this whenever the user wants a call-quality audit, a QA pass over recent calls, a "what's going wrong with this agent" review, or to find failed, unresolved, dropped, or otherwise problematic calls. Trigger on phrases like "review my calls", "what's wrong with the calls", "QA the last 100 calls", "find bad calls", or "audit recent calls".

Investigate why a specific Synthflow call (or a small set of similar calls) went wrong — failed or missed transfers, calls cut off, the agent going silent or repeating itself, actions or webhooks that didn't fire or failed, wrong data captured, or outbound calls that didn't connect. Use this whenever the user points at a call or a phone number and asks what happened or why, e.g. "why did this call drop", "the transfer didn't ring", "the booking didn't happen on this call", "the webhook never arrived", or "check the call from +1… this morning". For an audit of many recent calls, use the call-review skill instead.

Review AI voice-agent prompts, especially Synthflow Single-Prompt, for contradictions, missing context, unsafe tool/action behavior, escalation gaps, compliance risk, and regression risk. Use this when the user asks to review, audit, validate, improve, or compare a prompt before deployment.

Make a change to a live Synthflow voice agent safely — record a baseline, save a draft, review the diff, publish only on approval, verify the published state, and roll back if needed. Use this whenever the user wants to edit, update, fix, tweak, or publish an agent's prompt, greeting, voice, transcriber, LLM, actions, or any other setting, or wants to roll an agent back. Trigger on phrases like "update the prompt", "change the voice", "fix the agent", "publish the draft", "push this live", "roll back the agent", or "undo the last change".

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Automate browser interactions, test web pages and work with Playwright tests.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.