communication
/communication
Pisze lub przepisuje wiadomość (mail, czat, ofertę, ogłoszenie) pod konkretnego odbiorcę, z zachowaniem wszystkich faktów.
- Autor
- DomynAI ↗
- Repozytorium
- domyn-agents ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Pisze lub przepisuje wiadomość (mail, czat, ofertę, ogłoszenie) pod konkretnego odbiorcę, z zachowaniem wszystkich faktów.
Wyzwalacze z opisu
Oryginalny opis (EN)
Draft or rewrite a message (email, Slack/Teams, proposal, announcement, reply) for a given audience and register: tone, formality, length. Use for "write / draft / reply to", "rewrite this", "make it shorter / more formal / friendlier", "how do I say". Keeps every key point, fact and commitment intact.
Jak działa
- Core Principles
- Step 1 — Understand the Brief
- Step 2 — Extract What Must Survive
- Step 3 — Write
- Step 4 — Deliver
- Quality Checklist
Podgląd SKILL.md
---
name: communication
version: 1.0.0
description: >
Draft or rewrite a message (email, Slack/Teams, proposal, announcement, reply) for a given audience and register: tone, formality, length. Use for "write / draft / reply to", "rewrite this", "make it shorter / more formal / friendlier", "how do I say". Keeps every key point, fact and commitment intact.
tags: [writing, communication, email, productivity]
---
# Communication Skill
Drafts new messages and rewrites existing ones so they land with their audience: the right tone, formality, length and structure for the channel. Meaning is preserved exactly: every key point, fact, number, name, date and commitment survives the rewrite.
---
## Core Principles
1. **Meaning first, style second.** A rewrite may change every word, but not what the message says, asks or promises.
2. **Write for the reader.** Their role, what they already know, what they need to do after reading.
3. **Lead with the point.** The ask or the news goes first; context follows.
4. **Match the channel.** A Slack message is not a short email, and a proposal is not a long one.
5. **Never invent.** No new facts, figures, deadlines, promises or apologies the user didn't give. Use a visible placeholder (`[date]`, `[name]`) when something is missing.
6. **The user sends it, not you.** Produce the text; never send or post anything.
---
## Step 1 — Understand the Brief
Work out, from the request and any text provided:
| Element | Question | Default if unstated |
|---|---|---|
| **Channel** | email, chat (Slack / Teams), proposal, announcement, reply in a thread | infer from the request or the text |
| **Audience** | who reads it, how senior, how familiar with the topic, internal or external | infer from the text; a colleague if nothing suggests otherwise |
| **Goal** | inform, ask, persuade, decline, apologize, escalate, follow up | infer from the text |
| **Register** | formal, neutral-professional, friendly, casual; direct or diplomatic | neutral-professional |
| **Length** | as short as possible, a target (e.g. "under 100 words"), or "same as the original" | as short as the content allows |
| **Language** | | the language of the request or original text |
Ask **one** question, and only when the answer would change the message substantially — typically the audience or the goal when the text doesn't reveal them. Otherwise write the draft and state the assumptions you made in one line after it, so the user can correct them.
---
## Step 2 — Extract What Must Survive
For a rewrite, before touching the wording, list for yourself everything the original contains that the reader relies on:
- the **ask** or the **news**
- **facts and figures**: numbers, amounts, dates, times, names, links, references, attachments mentioned
- **commitments**: what the sender promises, and by when
- **constraints and caveats**: conditions, exceptions, "only if"
- **deadlines** and next steps
After drafting, check the list against the draft. Anything missing is a bug. If a point seems worth dropping (redundant, off-topic, risky), keep it and tell the user rather than removing it silently.
For a new message, the same list comes from the user's request. If the user gave bullet points, every bullet appears in the message.
---
## Step 3 — Write
**By channel**
- **Email**
- Subject line that says what the email is about or what it needs ("Approval needed: Q3 budget by Friday").
- Opening line with the point or the ask; context after.
- One idea per paragraph; short paragraphs.
- End with the specific next step or ask, and by when.
- Greeting and sign-off in the register's style.
- **Chat (Slack / Teams)**
- One to three short sentences where possible; no subject, no formal sign-off.
- Put the ask in the first line, so it shows in notifications and previews.
- Bullets for more than two items; mention people only when they must act.
- For a thread reply, don't repeat context the thread already has.
- **Proposal / longer document**
- Structure: problem or opportunity → proposal → benefits → cost / effort / risks → the decision or next step asked for.
- Headings and bullets so it can be scanned; key numbers stated once, clearly.
- **Announcement**
- What is changing, when, who is affected, what they need to do, where to ask questions.
**By register**
| Register | Characteristics |
|---|---|
| **Formal** | full sentences, no contractions, no slang or emoji, courteous openings and closings, titles where appropriate |
| **Neutral-professional** | plain and polite, contractions fine, no filler |
| **Friendly** | warm opening, personal touch, still clear and complete |
| **Casual** | conversational, short, emoji only if the user's own style uses them |
| **Direct** | the point in the first sentence, minimal cushioning |
| **Diplomatic** | acknowledge the other side, frame disagreement around shared goals, soften without blurring the message |
**Always**
- Plain words over jargon, unless the audience uses that jargon.
- Active voice; concrete verbs; cut filler ("I just wanted to reach out to…", "Please do not hesitate to…").
- Keep the sender's voice when rewriting: don't turn a direct person into a flowery one unless asked.
**Sensitive messages**
- **Bad news / declining**: state it clearly and early, give the reason briefly, offer what *is* possible.
- **Apology**: acknowledge the specific issue, take the responsibility the user wants to take (no more), say what happens next. Never apologize on the user's behalf for something they didn't ask to apologize for.
- **Pushback / disagreement**: separate the issue from the person, give the reason, propose an alternative.
- **Escalation**: facts, impact, what was already tried, the specific help needed.
- If the draft could create legal, HR or contractual exposure (admitting fault, commitments on pricing, statements about people), point it out to the user in one line.
---
## Step 4 — Deliver
- Give the message **ready to copy**, in a code block or clearly delimited, with the subject line on top for emails.
- Below it, at most a few lines:
- the assumptions you made (audience, register, goal), if the user didn't state them;
- for a rewrite, the main changes in one or two bullets (e.g. "moved the ask to the first line; cut from 240 to 110 words");
- any point you kept but think should be reconsidered, or any placeholder the user must fill.
- Offer alternative versions (shorter, more formal, …) only when the brief is ambiguous or the user asks. One good draft beats three average ones.
- When the user asks for changes, revise the draft rather than starting over, and keep what they didn't ask to change.
---
## Quality Checklist
- [ ] The ask or news is in the first line or two
- [ ] Every key point, fact, number, date, name and commitment from the original or the request is present and unchanged
- [ ] Nothing was invented; missing details are visible placeholders
- [ ] Tone, formality and length match the audience, channel and requested register
- [ ] The next step, and its deadline if any, is explicit
- [ ] The message is ready to copy, and the notes after it are brief
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · DomynAI/domyn-agents | 90 | Apache-2.0 |
| eBay/public-api-migration-skills | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 358bb6a8e2f2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100draft
Pisze w głosie użytkownika e-maile, wiadomości na Slacku i Teams, aktualizacje zespołowe i ogłoszenia według references/voice.md, bez automatycznego wysyłania na zewnątrz. - 100draft-message
Pisze wiadomość, e-mail lub odpowiedź w głosie użytkownika i pokazuje ją do akceptacji przed jakąkolwiek wysyłką. - 100slack-message
Pisze wiadomość na Slacka i kopiuje ją do schowka macOS tak, by po wklejeniu zachowała pogrubienia, kursywę, linki, listy, cytaty i kod. - 100draft-reply
Pisze odpowiedź na e-mail w lokalnym Thunderbirdzie, dopasowaną do tego, jak użytkownik zwykle pisze do danej osoby. - 100write-in-my-voice
Pisze lub przepisuje tekst użytkownika w jego głosie: Slack, e-maile, opisy PR, dokumentację, komentarze i notatki decyzyjne. - 90email-replier
Pisze szkic odpowiedzi na e-mail, wiadomość na Slacku lub LinkedIn, gdy użytkownik wkleja treść i prosi o odpowiedź.