
Openloomi Connectors
Openloomi Connectors tools - manage the native 7 messaging integrations and pair with...
Install
npx skills add melandlabs/openloomi --skill openloomi-connectors -g -a claude-code -y- Repository
- melandlabs/openloomi1k
- Category
- Git and review
- Updated
- 1mo ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google Calendar/Drive/Docs, GitHub, Notion, Linear, HubSpot, LinkedIn, Jira, Asana). Triggers: connect platform, integration status, list accounts, disconnect, list-accounts, status, connect, send-reply, native vs composio, 1000+ apps, list connections.
Note: If you haven't downloaded or installed openloomi yet, please refer to Getting Started for installation instructions.
OpenLoomi Connectors Skill
OpenLoomi Connectors handle two directions: pulling Signals in from your authorized platforms and pushing approved Actions back out through the same channel. OpenLoomi ships them through two layers:
- Native (this skill), 7 messaging-platform bots maintained directly by OpenLoomi: Telegram, WhatsApp, iMessage, Lark/Feishu, DingTalk, QQ, and WeChat. The
openloomi-connectorsCLI covers OAuth / app-credential / QR / interactive setup, list, status, disconnect, contact query, and message send for these. - Composio (paired
composioskill), a hosted OAuth broker that authorizes ~1000+ apps including Slack, Discord, X, Gmail, Outlook, Google Calendar/Drive/Docs, GitHub, Notion, Linear, HubSpot, LinkedIn, Jira, Asana. Composio handles "is this user authorised?" and stores the tokens; OpenLoomi's Loop channels consume the events as Signals (see Glossary, Composio / Loop channel).
When the user asks "what am I connected to?" or "list my accounts", run both, list-accounts here and the composio connection listing, and present the union. Keep auth, OAuth, and disconnect flows native to each skill.
This skill does not manage Loop channels, custom decision types, or classifier rules, those are openloomi-loop's job.

