Choose platform integration
Skill gaelic-ghost/socket/skills/choose-platform-integration
The Source for macOS Agent Workflows
npx -y skills add gaelic-ghost/socket --skill choose-platform-integrationAssembled 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.
What its author says it does
Copied from the file, not written here
Choose a supported chat, calling, business-messaging, or collaboration integration shape before implementation. Use for Discord, Telegram, Slack, Teams, WhatsApp Business, SMS/MMS/RCS, Google Meet, iMessage collaboration, and Apple VoIP requests.
SKILL.md
2.4 KB, as published. Nobody here has run it
Choose Platform Integration
Purpose
Choose the real platform surface before code, credentials, or a shared abstraction are added. The result is a documented integration shape and one implementation handoff, not a fictional universal bot SDK.
Workflow
- Classify the request as a server bot, workspace app, business messaging agent, meeting add-on, native Messages extension, VoIP calling app, or Mac operator workflow.
- Identify the user, installation, identity, inbound-event, outbound-response, and hosting model.
- Check current official platform docs for availability, policy, review, consent, and SDK lifecycle.
- Select the owning platform workflow and then the owning stack workflow.
- Define the minimum secure event contract before implementation: verified source, acknowledgement deadline, idempotency key, retry behavior, state owner, audit boundary, and human handoff.
Routing
- Discord: installed app and HTTP/Gateway interactions; use
discord-app-workflow. - Telegram: Bot API, webhook or polling, optional Mini App; use
telegram-bot-workflow. - Slack: workspace OAuth app, Events API, interactivity, or Socket Mode; use
slack-app-workflow. - Teams: Teams SDK or Microsoft 365 Agents SDK; use
teams-agent-workflow. - WhatsApp, SMS, MMS, or RCS: business-messaging route; use
whatsapp-business-workfloworsms-mms-rcs-workflow. - Google Meet: add-on, REST conference/artifact integration, or explicitly preview media access; use
google-meet-collaboration-workflow. - Apple: iMessage/Shared with You, communication notifications, Push to Talk, CallKit/LiveCommunicationKit plus PushKit/AVFAudio, documented iOS/iPadOS default roles, or an app-owned macOS client; use
apple-communication-workflow. - Signal: report that no official bot route is supported; do not substitute account automation.
Output
Return the selected surface, reasons, documented constraints, credential and data boundary, implementation owner, validation plan, and rejected alternatives. Stop if the requested platform capability is unsupported or needs a product-policy decision.