Claude-code-plugins-plus-skills twinmind-incident-runbook
install
source · Clone the upstream repo
git clone https://github.com/jeremylongshore/claude-code-plugins-plus-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/saas-packs/twinmind-pack/skills/twinmind-incident-runbook" ~/.claude/skills/jeremylongshore-claude-code-plugins-plus-skills-twinmind-incident-runbook && rm -rf "$T"
manifest:
plugins/saas-packs/twinmind-pack/skills/twinmind-incident-runbook/SKILL.mdsource content
TwinMind Incident Runbook
Overview
Incident response for TwinMind failures: transcription not starting, audio not captured, sync failures, and calendar disconnect. TwinMind uses the Ear-3 speech model (5.26% WER, 3.8% DER) for transcription, with GPT-4, Claude, and Gemini for AI summarization.
Prerequisites
- TwinMind account (Free, Pro $10/mo, or Enterprise)
- Chrome extension installed and authenticated
- Understanding of TwinMind workflow
Instructions
Step 1: Setup
TwinMind operates as a Chrome extension and mobile app with optional API access for Pro/Enterprise users.
# TwinMind API access (Pro/Enterprise) export TWINMIND_API_KEY="your-api-key" curl -H "Authorization: Bearer $TWINMIND_API_KEY" https://api.twinmind.com/v1/health # Expected: {"status": "ok"}
Step 2: Implementation
// TwinMind Incident Runbook implementation // Core TwinMind integration const twinmind = { transcriptionModel: "ear-3", languages: ["en", "es", "ko", "ja", "fr"], features: ["transcription", "summary", "action-items"], privacyMode: "on-device", // Audio never stored }; // Check transcription capabilities async function verify() { const health = await fetch("https://api.twinmind.com/v1/health"); console.log("TwinMind status:", await health.json()); }
Step 3: Verification
# Verify TwinMind integration curl -H "Authorization: Bearer $TWINMIND_API_KEY" https://api.twinmind.com/v1/health | jq .
Key TwinMind Specifications
| Feature | Specification |
|---|---|
| Transcription model | Ear-3 (5.26% WER) |
| Speaker diarization | 3.8% DER |
| Languages | 140+ supported |
| Audio processing | On-device (no recordings stored) |
| AI models | GPT-4, Claude, Gemini (auto-routed) |
| Platforms | Chrome extension, iOS, Android |
| Pricing | Free / Pro $10/mo / Enterprise custom |
Output
- TwinMind Incident Runbook configured and verified
- TwinMind integration operational
- Meeting transcription workflow ready
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Microphone access denied | Browser permissions not granted | Enable in Chrome settings |
| Transcription not starting | Audio source not detected | Check microphone selection |
| API key invalid | Incorrect or expired key | Regenerate in TwinMind dashboard |
| Sync failed | Network interruption | Check connection, retry |
| Calendar disconnect | OAuth token expired | Re-authorize in Settings |
Resources
Next Steps
See
twinmind-prod-checklist for production readiness.
Examples
Basic: Configure incident runbook with default TwinMind settings for standard meeting workflows.
Enterprise: Customize for high-volume meeting transcription with monitoring and alerting.