Menu

Individual skill

pachca-messaging

Писать в Пачку: разметка, упоминания, куда писать (тред, ответ с цитатой, личный чат), черновик, который отправит сотрудник, отложенные и регулярные сообщения в чат, файлы, пересылка, реакции, закрепление, «Важное», правка, удаление, поиск нужного сообщения, когда сначала спросить, лимиты. Когда: «напиши в чат», «отправь сообщение», «ответь в треде», «напиши в личку», «упомяни», «подготовь черновик, я отправлю сам», «агент готовит черновик, сотрудник отправляет», «запланируй сообщение», «напоминай в канал каждый понедельник», «отправь отчёт файлом .md», «приложи файл», «перешли сообщение», «поставь реакцию», «закрепи сообщение», «отметь как важное», «исправь сообщение», "send a message", "reply in the thread", "DM someone", "draft for me to send", "schedule a message", "attach a file", "forward a message", "pin". Not for: search or summaries as the goal, a reminder for an employee → pachca-search; buttons, forms, clicks → pachca-bots; an AI agent as a bot → pachca-ai-agent; uploads from code → pachca-api.

plugins/pachca/skills/pachca-messaging/SKILL.md

Read pinned source

Source commit 542014c04cf308d45040194e9290551570a1aee8

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
11
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Writing in Pachca

## When to use

Any time you put text into Pachca for the user: a message, a thread comment, a direct message, a draft, a scheduled message, a file, a reaction, a pin or a «Важное» mark, or an edit or deletion of a message. The tool descriptions, `pachca --help` and the API pages are the reference for arguments. This skill covers what they do not say: where to post, when to ask first, and what breaks.

Access paths: prefer the MCP tools (`pachca_send_message`, `pachca_create_draft`, …). In a terminal the CLI does the same (`pachca messages create`, `pachca drafts create`, `pachca upload`). With neither, call the REST API directly. All three call the same methods with the same permissions.

## Key concepts

- **Addressing.** A message goes to `entity_type` + `entity_id`. `discussion` (the default) takes the `chat_id` of any chat, `thread` takes the thread `id`, `user` takes an employee's user id.
- **A thread has two ids.** Its `id` goes with `entity_type: "thread"`. Its `chat_id` goes with `discussion`, like any chat. The parent message id is never the thread id.
- **Sender.** The message goes out under the token owner's name. With a bot token it carries the «Бот» badge. A message sent after a browser login, through MCP or through the CLI (`pachca auth login`), shows a badge on the avatar, «Отправлено через …» with the program's name (with its icon when Pachca knows one). One sent with a personal token looks exactly as if the employee typed it. Write in the voice of the account it goes out under.
- **Action labels.** MCP marks sending, reacting, pinning and adding to «Важное» as a change. Editing, deleting, unpinning, removing a reaction and removing from «Важное» are marked as a dangerous change. The program asks for confirmation based on these labels, so a clear request needs no question from you. The cases where you ask first are under "When to ask first".