Default communication app workflow

Skill gaelic-ghost/socket/plugins/messaging-collaboration-skills/skills/default-communication-app-workflow

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.From its SKILL.md

Install

npx -y skills add gaelic-ghost/socket --skill default-communication-app-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, 535 tokens by cl100k_base, as published. Nobody here has run it

Default Communication App Workflow

Purpose

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.

iOS And iPadOS Roles

Default instant messaging app: requires the Default Messaging App entitlement and im: URL handling. It receives a recipient address, not arbitrary message body content; provide sms: fallback only when the app cannot handle the recipient.
Default calling app: requires real VoIP capability, the Default Calling App entitlement, voip background mode, and CallKit or LiveCommunicationKit. Handle tel: routing and offer an explicit system fallback when VoIP cannot complete.
Default dialer: uses LiveCommunicationKit for cellular conversation initiation and has a separate Default Dialer App entitlement. Treat EU account/device requirements as release gates, not implementation details.
Default carrier messaging app: uses TelephonyMessagingKit for SMS, MMS, and RCS. Keep its entitlement, carrier behavior, user data, and EU availability separate from internet messaging.

macOS Boundary

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.

Validation And Release Gates

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.

References

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.