agentsclimarketplace
Sign in

Apple communication workflow

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

Route an Apple communication request to iMessage collaboration, communication notifications, Push to Talk, VoIP calling, default-app, or macOS companion workflows before implementation.From its SKILL.md

Install
npx -y skills add gaelic-ghost/socket --skill apple-communication-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

2.6 KB, 474 tokens by cl100k_base, as published. Nobody here has run it

Apple Communication Workflow

Purpose

Route an Apple communication feature to the documented framework and dedicated workflow that owns it. This is a decision and handoff skill; use apple-dev-skills for implementation, build, and device validation.

Supported Lanes

  • iMessage app and collaboration: a Messages extension creates interactive, app-specific messages; Shared with You connects app-owned collaboration metadata to system surfaces.
  • Communication notification: a Notification Service Extension enriches a mutable remote alert before delivery; communication and Time Sensitive behavior require the applicable capability and intent integration.
  • Push to Talk: PushToTalk owns system controls and channel events while the app owns the backend, audio transport, and channel membership.
  • VoIP calling: CallKit or LiveCommunicationKit owns system call UI and transactions; PushKit handles arrival; AVFAudio owns audio policy; SIP or WebRTC remains a transport decision.
  • Default app: iOS/iPadOS default messaging, calling, dialer, and carrier messaging roles have distinct entitlements, routing, and regional limits.
  • macOS companion: when there is no documented macOS default-app role, build an app-owned client and integrations rather than claiming control of Phone or Messages.

Workflow

  1. Use Xcode DocumentationSearch before planning Apple behavior; confirm framework availability and capability requirements.
  2. Route to exactly one detailed workflow: imessage-app-and-collaboration-workflow, communication-notifications-workflow, push-to-talk-workflow, voip-sip-calling-workflow, or default-communication-app-workflow.
  3. For Phone or Messages MCP evaluation, inspect public source, supported API, requested permissions, storage, authentication, audit behavior, and live test evidence before recommending it. Never authorize or automate personal calls/messages without the user's explicit instruction.
  4. Hand implementation to the relevant Apple framework and Xcode validation workflows.

Output

Return the lane, detailed workflow, documented behavior, required targets/capabilities or privacy keys, data and authorization boundary, validation device requirement, and owning Apple skill. Clearly call out the difference between a documented iOS/iPadOS default-app role and an app-owned macOS companion implementation.

What ships with it

Read from the repository

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

Gives 0 of the 12 instructions most automation workflows skills give in 474 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Search Xcode documentation before planning
  • Route to exactly one workflow
  • Inspect MCP tool evidence before recommending it
  • Hand implementation to framework workflows
  • Call out default-app versus companion differences

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.