claude-marketplace

Designs the structural skeleton of a Voicenter Bot via interview. Use this skill when the user wants to create, design, scope, or modify a Voicenter voice/chat bot — phrases like "design a bot", "create an agent spec", "build a Voicenter bot", "patch this bot", "add an intent", "change the bot's persona", "modify the flow graph", or any reference to the Agent Spec Designer / Skill 1 in the Voicenter bot generation pipeline. Produces an Agent Spec markdown file (sections 1-4, 4.5, section 5 stubs, section 6 initial, section 7 init). Two named entry modes — greenfield (no spec attached) and patch (spec attached). Does NOT author per-intent language content (validationPrompt, post-execution intentInstructions) — that's Skill 2 (Intent Detail Author). Does NOT emit wire-format JSON — that's Skill 3 (JSON Assembler).

Assembles a fully-detailed Voicenter Agent Spec into Bot JSON wire format — the final mechanical step in the three-skill pipeline. Use this skill when an Agent Spec exists with all section 5 entries marked `[detailed]` and the user wants the deployable JSON. Trigger phrases include "run Skill 3", "assemble the JSON", "emit the bot JSON", "publish the bot", "build the wire-format", "Skill 3 (JSON Assembler)", or any direct continuation from Skill 2's completion handoff. Produces a single `bot-<name>-<date>.json` file plus a banner identifying every fail-loud sentinel and any drift between spec section 6 and what Skill 3 regenerated. Refuses to assemble if any intent is still `[structural]` or `[detailed-revisit]`, or if the spec deviates from the strict template (Doc 2 §3.7). Runs the §15.4 cross-reference pass — 23 checks (8 §15.4 + 3 Compass + 3 botIntents-role + 1 duplicate-global-intent + 8 field-placement doctrine), checks 1–7, 11–13, 15, and 16–21 blocking. Does NOT author any text content (Skills 1 and

Authors the per-intent language content of a Voicenter Agent Spec — slot descriptions, validationPrompt, post-execution intentInstructions, and RT-specific Configuration text. Use this skill when an Agent Spec exists with section 5 entries marked `[structural]` or `[detailed-revisit]`, and the user wants to fill them in. Trigger phrases include "run Skill 2", "detail the intents", "fill in the per-intent fields", "Skill 2 (Intent Detail Author)", or any direct continuation from Skill 1's handoff hint. Walks intents in user-confirmed batches with a checkpoint after each batch. Reactivable — invoke as many times as needed; spec state is the resume point. Does NOT modify the structural skeleton (sections 1, 2, 3, 4, 4.5.1/.2/.4) — that's Skill 1 (Agent Spec Designer). Does NOT emit wire-format JSON — that's Skill 3 (JSON Assembler).

Pull call detail records (CDR) from Voicenter using the Call Log API

Receive and handle CDR push notifications from Voicenter after every call ends

Initiate or terminate outgoing calls using the Voicenter Click2Call API

Implement a Pop-Up Screen endpoint that Voicenter calls during incoming calls to display caller CRM data to agents

CRM integration scoping & onboarding playbook. Use when scoping a NEW CRM integration, running a discovery/feasibility/spec meeting, or choosing between API vs Chrome extension vs local BAT, Push vs Pull, and CRM-owned vs Voicenter-owned screen pop. Covers: CRM type detection (on-premise vs web), entity/field mapping, Click2Call station-code setup, screen pop architecture (who owns it), trigger-stage rules (ring/answer/hangup), call history method (CDR Push vs Call Log Pull), and full decision checklist. Trigger on: new CRM, CRM onboarding, integration spec, feasibility, station code, screen pop ownership, on-premise vs web CRM, Push vs Pull.

Pull specific call data by CallID with AI analysis — summary, emotions, personality traits, and insights. Does NOT include full transcription (CDR Notification only). Use for on-demand AI enrichment, CRM quality reviews, and retroactive summary retrieval via the two-step Call Log → GetCallHistory flow.

Connect Claude Code to the Voicenter MCP server using OAuth authentication

Get a real-time snapshot of all active calls and queue activity via the Voicenter Active Calls API

Add or remove phone numbers from the Voicenter organization blacklist

Retrieve the full list of active extensions and users in a Voicenter organization

Build an External Layer IVR endpoint that lets Voicenter route inbound calls based on your CRM business logic

Track which marketing campaign or web page generated an inbound call using the Voicenter Lead Tracker JS SDK

Set agent login/logout and status via the Voicenter Login/Logout API

Mute or unmute call recording in real time via the Voicenter Mute Call Recording API

Manage auto-dialer campaigns via the Voicenter Dialer API — add/remove destinations, control campaigns, manage agents

Connect to Voicenter real-time call and agent events via the EventsSDK (socket.io)

Build a VoiceBot data endpoint that the Voicenter Voice Agent calls mid-conversation to fetch dynamic CRM data