Individual skill
summarize-thread
Пересказать тред Пачки целиком: контекст, решения, открытые вопросы и поручения, со ссылками. Когда: «перескажи тред», «о чём договорились в треде», «кратко по треду», «что поправить по треду», «разбери замечания в треде», «собери из треда, что нашли», «убедись, что всё по треду поправили», "summarize this thread", "what was decided in the thread", "what feedback is in the thread". Not for: turning action items into reminders, or a digest of chats for a period → pachca-search.
plugins/pachca/skills/summarize-thread/SKILL.md
Source commit 542014c04cf308d45040194e9290551570a1aee8
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- 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
SKILL.mdcore · 5,524 bytesagents/openai.yamlasset · 152 bytes
Read excerpt
# Summarize a Pachca thread
Summarize the Pachca threads the user gave with the command: one or more thread links, message links or thread ids. If there is none, ask for it. With several, summarize each thread separately, in the order given. The user may add a window («с понедельника», «с моего последнего сообщения») and a question to answer («ответили ли мне», «что нужно поправить»).
Follow the `pachca-search` skill and its thread procedure. A link can name the thread itself (`thread_id`), the message the thread hangs under (`thread_message_id`), or a single message (`sidebar_message` or `message`); that message can be the one the thread hangs under, a comment inside the thread or a message with no thread. For a thread id or a `thread_id` link, `pachca_get_thread` gives the thread's `chat_id` and `message_id`. Otherwise find the thread chat with the "Find the thread chat" table in the skill's `references/threads.md`. A message with `thread` is the parent itself: its `id` is the thread's `message_id`. A comment inside a thread has no `thread`: its own `chat_id` is the thread chat, and its `entity_id` is the thread id, so `pachca_get_thread` by `entity_id` gives the thread's `message_id`. If the message has no thread (`thread` is `null` and its `entity_type` is not `thread`), say so and do not create one. Read the thread chat by its `chat_id`, not the parent chat.
1. Read every message of the thread (`pachca_list_chat_messages` by the thread's `chat_id`, all pages, oldest first: pass `sort=id` together with `order=asc` on every call, cursor pages included, because `order` alone is ignored; or read newest first and reverse; check the order by `created_at`) and the parent message (`pachca_get_message` by the thread's `message_id`). A standalone thread has no parent: its `message_id` is `null`, so skip that call.
2. Resolve each author once (`pachca_get_user`) when the response does not name them. A `404` means the author was deleted or is hidden from you: refer to them by `user_id`, do not guess a name from the text, and keep their messages in the summary.
3. Answer in the user's language:
- **Context**: what the thread is about, in two or three sentences;
- **Decisions**: what was agreed, who agreed, link to the message;
- **Open questions**: what is still unanswered and who should answer;
- **Action items**: what, who, by when, if the thread says so.