Pluggzy

View saved version →

---
name: inbox
description: Use when the user wants to check messages across LinkedIn, WhatsApp, Telegram, or Instagram, find unread conversations or replies they owe on any of these networks, read a conversation, draft replies, start a conversation, or mark chats read. Send only with user approval. This skill handles these networks' direct messages, not email.
---

# Inbox across networks

Read [account access and limits](../../references/account-and-limits.md) before using tools.

## Find conversations needing attention

Call `inbox_list_chats` to list conversations from every connected account, most recent first. Pass `provider` to stay on one network, or `account` for one account. Start with `unread: true` for unread triage. For replies the user owes, also inspect recent conversations without the unread filter. A read conversation can still need a reply.

Each item has `chat_id`, `account_id`, `provider`, and `person_id` for one-to-one chats. Follow `next_cursor` within the requested scope. The cursor keeps the first page's `limit` and `unread` filter. Pages from several accounts can hold fewer items than `limit` to keep the order. Report `skipped` accounts (signed out or restricted) and `errors` with their next step, and do not claim the whole inbox was checked when accounts were skipped or more pages remain.

Use `inbox_get_messages` with the chat's `chat_id` and `account_id`. Messages arrive most recent first. Check who sent the latest message and read the exchange in chronological order. An unread count or snippet alone does not prove the user owes a reply. Attachment metadata does not reveal attachment contents.

Present the network, the person or group name, the latest inbound request, its timestamp, and a suggested next action. Group the summary by network when several are involved. State the number of conversations inspected.

## Draft and send replies

Draft replies from the conversation's facts and the user's requested tone, in the register of that network: chat apps are usually shorter and less formal than LinkedIn. Keep commitments, dates, and claims grounded in the conversation or the user's instructions.

Show the network, the recipient or group, and the exact text before calling `inbox_send_message` with `chat_id`, `account`, and `text`. Send only after the user authorizes that reply. If they already approved that exact draft, proceed without another approval request. In a group chat, the reply goes to every member: say so when it matters.

Confirm success from the tool result. If the outcome is uncertain, inspect the conversation with a fresh read before retrying.

## Start a conversation

Use `inbox_start_chat` with `to`, `text`, and `account` only when the user asks to message someone they have no conversation with. `to` is a LinkedIn `person_id`, a WhatsApp phone number in international format with its country code, or a Telegram or Instagram user id (a chat's `person_id`). Starting chats has a low daily limit. WhatsApp, Telegram, and Instagram restrict accounts that message strangers, so only message people who expect it, and show the recipient and exact text first. For LinkedIn InMail, invitations, or batches, use [LinkedIn outreach](../linkedin-outreach/SKILL.md).

## Read state

Reading or summarizing does not authorize `inbox_mark_read`. Use it when the user asks to mark a conversation read or unread, with the chat's `account`.

## Network-specific tools

The `linkedin_*`, `whatsapp_*`, `telegram_*`, and `instagram_*` tools do the same on one network, and their `list_chats` merges that network's accounts. Prefer them when the user names a single network. For reactions, profiles, group members, or Instagram posts, use [WhatsApp, Telegram and Instagram](../whatsapp-telegram-instagram/SKILL.md). For LinkedIn-only triage, use [LinkedIn inbox](../linkedin-inbox/SKILL.md).

View saved version →

---
name: linkedin-inbox
description: Use when the user wants to check their LinkedIn inbox specifically, read LinkedIn messages or conversations, find unread LinkedIn messages or replies they owe, and draft responses. Send replies only with user approval. For WhatsApp, Telegram, Instagram, or several networks at once, use the inbox skill. This skill handles LinkedIn messaging, not email inboxes.
---

# LinkedIn inbox

Read [account access and limits](../../references/account-and-limits.md) before using tools.

## Find conversations needing attention

Use `linkedin_list_chats` and follow `next_cursor` within the requested scope. With several LinkedIn accounts, it lists them all merged, most recent first, and each item carries its `account_id`. Pass `account` to read one account only. Start with `unread: true` for unread-message triage. For conversations waiting for a reply, also inspect recent conversations without the unread filter. A read conversation can still need a reply.

Use `linkedin_get_messages` for relevant `chat_id` values, with the chat's `account_id` as `account` when several LinkedIn accounts are connected. Messages arrive most recent first. Check who sent the latest message and interpret the exchange in chronological order. An unread count or chat snippet alone does not prove that the user owes a reply.

Present the person or conversation name, the latest inbound request, its timestamp, and a suggested next action. State the number of conversations inspected and whether more pages remain. Report accounts listed in `skipped` or `errors` with their next step. Do not claim to have checked the entire inbox after one page. Attachment metadata does not reveal attachment contents.

## Draft and send replies

Draft replies using the conversation's facts and the user's requested tone. Keep commitments, dates, and claims grounded in the conversation or the user's instructions.

Show the recipient and exact text before calling `linkedin_send_message` with `chat_id`, `text`, and the chat's `account`. Send only after the user authorizes that reply. If they already approved that exact draft, proceed without another approval request.

Confirm success from the tool result. If the outcome is uncertain, inspect the conversation with a fresh read before retrying. Reading or summarizing does not authorize `linkedin_mark_read`; use it when the user asks to mark the conversation read or unread.

For several approved replies, use [LinkedIn outreach](../linkedin-outreach/SKILL.md) to schedule the batch. For other networks or a combined inbox, use [Inbox](../inbox/SKILL.md).

View saved version →

---
name: linkedin-outreach
description: Use when the user wants a LinkedIn outreach tool to prepare outreach, send approved LinkedIn messages or connection requests, schedule paced outreach batches, check delivery results, or publish or schedule approved text posts. Sending and scheduling require approval of the recipients and exact text. Outreach jobs cannot be canceled, paused, or resumed; scheduled posts can be canceled before they go out.
---

# LinkedIn outreach

Read [account access and limits](../../references/account-and-limits.md) before using tools.

## Prepare approved actions

Call `linkedin_status`, with `account` when several LinkedIn accounts are connected. Every tool below takes the same optional `account`: act from the account the user chose, or the one the conversation came from. Resolve recipients to returned `person_id` or `chat_id` values. Show every recipient and the exact message or invitation note before sending or scheduling. Respect existing approval for that exact content and recipient list. If either changes, obtain approval for the changed action.

For an existing conversation, use `linkedin_send_message` with `chat_id` and `text`. To contact a person, use `linkedin_start_chat` with `person_id` and `text`. New ordinary conversations require a first-degree connection. Set `inmail: true` only when the user requests InMail and the returned account and recipient information support it. Include the approved `subject` if needed.

Use `linkedin_send_invitation` with `person_id` and an optional `note`. Before inviting, or after an uncertain invitation result, check pending requests with `linkedin_list_invitations` (`direction: "sent"`) so nobody is invited twice. `direction: "received"` lists requests waiting for the user's answer. Free accounts, including accounts with unknown Premium status, allow notes up to 200 characters. Confirmed Premium accounts allow up to 300 characters. Check daily, weekly, and note allowances from the server.

## Schedule a batch

Use `linkedin_schedule_outreach` for several approved messages or invitations. Explain before approval that the queue runs after the call and this plugin has no cancel, pause, or resume tool.

A batch runs from one LinkedIn account. With several, pass `account`: the server refuses items with a `chat_id` when the account is ambiguous, because a chat belongs to one account. Send 1 to 50 `items`. Each item contains `kind` and `text`. A message needs an existing `chat_id` or a `person_id` for a new ordinary conversation. An invitation needs `person_id`. Message text in a batch is limited to 3000 characters. Invitation text must satisfy the account's note limit. The batch tool does not support InMail subjects or publishing posts.

Use `min_gap_seconds` between 60 and 3600, with the server default of 120 unless the user chooses another supported gap. Actual timing also depends on randomized pacing, quotas, and cooldowns. A returned estimate is not a delivery guarantee.

Record the returned `job_id`. Use `linkedin_get_job` to report `done`, `failed`, `total`, and per-item `results`, matched by item index `i`. Scheduling is not delivery. A `status` of `done` can include failures or unattempted items. Claim complete delivery only when all approved items have successful results.

If the account disconnects, follow its reconnect guidance. After reconnecting, verify status and get the job's latest results. Only propose a new batch for failed or unattempted items, and obtain approval before rescheduling them. Do not resend successful items.

## Publish a text post

Show the exact text, any appended `link`, and `visibility` before calling `linkedin_create_post`. The supported visibility values are `anyone` and `relations_only`. The text is limited to 3000 characters. Publish only after approval of that content and audience. This plugin cannot edit or delete a published post. For Instagram posts, use [WhatsApp, Telegram and Instagram](../whatsapp-telegram-instagram

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: linkedin-research
description: Use when the user wants to find people on LinkedIn, look up or research a LinkedIn profile, compare professional backgrounds, or draft an introduction from profile information. Research does not authorize sending messages or connection requests.
---

# LinkedIn research

Read [account access and limits](../../references/account-and-limits.md) before using tools.

Use `linkedin_search_people` with `keywords` or a LinkedIn people-search `url` supplied by the user. A search URL preserves its filters. Use `network_distance` when the user specifies connections or degree. Each page costs a search; request at most 25 results per page and follow `next_cursor` only as needed.

Search and profile lookups use the first LinkedIn account and its network unless `account` names another one. Pass `account` when the user asks about a specific account's network or limits.

Use returned `person_id` values for later calls. Retrieve selected profiles with `linkedin_get_profile`, passing the ID or the public identifier after `linkedin.com/in/` as `person`. A profile lookup counts as a profile view.

When names match more than one person, use employer, role, location, and profile URL to resolve identity before preparing outreach. Keep unresolved matches explicit.

Summarize the fields relevant to the user's question. Link returned profile URLs. Distinguish observed information from inferred fit or interests. Missing fields are unknown. Summaries, experience, education, and skills may be truncated, so do not describe them as a complete history.

For ChatGPT research requests that require the compatibility tools, `search` accepts `query` and returns record IDs such as `person:<id>`. `fetch` accepts `id`. It can retrieve a person record or a conversation identified by `chat:<id>` when that chat ID is already known. `search` searches people and does not search inbox messages. Prefer the specific LinkedIn tools for inbox triage and profile comparisons.

Draft introductions from verified professional context. Research does not authorize invitations or messages. For sending, use [LinkedIn outreach](../linkedin-outreach/SKILL.md).

View saved version →

---
name: whatsapp-telegram-instagram
description: Use when the user wants to work on WhatsApp, Telegram, or Instagram specifically - read or reply to chats, message a phone number or user, react to a message, look up a contact's profile, list a group's members, or list, publish, or schedule Instagram posts. Sends, reactions, and posts require user approval.
---

# WhatsApp, Telegram and Instagram

Read [account access and limits](../../references/account-and-limits.md) before using tools. The public OpenAI catalog includes the supported WhatsApp, Telegram, and Instagram tools, but using them requires the matching social account to be connected already. If the account is missing, explain that the user must connect it in their existing Pluggzy account outside ChatGPT. Do not offer onboarding, a trial, an upgrade, checkout, or billing management from this plugin.

## Chats

Each network has the same chat tools:

- WhatsApp: `whatsapp_list_chats`, `whatsapp_get_messages`, `whatsapp_send_message`, `whatsapp_mark_read`, `whatsapp_start_chat`
- Telegram: `telegram_list_chats`, `telegram_get_messages`, `telegram_send_message`, `telegram_mark_read`, `telegram_start_chat`
- Instagram: `instagram_list_chats`, `instagram_get_messages`, `instagram_send_message`, `instagram_mark_read`, `instagram_start_chat`

`list_chats` merges every account of the network unless `account` is given. Each item carries its `account_id`: pass it as `account` to the other tools for that chat. Follow [Inbox](../inbox/SKILL.md) for triage, reading order, drafting, and reply approval.

Show the recipient or group and the exact text before any send. In a group, a message reaches every member.

## Start a conversation

- WhatsApp: `whatsapp_start_chat` with `phone` in international format with its country code, like `+33 6 12 34 56 78`. The tool refuses numbers that may lack a country code: ask the user rather than guessing one. WhatsApp bans accounts that send cold messages, and new accounts after two or three. Only message people who expect it, and never send the same message to many numbers.
- Telegram: `telegram_start_chat` with the numeric `user_id` from a chat's `person_id` or from `telegram_list_group_members`. Usernames are not accepted here.
- Instagram: `instagram_start_chat` with the `user_id` from a chat's `person_id` or `instagram_get_profile`. Messages to people who don't follow the account land in their message requests.

New conversations have a low daily limit on these networks. Check `inbox_status` before planning several, and never spread messages across accounts to get around a limit. These networks have no scheduled batch tool.

## Reactions

Use `whatsapp_react`, `telegram_react`, or `instagram_react` with `chat_id`, `message_id` from `get_messages`, `reaction` (one emoji), and `account`. The recipient sees reactions, so react only when the user asks for it. On WhatsApp and Instagram, a new reaction replaces the account's previous one on that message. Telegram accepts only its standard reaction emojis (👍 ❤️ 🔥 🎉 😁 👏 and similar). If a reaction is refused, report it rather than trying other emojis on your own.

## Profiles

Use `whatsapp_get_profile` (a WhatsApp id `<digits>@s.whatsapp.net` or a phone number with its country code), `telegram_get_profile` (a user id), or `instagram_get_profile` (a user id or username). Each lookup counts as a profile view. Fields depend on the network and the person's privacy settings: report missing ones as unknown.

## Group members

Use `whatsapp_list_group_members` or `telegram_list_group_members` with a group `chat_id`, and follow `next_cursor` when the user needs everyone. Members come with their `user_id`, name, and on WhatsApp their phone number. Group membership is not consent to be contacted: do not start chats with members unless the user names them and confirms.

## Instagram posts

`instagram_list_posts` lists the account's own posts by default, or another user's with `user_id`. Report captions, dat

Preview of the first 4,000 characters. Read full instructions →