A workflow for writing Genesys Cloud Architect call and messaging flows in TypeScript, a programming language. It uses the Architect Scripting SDK to check the code and can deploy completed flows.

Creating or deploying inbound-call, bot, email, message, and workflow flows, including greetings, menus, routing, queue transfers, and data lookups.

Building a flow by hand can lead to invalid code or deployment errors. Type checking and a defined deployment process catch problems before the flow is published.

write-flow — Skill by MakingChatbots

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/makingchatbots/genesys-cloud-plugins/write-flow

Any agent

npx skills add MakingChatbots/genesys-cloud-plugins --skill write-flow

Clone the repo

git clone --depth 1 https://github.com/MakingChatbots/genesys-cloud-plugins

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,409 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00035	$0.01409
Opus 5	$0.00017	$0.00705
Sonnet 5	$0.00007	$0.00282
Haiku 4.5	$0.00003	$0.00141

Measured yesterday against content hash f06d431ed8ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

write-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/write-flow/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write & Deploy Architect Flows

Create Genesys Cloud Architect flows as TypeScript, typecheck them, and deploy them via the deploy_flow MCP tool.

Prerequisites

The user's project must have the Architect Scripting SDK installed for type checking:

npm install --save-dev purecloud-flow-scripting-api-sdk-javascript

Deploy only (existing flow file)

If the user already has a flow file and just wants to deploy it, skip straight to step 5 — call the deploy_flow MCP tool with the file path. Only fall back to steps 1–4 if deployment fails or the user asks for help writing/fixing the flow.

Workflow

1. Understand the requirement

Ask the user:

Flow type: inbound call, bot flow, digital bot flow, inbound email, inbound message (SMS), or workflow
What it should do: routing, menus, greetings, queue transfers, data lookups, etc.
Flow name: what to name the flow in Architect

Only ask about queue names if the user's description involves queue transfers. Not every flow routes to a queue.

2. Read the relevant references

Before writing any flow code, read these reference files from this skill:

Always read: references/sdk-patterns.md — core SDK patterns and the buildFlow contract
Always read: references/gotchas.md — SDK quirks that cause silent failures
Always read: references/action-reference.md — available action types
Read when the flow uses expressions: references/expression-reference.md — expression language syntax, functions, operators, data types, and common patterns. Read this whenever the flow involves conditional logic, dynamic text, variable manipulation, date/time calculations, or any setExpression() / expression property usage.
Read the matching example from references/examples/:
- bot-flow.md — bot flow with NLU intent detection, slot filling, and testing
- digital-bot-flow.md — digital bot with menu, free-text fallback, and exit
- inbound-call.md — IVR with menus and queue transfers
- inbound-email.md — auto-reply and queue transfer
- inbound-message.md — SMS auto-reply and queue transfer
- workflow.md — callback workflow

Read the full file on GitHub · 148 lines

Files

What ships with it

10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 148 lines · 35 tokens per session scan A f06d431ed8ef

Subscribe to this mod's changes

write-flow is a skill published in the GitHub repository MakingChatbots/genesys-cloud-plugins (9 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,409 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloud Languages Writing and docs

systematic-debugging

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

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens