From speak-pack
Automates Speak integration testing with a GitHub Actions pipeline featuring mocked API tests and audio validation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/speak-pack:speak-ci-integrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
GitHub Actions pipeline for Speak integrations with mocked API tests and audio validation.
GitHub Actions pipeline for Speak integrations with mocked API tests and audio validation.
speak-install-auth setupConfigure ci integration for your Speak integration. Speak uses OpenAI's GPT-4o for AI tutoring and Whisper for speech recognition.
// speak_ci_integration_config.ts
const config = {
apiKey: process.env.SPEAK_API_KEY!,
appId: process.env.SPEAK_APP_ID!,
environment: process.env.NODE_ENV || 'development',
};
// Core implementation for speak ci integration
import { SpeakClient } from '@speak/language-sdk';
const client = new SpeakClient(config);
// CI test with mocked responses
async function runCITests() {
const mockClient = new MockSpeakClient();
await mockClient.assessPronunciation({ audioPath: "test.wav", targetText: "hello", language: "en" });
console.log("CI tests passed");
}
npm test
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Invalid API key | Verify SPEAK_API_KEY |
| 429 Rate Limited | Too many requests | Implement backoff |
| Connection timeout | Network issue | Check connectivity to api.speak.com |
| Audio format error | Wrong codec | Convert to WAV 16kHz mono |
For deployment, see speak-deploy-integration.
Basic: Apply ci integration with default settings for a standard Speak integration.
Production: Configure with monitoring, alerting, and team-specific language learning requirements.
npx claudepluginhub pw00kt/fuzzy-sniffle --plugin speak-pack2plugins reuse this skill
First indexed Jul 18, 2026
Automates Speak integration testing with a GitHub Actions pipeline featuring mocked API tests and audio validation.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.