automating-voice-memos
Automates Apple Voice Memos (Mac Catalyst, no dictionary) via JXA using filesystem/SQLite access and System Events UI scripting. Use when asked to "automate Voice Memos", "export voice recordings", "access Voice Memos database", or "transcribe voice memos".
What this skill does
# Automating Voice Memos (no dictionary, data+UI hybrid)
## Relationship to the macOS automation skill
- This is a standalone skill for Voice Memos automation.
- For setup help, see the `automating-mac-apps` skill for permissions (Full Disk Access, Accessibility) and the ObjC bridge basics.
- Prerequisites: Basic JXA (JavaScript for Automation) knowledge; install via macOS System Preferences > Security & Privacy.
## Core Framing
- **Catalyst App**: Voice Memos is an iOS app adapted for macOS without full macOS APIs, hence no AppleScript dictionary for automation.
- **UI-first**: Prefer UI scripting/keyboard shortcuts for exports to avoid touching the database/container.
- **Data (optional)**: Use data-layer control only if needed (ObjC + sqlite3). This requires broader permissions.
- **Permissions**: Accessibility for UI automation; Full Disk Access only if you read/write the container/DB.
## Workflow (default)
1) UI-first (no FDA): export via menu/shortcut to a folder you control.
2) Optional data path: resolve storage paths; query CloudRecordings.db (Apple epoch +978307200) only if required.
3) For UI actions (recording/export), drive the app with System Events (shortcuts preferred over clicks).
4) For editing, prefer external tools (ffmpeg) after export; avoid writing directly into the container unless you accept FDA.
## Quickstart (UI-only export; no Full Disk Access)
- Open Voice Memos and select a recording.
- Export/share UI: the Share sheet can send audio to Notes/other apps (no direct File > Export).
- Transcript copy (UI-only, no FDA):
- Run: `osascript skills/automating-voice-memos/scripts/copy_transcript_to_file.applescript "/path/to/output.txt"`
- Defaults: Desktop/voice-memo-transcript.txt if no arg.
- Shows transcript (if available), selects all, copies, and writes to the target file via clipboard.
## Permissions
- **Accessibility**: System Settings > Privacy & Security > Accessibility > Enable for System Events and your automation app (Terminal/Python/Script Editor).
- **Full Disk Access**: Only if you read/write the Voice Memos container/DB directly. UI-only exports do not require FDA.
- **Verify**: For UI-only, confirm you can open the Export menu and interact with the save dialog. For data access, verify `${home}/Library/Group Containers/group.com.apple.VoiceMemos.shared/`.
## Validation Checklist
After implementing Voice Memos automation:
- [ ] Verify Accessibility permissions granted for Terminal/Script Editor
- [ ] Confirm Voice Memos app opens and responds to UI scripting
- [ ] Test transcript copy script executes without errors
- [ ] Validate output file contains expected transcript text
- [ ] For data access: verify Full Disk Access and database path exists
## Troubleshooting
- **Permission denied**: Verify Full Disk Access and Accessibility permissions.
- **Database locked**: Close Voice Memos app before querying.
- **File not found**: Check macOS version for correct storage path.
- **UI automation failures**: Ensure Voice Memos is focused and Accessibility is enabled.
## When Not to Use
- For cross-platform audio recording (use ffmpeg or platform-agnostic tools)
- When you need programmatic audio capture (use AVFoundation directly)
- For iOS Voice Memos automation (no API available)
- When Full Disk Access cannot be granted
## What to load
- Start with basics & prerequisites: `automating-voice-memos/references/voice-memos-basics.md` (setup and core concepts).
- UI automation: `automating-voice-memos/references/voice-memos-ui.md` (shortcuts, AX scripting).
- Data access (if needed): `automating-voice-memos/references/voice-memos-data.md` (storage paths, epochs, database schema).
- Recipes: `automating-voice-memos/references/voice-memos-recipes.md` (exports, transcripts, recording control).
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.