.claude/skills/capability/SKILL.md
--- 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 Invento
npx skillsauth add claudeaceae/samara-main .claude/skills/capabilityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Verify if a specific action is possible and diagnose any blockers.
Full capabilities documentation: ~/.claude-mind/self/inventory.md
# 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
| 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 (legacy) |
| Shared workspace notes | Filesystem | ~/.claude-mind/shared/ (preferred) |
| 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 |
launchctl list co.organelle.Samara 2>/dev/null | grep -q 'PID' && echo "Samara: OK" || echo "Samara: Not running"
~/.claude-mind/system/bin/message "test" --dry-run 2>/dev/null
osascript -e 'tell application "Calendar" to get name of calendars' 2>&1
osascript -e 'tell application "Contacts" to get name of first person' 2>&1
ls ~/.claude-mind/shared 2>/dev/null
osascript -e 'tell application "Notes" to get name of first note' 2>&1
osascript -e 'tell application "Mail" to get name of first account' 2>&1
grep -q "bluesky" ~/.claude-mind/system/config.json && echo "Bluesky: Configured" || echo "Bluesky: Not configured"
ls ~/Library/Messages/chat.db 2>/dev/null && echo "FDA: OK" || echo "FDA: Missing"
Identify the capability: What action is being attempted?
Check prerequisites:
Test minimally: Run simplest possible version of the action
Check logs: Look for error messages
log show --predicate 'process == "osascript"' --last 2m
development
# /webhook --- name: webhook description: Manage webhook sources - list, add, test, and view incoming events context: fork triggers: - webhook - add webhook - create webhook - webhook setup - incoming webhooks --- Manage the webhook receiver system. Use this skill to add new webhook sources, test existing ones, and view incoming events. ## What You Can Do 1. **List sources** - Show all registered webhook sources 2. **Add source** - Create a new webhook source with secure secret 3.
testing
Check crypto wallet balances, transaction history, and addresses
testing
# /voice-call - FaceTime Voice Calling Place and receive FaceTime Audio calls with live transcription and voice/text responses. ## Quick Start ```bash # Full voice conversation (responds via FaceTime audio) ~/.claude-mind/system/bin/voice-call --voice-response # Call with text responses (via iMessage) ~/.claude-mind/system/bin/voice-call --text-response # Call a specific number ~/.claude-mind/system/bin/voice-call +15551234567 --voice-response ``` ## Prerequisites Run `audio-setup --check
tools
--- name: sync description: Check for drift between repo and running system. Use when checking if scripts or Samara are out of sync, verifying system integrity, or before/after rebuilds. Trigger words: sync, organism sync, check drift, system drift, repo sync. context: fork allowed-tools: - Bash - Read - Grep --- # Sync Skill Check for drift between the repo and running system, and optionally fix it. ## What This Does Runs the `sync-organism` script to detect differences between: - `~/