What is manage-workflows?

A skill for creating and managing automated Voice Logica workflows. A workflow is a sequence of actions that starts from an event, such as a call, email, API request, or keyword.

Use it to create, edit, test, run, version, and assign workflows, including triggers, action nodes, branching cases, and connections between steps.

It provides a way to build and maintain repeatable automation without manually handling each event.

manage-workflows — Skill for Claude Code by voicelogica

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.

Any agent

npx skills add voicelogica/voice-logica-plugin --skill manage-workflows

Clone the repo

git clone --depth 1 https://github.com/voicelogica/voice-logica-plugin

Made for: Claude Code.

Or install voice-logica, the plugin that ships this one along with the rest of its 17 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-workflows/github.svg)](https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-workflows)

Your own site

<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-workflows"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-workflows/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-workflows"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00051	$0.01299
Opus 5	$0.00026	$0.00649
Sonnet 5	$0.00010	$0.00260
Haiku 4.5	$0.00005	$0.00130

Measured 11d ago against content hash dec9eda0237c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

manage-workflows 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 11d ago.

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/manage-workflows/SKILL.md · 121 lines

How it starts

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

Manage Voice Logica workflows

Use workflow MCP tools. Do not invent workflow IDs, node IDs, or trigger names.

The Workflows menu in the app is admin role. MCP workflow tools still follow whatever access the connected user has. Tunnels (for private HTTP ERPs) are also admin-only.

MCP tools

Workflow CRUD and run:

list_workflows / get_workflows / get_workflow
create_workflow / update_workflow / delete_workflow
run_workflow / test_workflow

Triggers:

add_workflow_trigger / update_workflow_trigger / remove_workflow_trigger

Nodes and graph:

add_workflow_node / update_workflow_node / remove_workflow_node
add_switch_case
connect_workflow_nodes / disconnect_workflow_nodes

Versions:

list_workflow_versions / save_workflow_version / delete_workflow_version

Assign to an agent:

get_agent_workflows / update_agent_workflows

Triggers

onAPICall — HTTP into the workflow
onCallEnd — after the call
onCallStart — when the call starts
onKeywordDetected — keyword during the call
duringCall — mid-call automation
onEmailReceived — inbound mailbox email

Nodes

emailConfig — send email
apiCall — HTTP request
llmCompletion — model step
sendSms — SMS
codeExecution — script step
if — boolean branch
switch — multi-way branch (add_switch_case)
loop — iterate

Limits: table nodes max 500 rows / 50 cols. Call-trigger function name max 64; condition max 500.

`apiCall` shape (easy to get wrong)

Canonical shape:

headers and params are lists of {key, value}, not JSON maps
Query string values go in params, not queryParams (there is no queryParams field)
Body is a raw JSON string plus bodyType

headers: [{key: "Authorization", value: "Bearer …"}]
params:  [{key: "orderId", value: "{{orderId}}"}]

Do not send {"Authorization": "Bearer …"}.

If a request works in Postman but fails or returns a plausible-wrong 200 from the node, check this shape first — not firewall or DNS. Other working integrations on the same company already kill the network theory.

Read the full file on GitHub · 121 lines

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.

11d ago First seen · 121 lines · 51 tokens per session scan A dec9eda0237c

Subscribe to this mod's changes

manage-workflows is a skill published in the GitHub repository voicelogica/voice-logica-plugin (0 stars, last pushed 19d ago), licensed MIT. It adds 51 tokens to every session and 1,299 once invoked, about $0.0003 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.

Building agents gemini-cli-extension mcp voice ai

manage-workflows

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Manage Voice Logica workflows

MCP tools

Triggers

Nodes

`apiCall` shape (easy to get wrong)

What this file has done since we first saw it

Other skills, from other repositories

gws-gmail-send

gws-shared

gws-sheets

gws-gmail

gws-modelarmor

gws-docs

manage-workflows

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Manage Voice Logica workflows

MCP tools

Triggers

Nodes

apiCall shape (easy to get wrong)

What this file has done since we first saw it

Other skills, from other repositories

gws-gmail-send

gws-shared

gws-sheets

gws-gmail

gws-modelarmor

gws-docs

`apiCall` shape (easy to get wrong)