twinmind-common-errors
Provides a quick reference to diagnose and resolve frequent TwinMind transcription and API errors.
Install
mkdir -p .claude/skills/twinmind-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7123" && unzip -o skill.zip -d .claude/skills/twinmind-common-errors && rm skill.zipInstalls to .claude/skills/twinmind-common-errors
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Diagnose and fix TwinMind common errors and exceptions.Key capabilities
- →Identify common TwinMind error modes
- →Verify API connectivity and authentication
- →Reset microphone permissions on macOS and Windows
- →Amplify or convert audio files for transcription
How it works
Matches error messages against a documented reference of failure modes and provides specific CLI or code-based remediation steps.
Inputs & outputs
When to use twinmind-common-errors
- →Fix 401 authentication errors
- →Resolve microphone access failures
- →Debug transcription service issues
- →Verify API connectivity
About this skill
TwinMind Common Errors
Overview
Quick reference for the most common TwinMind errors and their solutions.
Prerequisites
- TwinMind extension or API configured
- Access to error logs or console
- API credentials for testing
Instructions
Step 1: Identify the Error
Check error message in console, extension popup, or API response.
Step 2: Find Matching Error Below
Match your error to one of the documented cases.
Step 3: Apply Solution
Follow the solution steps for your specific error.
Error Reference
Authentication Failed
Error Message:
Error: Authentication failed - Invalid or expired API key
Status: 401 Unauthorized # HTTP 401 Unauthorized
Cause: API key is missing, expired, or incorrect.
Solution:
set -euo pipefail
# Verify API key is set correctly
echo $TWINMIND_API_KEY
# Test authentication
curl -H "Authorization: Bearer $TWINMIND_API_KEY" \
https://api.twinmind.com/v1/health
# Regenerate key if expired
# Visit: https://twinmind.com/settings/api
Microphone Access Denied
Error Message:
Error: Microphone permission denied
NotAllowedError: Permission denied
Cause: Browser or OS hasn't granted microphone access.
Solution:
Chrome:
1. Click lock icon in address bar
2. Site Settings > Microphone > Allow
3. Reload the page
macOS:
# Check current permissions
tccutil list com.google.Chrome
# Reset permissions (requires re-grant)
tccutil reset Microphone com.google.Chrome
Windows:
Settings > Privacy > Microphone > Allow apps to access microphone
Transcription Timeout
Error Message:
Error: Transcription timeout after 300000ms
RequestTimeoutError: Request exceeded timeout
Cause: Audio file too large or network issues.
Solution:
// Increase timeout for large files
const client = new TwinMindClient({
apiKey: process.env.TWINMIND_API_KEY,
timeout: 600000, // 10 minutes # 600000 = configured value
});
// Or use async processing with webhooks
const response = await client.post('/transcribe', {
audio_url: audioUrl,
async: true,
webhook_url: 'https://your-server.com/webhook/twinmind',
});
Rate Limit Exceeded
Error Message:
Error: Rate limit exceeded. Please retry after 60 seconds.
Status: 429 Too Many Requests # HTTP 429 Too Many Requests
X-RateLimit-Remaining: 0
Cause: Too many API requests in a short period.
Solution:
// Implement exponential backoff
async function withBackoff<T>(operation: () => Promise<T>): Promise<T> {
const maxRetries = 5;
for (let attempt = 0; attempt < maxRetries; attempt++) {
try {
return await operation();
} catch (error: any) {
if (error.response?.status !== 429) throw error; # HTTP 429 Too Many Requests
const retryAfter = parseInt(error.response.headers['retry-after'] || '60');
console.log(`Rate limited. Waiting ${retryAfter}s...`);
await new Promise(r => setTimeout(r, retryAfter * 1000)); # 1000: 1 second in ms
}
}
throw new Error('Max retries exceeded');
}
See twinmind-rate-limits for detailed rate limiting strategies.
Audio Format Not Supported
Error Message:
Error: Unsupported audio format
AudioFormatError: Format 'xyz' is not supported
Cause: Audio file in incompatible format.
Solution:
# Convert to supported format using ffmpeg
ffmpeg -i input.xyz -acodec libmp3lame -q:a 2 output.mp3
# Supported formats: MP3, WAV, M4A, WebM, OGG, FLAC
Supported formats:
| Format | Extension | Notes |
|---|---|---|
| MP3 | .mp3 | Recommended, good compression |
| WAV | .wav | Best quality, larger files |
| M4A | .m4a | iOS recordings |
| WebM | .webm | Browser recordings |
| OGG | .ogg | Open format |
| FLAC | .flac | Lossless audio |
No Audio Detected
Error Message:
Error: No audio detected in input
TranscriptionError: Empty or silent audio
Cause: Audio file is silent, corrupted, or too quiet.
Solution:
# Check audio file properties
ffprobe -i audio.mp3 -show_streams -select_streams a
# Check audio levels
ffmpeg -i audio.mp3 -filter:a volumedetect -f null /dev/null
# Amplify quiet audio
ffmpeg -i quiet.mp3 -filter:a "volume=2.0" amplified.mp3
Speaker Diarization Failed
Error Message:
Error: Speaker diarization failed
DiarizationError: Unable to identify distinct speakers
Cause: Single speaker, overlapping speech, or poor audio quality.
Solution:
// Retry without diarization
const transcript = await client.transcribe(audioUrl, {
diarization: false, // Disable diarization
});
// Or provide speaker count hint
const transcript = await client.transcribe(audioUrl, {
diarization: true,
expected_speakers: 3, // Help the model
});
Calendar Sync Failed
Error Message:
Error: Calendar sync failed
OAuth2Error: Token expired or revoked
Cause: Google/Microsoft OAuth token expired.
Solution:
1. Open TwinMind extension
2. Go to Settings > Integrations
3. Click "Disconnect" for calendar
4. Click "Connect" to re-authorize
5. Grant all requested permissions
Summary Generation Failed
Error Message:
Error: Summary generation failed
GenerationError: Transcript too short for summarization
Cause: Transcript doesn't have enough content.
Solution:
// Check transcript length before summarization
const minWordsForSummary = 50;
const wordCount = transcript.text.split(/\s+/).length;
if (wordCount < minWordsForSummary) {
console.log('Transcript too short for summary');
return null;
}
const summary = await client.summarize(transcript.id);
Extension Not Loading
Error Message:
Extension error: Unable to establish connection
Chrome error: Extension context invalidated
Cause: Extension crashed, outdated, or Chrome issue.
Solution:
1. Disable and re-enable extension:
chrome://extensions/ > TwinMind > Toggle off/on
2. Clear extension data:
Right-click extension > Manage Extensions > Clear data
3. Reinstall extension:
Remove > Visit Chrome Web Store > Reinstall
4. Check for conflicts:
Disable other extensions temporarily
Network Error
Error Message:
Error: Network request failed
TypeError: Failed to fetch
ERR_CONNECTION_REFUSED
Cause: Network connectivity issues or firewall blocking.
Solution:
set -euo pipefail
# Test API connectivity
curl -v https://api.twinmind.com/v1/health
# Check if firewall is blocking
telnet api.twinmind.com 443 # 443: HTTPS port
# Test with different DNS
curl --resolve api.twinmind.com:443:$(dig +short api.twinmind.com) \ # HTTPS port
https://api.twinmind.com/v1/health
Quick Diagnostic Commands
set -euo pipefail
# Check TwinMind API status
curl -s api/v2/status.json | jq '.status'
# Verify API connectivity
curl -I https://api.twinmind.com/v1/health
# Test authentication
curl -H "Authorization: Bearer $TWINMIND_API_KEY" \
https://api.twinmind.com/v1/me
# Check local environment
env | grep TWINMIND
# Validate audio file
ffprobe -v error -show_format -show_streams audio.mp3
Escalation Path
- Collect evidence with
twinmind-debug-bundle - Check TwinMind status page:
- Search community forum:
- Contact support with request ID: [email protected]
Resources
- TwinMind Status Page
- TwinMind Support
- TwinMind Community
- Error Code Reference
Next Steps
For comprehensive debugging, see twinmind-debug-bundle.
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
Error Handling
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with debugging |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Examples
Basic usage: Apply twinmind common errors to a standard project setup with default configuration options.
Advanced scenario: Customize twinmind common errors for production environments with multiple constraints and team-specific requirements.
When not to use it
- →When the issue is unrelated to TwinMind services
- →When the error is caused by third-party hardware failure
Prerequisites
Limitations
- →Requires manual identification of the error type
- →Some solutions require administrative access to system settings
How it compares
Provides targeted, environment-specific commands for TwinMind rather than generic debugging advice.
Compared to similar skills
twinmind-common-errors side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| twinmind-common-errors (this skill) | 1 | 27d | Caution | Intermediate |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
| claude-in-chrome-troubleshooting | 2 | 2mo | Review | Intermediate |
| openrouter-common-errors | 3 | 27d | Caution | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
claude-in-chrome-troubleshooting
trailofbits
Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.
openrouter-common-errors
jeremylongshore
Execute diagnose and fix common OpenRouter API errors. Use when troubleshooting failed requests. Trigger with phrases like 'openrouter error', 'openrouter not working', 'openrouter 401', 'openrouter 429', 'fix openrouter'.
linear-common-errors
jeremylongshore
Diagnose and fix common Linear API errors. Use when encountering Linear API errors, debugging integration issues, or troubleshooting authentication problems. Trigger with phrases like "linear error", "linear API error", "debug linear", "linear not working", "linear authentication error".
gamma-common-errors
jeremylongshore
Debug and resolve common Gamma API errors. Use when encountering authentication failures, rate limits, generation errors, or unexpected API responses. Trigger with phrases like "gamma error", "gamma not working", "gamma API error", "gamma debug", "gamma troubleshoot".
groq-common-errors
jeremylongshore
Diagnose and fix Groq common errors and exceptions. Use when encountering Groq errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "groq error", "fix groq", "groq not working", "debug groq".