From messaging-collaboration-skills
Plan iOS and iPadOS default messaging, calling, dialer, and carrier messaging app roles while separating documented system integrations from an app-owned macOS companion implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/messaging-collaboration-skills:default-communication-app-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Choose the documented default-app role before building routing, UI, account, or
Choose the documented default-app role before building routing, UI, account, or transport logic. A default messaging app, default calling app, default dialer, and default carrier messaging app are separate products with different system contracts.
im: URL handling. It receives a recipient address, not
arbitrary message body content; provide sms: fallback only when the app
cannot handle the recipient.voip background mode, and CallKit or
LiveCommunicationKit. Handle tel: routing and offer an explicit system
fallback when VoIP cannot complete.Do not claim a corresponding documented macOS default messaging or calling-app role without current Apple evidence. When building for macOS, implement an app-owned messaging/calling client, account setup, local notifications, contacts/share integrations where available, and companion continuity behavior. That client must not imply access to Apple Messages, Phone, carrier SMS/MMS/RCS, or system call routing.
Validate default-role selection, URL routing, unavailable-recipient and transport fallback, entitlement/provisioning state, privacy disclosures, physical-device behavior, regional availability, and App Review evidence. Keep each role's capability inventory in the app project; do not silently enable an entitlement because another communication role needs it.
Creates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.
npx claudepluginhub gaelic-ghost/socket --plugin messaging-collaboration-skills