Przejdź do treści
Biblioteka skilli
Dokumenty i biuro · Pisanie

plain-email

/plain-email

Sprawdza albo przepisuje e-mail lub krótką wiadomość tak, by odbiorca w dwóch zdaniach wiedział, czego oczekujesz.

Repozytorium
say-it-plainly ↗
Licencja
MIT
Ostatnia zmiana repozytorium
29.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 29.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Sprawdza albo przepisuje e-mail lub krótką wiadomość tak, by odbiorca w dwóch zdaniach wiedział, czego oczekujesz.

Oryginalny opis (EN)

Review or rewrite an email or chat message so the reader knows what you want within two lines. Use for emails, replies and short messages.

Jak działa

  1. The rules
  2. Emails and messages
  3. Review
  4. Rewrite
  5. House formatting
  6. What you must not do
Sekcje z nagłówków SKILL.md, w oryginale · 86 linii, 1 056 słów
Podgląd SKILL.md
---
name: plain-email
description: Review or rewrite an email or chat message so the reader knows what you want within two lines. Use for emails, replies and short messages.
---

# Plain Email

You do not need to install anything to try this once. Copy this whole file, paste it into any AI chat, then paste your text underneath. The lines between the dashes at the very top are just this file's label. Leave them in.

This skill reviews or rewrites an email or short message so the reader knows what is wanted from them, and by when, within the first two lines.

## The rules

These apply to every kind of writing.

1. **Write for one reader.** Picture the person. Say it the way you would say it to them across a desk.
2. **Put the point first.** Start with what the reader needs most, then give the support.
3. **One idea to a sentence.** Break the long sentence. A reader should not have to hold a clause open while they wait for its end.
4. **Use the short, everyday word.** "Use", not "utilise". "Help", not "facilitate". Jargon only when your reader uses it themselves.
5. **Cut what does no work.** If a sentence still works without a word, cut the word. If the piece still works without a sentence, cut the sentence.
6. **Name who did it.** Put a person in the sentence. "I sent the proposal", not "the proposal was sent".
7. **Drop stock phrases and filler.** Openers and sign-offs that say nothing, and metaphors you have read so often you no longer see them.
8. **Be specific enough to be checked.** Name the person, the number, the date. If you do not know, say what you do not know. Never invent a detail to fill a gap.
9. **Keep real uncertainty and cut the rest.** A hedge that honestly marks what you are unsure of stays. A hedge that hides a claim goes.
10. **Say how two things relate.** Use "because", "although", "so" or "once". Do not leave the link to the rhythm of two sentences side by side.
11. **Claim no more than you know.** Do not turn an impression into a result, a reading into a fact, or two things that happened together into one causing the other.
12. **Break any rule before you write something clumsy.**

## Emails and messages

The reader is busy and may read this on a phone between other things. They should know what you want from them within two lines.

- **One ask.** If you need two things, send two messages, or say which one matters most. Put the ask in the first two lines.
- **The subject line says what you need.** "Can you confirm the 14th by Friday?" beats "Quick question".
- **Answer first when you are replying.** Give the answer, then the reason.
- **Say when, not "soon".** Name the day, the time or the date.
- **Short paragraphs, one idea each.** Lists only for a real list of items.
- **Do not apologise for writing,** and do not thank someone in advance for something they have not done.
- **Cut the opener and the closer** if they only fill space: "Hope you're well", "Just checking in", "Please don't hesitate to".
- **Keep it short.** Most emails work in under 150 words. If yours is longer, check that every paragraph earns its place.

## Review

Use this when the person wants a critique and wants their text left alone.

Reply with these four parts, in this order:

1. **Does it do its job?** Two sentences: who the reader is, and whether this text gives them what they need.
2. **What to change.** The seven changes that would help the reader most, most important first. For each one, quote the exact words, say in one sentence what is wrong, and say what to do instead. Do not rewrite the text.
3. **What already works.** One or two things to keep.
4. **What I could not tell.** Any facts you would need from the writer to judge a sentence. Ask for them. Do not guess.

If the text is already clear, say so and stop. Do not invent faults to look useful.

## Rewrite

Use this when the person wants an edited version.

Reply with the rewritten text first, then three short parts:

1. **What I changed.** A short list.
2. **What I kept on purpose.** Hedges that mark real uncertainty, figures, names, and any sentence that was rough but sounded like the writer.
3. **What I need from you.** Anything missing, written as a question. Never fill a gap with an invented fact, number, name or date.

A rewrite changes how the text reads and leaves what it claims exactly where it was. After you rewrite, check that the new text keeps the original's scope, certainty, emphasis and cause. If a clearer sentence would claim more than the original did, keep the weaker claim. Keep the writer's voice. Smoothing a rough sentence into a bland one is not an improvement.

If the person does not say which mode, ask once: "Review it, or rewrite it?"

## House formatting

These are the author's own preferences, not rules of good writing. Apply them only if the person asks for "house formatting" or asks for these rules by name. Otherwise leave their formatting alone.

- No em dashes. Use a comma, a colon or a full stop.
- Straight quotes and apostrophes only. No curly ones.
- Dates with an ordinal suffix, day first: 21st May, 3rd July.
- Spell out numbers one to nine in prose. Use numerals for 10 and above.
- Percentages in numerals: 95%, not ninety-five per cent.
- Currency in full figures: £18,000, not £18k or eighteen thousand pounds.
- No emojis in writing for customers.
- No headings inside an email.
- Sign off an email on two lines: "Best," then the name.

## What you must not do

- Never invent a fact, number, name, date or quote. If something is missing, ask for it.
- Never make the writing sound more certain, more complete or more important than the original did.
- Do not praise the writer or pad your reply. Follow these rules in your own reply too.
- If the text is not what this skill is for, say so in one sentence, then use the general rules above.
- If the text is too thin to judge, ask for what you need and stop.

Wersje

W bazie nie ma innych skilli o nazwie plain-email.

Migawka bazy z 13.11.2026 · wersja paczki 3aeb146464d5 (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

  • 100email
    Planuje ważny e-mail lub długą wiadomość przed napisaniem: co odbiorca ma zrobić, kto to czyta, ton i temat, a potem sprawdza go na odbiorcach.
  • 100rewrite
    Przepisuje jedną wiadomość sprzedażową, skrypt rozmowy lub wiadomość na LinkedIn i sprawdza ją przed zapisaniem.
  • 100email-drafter
    Pisze e-maile, na które ktoś odpowie: prośba w dwóch pierwszych zdaniach, kontekst dalej, jeden jasny kolejny krok i ton dopasowany do relacji.
  • 100draft-message
    Pisze wiadomość, e-mail lub odpowiedź w głosie użytkownika i pokazuje ją do akceptacji przed jakąkolwiek wysyłką.
  • 90plain-report
    Sprawdza albo przepisuje raport lub propozycję tak, by od razu było widać ustalenie i decyzję, której potrzebuje czytelnik.
  • 100anti-ai-slop-writing
    Pisze i przepisuje teksty dla czytelników, np. e-maile, posty, raporty i opisy zmian, tak by nie miały śladów pisania przez AI.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.