Notre avis
Diagnostique et gère le broker de messages Samara.app, en vérifiant son état d'exécution, les logs, l'autorisation Full Disk Access, et en effectuant des redémarrages ou reconstructions.
Points forts
- Fournit une commande unique pour vérifier si Samara est en cours d'exécution et consulter les logs récents.
- Inclut des instructions claires pour vérifier l'autorisation Full Disk Access et la validité de la signature du code.
- Offre une méthode sûre et documentée pour redémarrer ou reconstruire Samara en évitant les pièges de permissions courants.
Limites
- Uniquement applicable à Samara.app sur macOS ; pas utile pour d'autres brokers de messages ou plateformes.
- Nécessite un environnement préconfiguré (par exemple, le script `update-samara`) pour les reconstructions ; sinon incomplet.
- Les diagnostics reposent sur la lecture de fichiers de logs spécifiques et de logs système qui peuvent varier.
Utilisez-le lorsque les messages iMessage ne sont pas détectés par votre agent IA, que Samara a planté ou que vous devez confirmer son état de fonctionnement.
Ne l'utilisez pas pour un débogage macOS général non lié à Samara, ou si le problème se situe en dehors du périmètre de Samara (par exemple, iMessage lui-même est en panne).
Analyse de sécurité
PrudenceThe skill uses Bash for legitimate system management tasks (process control, log reading, code signing checks) and explicitly forbids dangerous practices like copying from DerivedData. The hook script is a mitigation but introduces additional attack surface. No network calls or destructive commands, but the capabilities are powerful and could be misused if the skill were compromised.
- •Uses Bash to kill and restart applications (pkill, open)
- •Reads system logs (log show) that may contain sensitive information
- •Uses a hook script (block-deriveddata-copy.sh) with elevated access
Exemples
Samara seems to not be working. Please check if it's running, view the last few lines of its logs, and confirm Full Disk Access status.Restart Samara.app because it stopped responding. After restarting, verify it's running and check for any errors.Samara crashed after an update and Full Disk Access is revoked. Rebuild it using the proper update-samara script and verify the code signature.name: samara description: Debug, check, or restart Samara.app - the message broker. Use when messages aren't being detected, Samara crashed, need to view logs, check Full Disk Access, or restart the app. Trigger words: samara, messages not working, restart, logs, FDA, broker. context: fork allowed-tools:
- Bash
- Read
- Grep
- Glob
- Write
hooks:
PreToolUse:
- matcher: "Bash"
hooks:
- type: command command: "/Users/claude/Developer/samara-main/.claude/hooks/block-deriveddata-copy.sh" timeout: 5
- matcher: "Bash"
hooks:
Samara Debug and Control
Diagnose and manage Samara.app, the message broker that connects iMessage to Claude.
Quick Actions
Check if Running
pgrep -fl Samara
ps aux | grep -i [S]amara
View Recent Logs
# Samara's own logs
tail -50 ~/.claude-mind/logs/samara.log 2>/dev/null
# System logs for Samara
log show --predicate 'process == "Samara"' --last 5m 2>/dev/null | tail -30
Restart Samara
# Kill if running
pkill -f Samara
# Wait a moment
sleep 2
# Relaunch
open /Applications/Samara.app
Tip: This sequence is a good candidate for the Bash subagent (Task tool with subagent_type=Bash) to avoid polluting context with intermediate steps.
Check Full Disk Access
# This will work if FDA is granted
ls ~/Library/Messages/chat.db && echo "FDA: OK" || echo "FDA: MISSING"
# Check code signature (Team ID must be stable)
codesign -d -r- /Applications/Samara.app 2>&1 | head -5
Common Issues
Messages Not Being Detected
- Check Samara is running
- Check FDA is intact
- Check chat.db is readable
- Look for errors in logs
Samara Crashed
- Check system logs for crash reason
- Restart with
open /Applications/Samara.app - If repeated crashes, may need rebuild
FDA Revoked After Update
This happens if Team ID changed during rebuild:
# Check current signature - MUST show G4XVD3J52J
codesign -d -r- /Applications/Samara.app 2>&1 | grep "subject.OU"
# If shows 7V9XLQ8YNQ or any other team: WRONG CERTIFICATE USED
# Must rebuild properly and re-grant FDA
Rebuild Samara
CRITICAL: ONLY use the update-samara script. NEVER copy from DerivedData.
A Claude instance previously broke FDA by copying a Debug build from
~/Library/Developer/Xcode/DerivedData/. This used automatic signing which picked the WRONG certificate and revoked all permissions.
The ONLY correct way to rebuild:
~/.claude-mind/bin/update-samara
FORBIDDEN (will break FDA):
cp -R ~/Library/Developer/Xcode/DerivedData/.../Samara.app /Applications/xcodebuild -configuration Debugfor deployment- Any manual copy of Samara.app to /Applications
Verify after rebuild:
codesign -d -r- /Applications/Samara.app 2>&1 | grep "subject.OU"
# Must show: G4XVD3J52J
# If shows: 7V9XLQ8YNQ - WRONG! FDA will be revoked
Diagnostic Report
When troubleshooting, gather:
- Is Samara running?
- FDA status
- Recent log errors
- Last successful message detection
- Code signature validity
Present findings clearly with recommended actions.
Related Skills
For specific issues, use these specialized skills:
/diagnose-leaks— Debug thinking traces or session IDs leaking into messages/debug-session— Debug session management, batching, and task routing/status— Quick system health check
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.