jeremylongshore / speak-incident-runbook
Install for your project team
Run this command in your project directory to install the skill for your entire team:
mkdir -p .claude/skills/speak-incident-runbook && curl -L -o skill.zip "https://fastmcp.me/Skills/Download/4231" && unzip -o skill.zip -d .claude/skills/speak-incident-runbook && rm skill.zipProject Skills
This skill will be saved in .claude/skills/speak-incident-runbook/ and checked into git. All team members will have access to it automatically.
Important: Please verify the skill by reviewing its instructions before using it.
Execute Speak incident response procedures with triage, mitigation, and postmortem. Use when responding to Speak-related outages, investigating errors, or running post-incident reviews for language learning feature failures. Trigger with phrases like "speak incident", "speak outage", "speak down", "speak on-call", "speak emergency", "speak broken".
0 views
0 installs
Skill Content
---
name: speak-incident-runbook
description: |
Incident response for Speak API outages: triage, fallback to offline mode, and recovery procedures.
Use when implementing incident runbook,
or managing Speak language learning platform operations.
Trigger with phrases like "speak incident runbook", "speak incident runbook".
allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
tags: [saas, speak, api]
---
# Speak Incident Runbook
## Overview
Incident response for Speak API outages: triage, fallback to offline mode, and recovery procedures.
## Prerequisites
- Completed `speak-install-auth` setup
- Valid API credentials configured
- Understanding of Speak API patterns
## Instructions
### Step 1: Configuration
Configure incident runbook for your Speak integration. Speak uses OpenAI's GPT-4o for AI tutoring and Whisper for speech recognition.
```typescript
// speak_incident_runbook_config.ts
const config = {
apiKey: process.env.SPEAK_API_KEY!,
appId: process.env.SPEAK_APP_ID!,
environment: process.env.NODE_ENV || 'development',
};
```
### Step 2: Implementation
```typescript
// Core implementation for speak incident runbook
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");
}
```
### Step 3: Verification
```bash
npm test
```
## Output
- Speak Incident Runbook configured and verified
- CI pipeline with mocked Speak API tests
- Error handling and monitoring in place
## Error Handling
| 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 |
## Resources
- [Speak Website](https://speak.com)
- [OpenAI Realtime API](https://platform.openai.com/docs/guides/realtime)
- [Speak GPT-4 Blog](https://speak.com/blog/speak-gpt-4)
## Next Steps
For deployment, see `speak-deploy-integration`.
## Examples
**Basic**: Apply incident runbook with default settings for a standard Speak integration.
**Production**: Configure with monitoring, alerting, and team-specific language learning requirements.