Vérification de Capacités

VérifiéSûr

Vérifiez si une action spécifique est possible et diagnostiquez les obstacles. Utilisez pour vérifier les permissions, l'existence de capacités ou dépanner les dysfonctionnements.

Spar Skills Guide Bot
DeveloppementIntermédiaire
4002/06/2026
Claude Code
#capability#permissions#troubleshooting#automation#system

Recommandé pour

Notre avis

Vérifie si une action spécifique est réalisable et diagnostique les blocages potentiels (permissions, configurations, services).

Points forts

  • Approche systématique pour tester les capacités.
  • Utilise des commandes bash simples et reproductibles.
  • Couvre une large gamme d'intégrations système (Messages, Calendrier, Contacts, etc.).
  • Évite les essais-erreurs en fournissant un diagnostic clair.

Limites

  • Dépend de scripts et permissions système spécifiques, pouvant varier selon la configuration.
  • Nécessite une configuration préalable (credentials, permissions système).
  • Certaines vérifications peuvent renvoyer des messages d'erreur incomplets.
Quand l'utiliser

Utilisez cette compétence lorsque vous souhaitez confirmer qu'une action est possible (ex. envoyer un iMessage, accéder aux contacts) avant de l'exécuter.

Quand l'éviter

Évitez de l'utiliser si les permissions et configurations sont déjà connues comme fonctionnelles, ou si l'action est triviale et ne nécessite pas de vérification.

Analyse de sécurité

Sûr
Score qualité85/100

This skill only provides diagnostic commands (pgrep, osascript, ls, grep) to check system capabilities. It does not execute destructive actions, exfiltrate data, or use obfuscated payloads. The declared tools (Bash, Read, Grep, Glob) are used for harmless introspection.

Aucun point d'attention détecté

Exemples

Check iMessage capability
Can I send an iMessage from this environment? Check what's blocking it.
Permission troubleshooting for calendar
Why can't I read the calendar? Check my capabilities and diagnose any blockers.
Overall capability inventory
Show me what actions I'm currently able to perform and what permissions are missing.

name: capability description: Check if a specific action is possible and what might be blocking it. Use when asking if you can do something, checking permissions, verifying a capability exists, or troubleshooting why something isn't working. Trigger words: can I, capability, able to, permission, possible, how do I. context: fork allowed-tools:

  • Bash
  • Read
  • Grep
  • Glob

Capability Check

Verify if a specific action is possible and diagnose any blockers.

Capability Inventory

Full capabilities documentation: ~/.claude-mind/self/inventory.md

Access Patterns

# Read full inventory (comprehensive reference)
cat ~/.claude-mind/self/inventory.md

# Search for specific capability
grep -ni "search term" ~/.claude-mind/self/inventory.md

# List all sections
grep "^## " ~/.claude-mind/self/inventory.md

Quick Capability Matrix

| Capability | Method | Requires | |------------|--------|----------| | Send iMessage | AppleScript via Samara | Samara running, Automation permission | | Send image | send-image script | Pictures folder workaround | | Read calendar | AppleScript | Calendar permission | | Write calendar | AppleScript | Calendar permission | | Read contacts | AppleScript | Contacts permission | | Read/write notes | AppleScript | Notes permission | | Send email | AppleScript | Mail permission | | Post to Bluesky | bluesky-post script | Credentials in config | | Browse web | Playwright MCP | MCP server running | | Take screenshot | screenshot script | Screen recording permission | | Read Messages DB | Direct file access | Full Disk Access | | Run shell commands | Bash | Always available | | Read/write files | Direct | Always available |

Checking Specific Capabilities

Messaging

pgrep -q Samara && echo "Samara: OK" || echo "Samara: Not running"
~/.claude-mind/system/bin/message "test" --dry-run 2>/dev/null

Calendar

osascript -e 'tell application "Calendar" to get name of calendars' 2>&1

Contacts

osascript -e 'tell application "Contacts" to get name of first person' 2>&1

Notes

osascript -e 'tell application "Notes" to get name of first note' 2>&1

Mail

osascript -e 'tell application "Mail" to get name of first account' 2>&1

Bluesky

grep -q "bluesky" ~/.claude-mind/system/config.json && echo "Bluesky: Configured" || echo "Bluesky: Not configured"

Full Disk Access

ls ~/Library/Messages/chat.db 2>/dev/null && echo "FDA: OK" || echo "FDA: Missing"

Troubleshooting Flow

  1. Identify the capability: What action is being attempted?

  2. Check prerequisites:

    • Is the required app/service running?
    • Are permissions granted?
    • Is configuration present?
  3. Test minimally: Run simplest possible version of the action

  4. Check logs: Look for error messages

log show --predicate 'process == "osascript"' --last 2m
  1. Report findings: What works, what doesn't, what to fix

Common Blockers

  • "Not authorized to send Apple events": Missing Automation permission
  • "Operation not permitted": Missing FDA or specific permission
  • "Application isn't running": Need to launch the app first
  • "No such file": Script or config missing
Skills similaires