speak-performance-tuning
Optimize Speak API latency with audio preprocessing, response caching, and connection pooling. Use when implementing performance tuning, or managing Speak language learning platform operations. Trigger with phrases like "speak performance tuning", "speak performance tuning". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-performance-tuning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Speak Performance Tuning ## Overview Optimize Speak API latency with audio preprocessing, response caching, and connection pooling. ## Prerequisites - Completed `speak-install-auth` setup - Valid API credentials configured - Understanding of Speak API patterns ## Instructions ### Step 1: Configuration Configure performance tuning for your Speak integration. Speak uses OpenAI's GPT-4o for AI tuto
What does the speak-performance-tuning skill do?
Optimize Speak API latency with audio preprocessing, response caching, and connection pooling. Use when implementing performance tuning, or managing Speak language learning platform operations. Trigger with phrases like "speak performance tuning", "speak performance tuning". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-performance-tuning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.