Speak incident runbook

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/saas-packs/speak-pack/skills/speak-incident-runbook

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-incident-runbook

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

'Incident response for Speak API outages: triage, fallback to offline mode, and recovery procedures.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, as published. Nobody here has run it

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.

// 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

// 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

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

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.