safe-agent-change

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.

Build and run simulated-caller tests against a Synthflow voice agent, then report which scenarios pass or fail with transcript evidence. Use this whenever the user wants to test an agent before or after a change, check that a prompt fix works, reproduce a failure from a real call, build a test suite, or re-run existing simulations. Trigger on phrases like "test the agent", "run the simulations", "regression test", "make sure this didn't break anything", "build a test suite", "reproduce this call", or "re-run the tests".

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Teach the user a new skill or concept, within this workspace.

No description in the SKILL.md.

No description in the SKILL.md.

Ask which skill or flow fits your situation. A router over the skills in this repo.

No description in the SKILL.md.

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.