SpeakSwiftlyServer

Use when a user wants Speak Swiftly to read Codex replies aloud automatically through Codex lifecycle hooks, including plugin-managed hook setup, hook command path diagnosis, hook doctor interpretation, duplicate-hook diagnosis, centralized hook logs, final-reply TTS troubleshooting, or validation from another working directory.

Use when a user wants SpeakSwiftly voice-profile or speech-generation help, including voice creation from text or audio over HTTP, profile listing over slim MCP or HTTP, immediate spoken playback over MCP, retained audio artifacts over HTTP, retained batch jobs over HTTP, and generation artifact tracking over HTTP.

Use when a user wants to inspect or control the running SpeakSwiftlyServer runtime, including readiness, queues, playback state, active requests, generation backlog, playback backlog, backend switching, model reloads, queue clearing, request cancellation, or the local control panel. Use slim MCP resources for broad reads, HTTP endpoints for controls, and the browser-served control panel for visual operator help.

Use when a user wants general help with the slim Speak Swiftly MCP surface, including broad requests to inspect runtime state, read replies aloud, draft voice or text-profile guidance, or decide whether to use MCP resources, MCP prompts, the live-speech MCP tool, or HTTP endpoints.

Use when a user wants to inspect or change SpeakSwiftly text normalization, including built-in style changes, active or stored text profiles, replacement authoring, persistence reload or save operations, and effective-profile verification before speech generation. Use slim MCP resources/prompts for orientation and drafting; use HTTP endpoints for mutations and detailed reads.

Use when a user wants to set up SpeakSwiftlyServer on their machine as a per-user LaunchAgent, or needs to install, refresh, promote, inspect, validate, troubleshoot, or remove that background service. This skill covers the supported launch-agent CLI workflow, plugin-aware Codex access expectations, required config-file checks, staged-artifact expectations, and end-to-end HTTP plus MCP health verification.