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

minto

/minto

Porządkuje myśli i teksty według piramidy Barbary Minto: wniosek na początku, argumenty pogrupowane logicznie, dla maili i raportów.

Repozytorium
minto ↗
Licencja
MIT
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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
4
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.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

Porządkuje myśli i teksty według piramidy Barbary Minto: wniosek na początku, argumenty pogrupowane logicznie, dla maili i raportów.

Wyzwalacze z opisu

mintopyramidSCQMECEanswer firststructure thisdoes my point come across?check the logic
Oryginalny opis (EN)

Applies Barbara Minto's Pyramid Principle to organize ideas and writing, with the conclusion first and supporting arguments grouped logically. Clarifies what you want to say, structures from scratch, reviews drafts and defines problems before a proposal. Use it for emails, proposals, quotes, reports, executive summaries, presentations, theses, papers and classes, or when someone says "minto", "pyramid", "SCQ", "MECE", "answer first", "structure this", "does my point come across?" or "check the logic".

Jak działa

  1. Three rules that override everything else
  2. Language
  3. Choosing the mode
  4. The pyramid rules
  5. The introduction: SCQ
  6. Clarify mode
  7. Structure mode
  8. Review mode
  9. Define the problem mode
  10. Adaptations by type of text
Sekcje z nagłówków SKILL.md, w oryginale · 197 linii, 2 820 słów
Podgląd SKILL.md
---
name: minto
description: Applies Barbara Minto's Pyramid Principle to organize ideas and writing, with the conclusion first and supporting arguments grouped logically. Clarifies what you want to say, structures from scratch, reviews drafts and defines problems before a proposal. Use it for emails, proposals, quotes, reports, executive summaries, presentations, theses, papers and classes, or when someone says "minto", "pyramid", "SCQ", "MECE", "answer first", "structure this", "does my point come across?" or "check the logic".
---

# Minto

Skill based on *The Pyramid Principle: Logic in Writing and Thinking*, by Barbara Minto. The principles are explained in our own words. It is a tribute and is not affiliated with the author.

The core idea: readers understand best when they get the summarizing idea first and then the ideas that support it, grouped and in an order they can recognize. Organizing a text this way also forces clearer thinking.

## Three rules that override everything else

1. **Don't rewrite what you weren't asked to change.** If the user shares a draft just for you to look at, say what you notice and offer to restructure it. The rewritten version does not appear in your reply until they say yes. Showing "how it would look" is already rewriting it without permission.
2. **Don't force the pyramid where the order is the content.** Incident timelines, procedures, manuals, tutorials, meeting minutes, thank-you or apology notes, stories. There, chronological order is the logical order. Say so in one line and offer to polish it as it is.
3. **Don't invent anything.** Every figure, name, date, quote and claim must come from the user's material, including any math done with their numbers. Don't strengthen a claim either ("sales went down" does not become "sales collapsed"). Anything missing is marked like this: `[missing: ...]`.

## Language

Respond in the language of the user's text; if there is no text, in the language of their request. Don't translate their material unless they ask. The method's terms (SCQ, key line) are for thinking, not for printing in the final text.

## Choosing the mode

If the user names a mode, use it. If not:

| Signal | Mode |
|---|---|
| Vague idea, no text ("I need to write to the board about X", "I don't know how to frame this") | **Clarify** |
| Notes, data, a transcript or a request to write something new | **Structure** |
| Existing text + "review", "does it come across?", "what's missing?", "is the logic right?" | **Review** |
| Existing text + "restructure it", "minto this", "rewrite it" | **Structure** on that text |
| A client's or the company's problem before proposing or researching something | **Define the problem** |

If the request mixes signals, pick one, say so in one sentence and move on. Don't explain the skill's mechanics to the user (modes, rules, internal names): talk to them about their text.

## The pyramid rules

1. **One idea at the top.** A single sentence that answers the reader's question. Test: if it takes two different objections to refute it, it's two ideas, not one.
2. **Each idea summarizes the ones below it.** At any level, the idea on top is the synthesis of its group.
3. **Ideas in a group are of the same kind.** Test: the whole group fits under a single plural noun (reasons, steps, problems, risks, parts, options).
4. **Ideas in a group follow an order you can name.** There are only four:
   - **Deductive:** premise, premise, therefore.
   - **Chronological:** steps or a cause-and-effect sequence.
   - **Structural:** parts of a whole (areas, regions, stages of a process).
   - **Comparative or by degree:** from most to least important, large or urgent, with an explicit criterion.
   If you can't say which one was used, the group hasn't been thought through yet.
5. **Question and answer vertically.** Each idea raises a question in the reader (why?, how?, which ones?, how do you know?) and the level below answers exactly that question.
6. **Induction or deduction horizontally.** Induction (several ideas of the same kind that together support the one above) is preferred for the first level, because each point can be understood on its own. Deduction (a chain of premises) works better at lower levels and in short chains; at the top it makes the reader wait until the end to learn what is being asked of them.
7. **No overlaps or gaps (MECE).** Ideas don't repeat each other and, together, answer the whole question. Overlap test: cover one branch. If its content fits in the others and the question is still answered, it was a duplicate.
8. **Logic decides the number, not habit.** The norm is 2 to 5 ideas per group. Don't force three: two reasons that cover the case are worth more than three with filler. If there are more than five, regroup; the mind starts grouping on its own when it receives more than four or five items.

### The kind of idea depends on the reader's question

| Reader's question | Kind of ideas at the first level |
|---|---|
| Why? Is it worth it? Should I approve? | Reasons: what the reader gains, avoids or risks |
| How? What do we do? | Actions or steps, written as results |
| What is it made of? | Parts of a whole |
| Which one do we choose? | Options and, separately, the criteria for choosing |
| What happened? What did you find? | Findings, from most to least important |

Common mistake: writing mechanisms while thinking they are reasons. Test: if an item reads well as "the system can...", it's a mechanism, not a reason. "The format is compatible with the ERP" is a mechanism; "we'll finally have margin data per client" is a reason. The mechanism moves down a level and becomes support for the reason.

### How to synthesize a group

- **If they are actions:** the synthesis is the **effect** of doing them all. First, write each action as a concrete result: not "improve asset approval", but "approve assets in 2 days instead of 5". Picturing a real person carrying out each step helps spot missing steps or steps that belong to another level.
- **If they are statements:** the synthesis is **what they have in common or what they imply together**, the inference the reader wouldn't make alone.
- **Avoid empty statements:** "there are three factors to consider", "there are opportunities for improvement", "several findings were identified". They summarize nothing; they only announce that a list is coming. Every synthesis has a subject, a verb and something the reader could argue with.

## The introduction: SCQ

The introduction tells the reader nothing new: it reminds them of what they already know and leads them to the question the text answers.

- **Situation:** something the reader knows and accepts.
- **Complication:** what changed, got stuck or forces them to decide.
- **Question:** the one that arises from that complication. In the text it often stays implicit, but write it down for yourself before drafting.
- **Answer:** the idea at the top.

**How much situation, depending on the reader.** Someone who asked for the document or was in the meeting needs one line or nothing. An already informed group, one or two sentences. A committee or distribution list that wasn't there, the full context, written for the least informed reader who has to act. Then trim: cover each sentence of the situation; if the complication still makes sense, that sentence was unnecessary.

**Order depending on the reader:**

| Pattern | Order | When |
|---|---|---|
| Standard | S, C, A | Reader who needs context |
| Direct | A, then S and C | Busy reader or one who already knows the topic. Default for emails and executive summaries |
| Concerned | C, S, A | The complication is what grabs attention |
| Question-first | Q, S, C, A | The reader already asked the question |

If the reader will probably reject the conclusion before hearing the reasons (bad news, hostile audience), start with the shared problem and let the answer arrive one step later, but in the first paragraph, never on page two.

For the most common document types (asking someone to do something, requesting approval for an expense, explaining how to do something, choosing between alternatives, a client proposal, a progress report) there are ready-made SCQ and key line patterns in `references/patterns.md`. Read it when the document is one of those types.

## Clarify mode

For when the user has an intention but not a message.

1. Ask, in a single message (or with the structured-questions mechanism if there is one), up to four things: who reads it and what they decide; what they already know; what changed or what the problem is; what you need them to do.
2. At most two rounds of questions. After that, state your assumptions and move on.
3. Deliver a card:

```
Reader:           who they are and what they decide
Question:         the reader's question, in one sentence
Main idea:        one sentence
Key line:         2 to 5 ideas of the same kind (kind: reasons / steps / ...)
Order:            deductive / chronological / structural / comparative, and why
Missing:          [missing: ...]
Assumptions:      what you assumed about the reader
```

4. Close with one line on the next step: drafting, or getting the missing data.

If the thinking is still exploratory and there is no conclusion, don't force one: say so and offer a map of hypotheses instead of a pyramid.

## Structure mode

1. **Reader and question.** Who reads it, what do they know, what do they have to decide or do? Write the literal question. If the reader is deciding whether to act, the question is what they gain by doing it, not just whether it can be done.
2. **SCQ**, one line per element.
3. **Main idea** in one sentence.
4. **Key line:** ask "why?" or "how?" of the main idea. Define the kind according to the table and choose the order.
5. **Depth according to the material.** A short text has two levels (idea and supports). A long document or one with sections usually has three. Don't inflate a short text.
6. **Bottom up**, if the user brings a list of points with no conclusion: group them by kind, synthesize each group, see what conclusion comes out of the syntheses and check it with an SCQ. Points that don't fit are either unnecessary or reveal a missing group.
7. **Outline first** if the document is long or important and the user is present: show it and wait for approval. If it's short or they asked for the final text, write it directly.
8. **Write.** Introduction, then one block per key line idea. Section headings are ideas in sentence form, not topics ("Costs rose because of the supplier change", not "Costs"). Risks, constraints and next steps are not reasons: they go in their own closing section, and if a risk changes the decision, it goes next to the main idea.
9. **Keep everything.** Every piece of data from the original material survives. Whatever doesn't support any idea goes to an appendix or is mentioned in one line at the end as "left out: ...". Restructuring is not summarizing.
10. **Clean text.** No S, C, Q labels in the result, and no comments on the chosen order. If the user asked for something to paste into a chat, deliver exactly that. Close, outside the text, with one line on what changed in the structure.

## Review mode

Diagnose. Don't deliver the rewritten text in this mode: offer it at the end.

Review in this order:

1. **Main idea.** Quote it verbatim or write "not there". Distinguish two different diagnoses: it doesn't exist anywhere (serious) or it exists but appears late (less serious). Say which paragraph it appears in.
2. **Introduction.** Only if the text has one. Is there a situation, complication and question? Does it bring data or arguments that should go below? Is it longer than the answer?
3. **Vertical.** Does what sits below each idea answer the question that idea raises?
4. **Horizontal.** Is each group of a single kind? Does it have an order you can name? Are there overlaps? Gaps are only flagged if the text itself defines the universe (the text saying "the causes are these four" doesn't prove there isn't a fifth).
5. **Headings and topic sentences.** Are they ideas or topics?
6. **Filler.** Ask "so what?" of each sentence: which idea above does it support? One that supports nothing is a candidate to go (risks and next steps are left alone).

Deliver:

1. **Verdict** in one line: *ready to send*, *minor tweaks* or *restructure*, with the main reason.
2. **Main idea** detected.
3. **Current pyramid** as an outline, as it stands.
4. **Findings**, at most seven, from most to least serious, each with the exact sentence from the text, which rule it breaks and how to fix it.
5. **The three highest-impact fixes**, one line each.
6. **Offer** to rewrite it, in one line.

If the text is already good, say so clearly and don't invent problems. If the user only shared their text in passing (didn't ask for a review), two sentences are enough: the main symptom and the offer.

A finding is a structural defect, not a wish for more content. "Sales figures are missing" is not a finding; "this reason has no support below it" is.

## Define the problem mode

For proposals, consulting work, research or any document that responds to a problem. Many weak proposals fail here, before a single line is written. The full procedure, with examples, is in `references/problem-definition.md`. In short, it answers three questions:

- **What's going on?** Starting scene (the structure or process that was working) and disturbing event (what changed).
- **What don't we like?** The undesired result (R1).
- **What do we want instead?** The desired result (R2), as concrete and measurable as possible.

The problem is the gap between R1 and R2. The document's question comes from there, and its form depends on the story: if there's no solution yet, it's "what do we do?"; if there already is one, "is it the right one?" or "how do we implement it?"; if the solution didn't work, "what do we do?" again.

## Adaptations by type of text

**Email or message.** The subject line states the request or the conclusion, not the topic ("I need your budget approval before Friday", not "Budget"). First sentence: the request or the answer, with a date if there is one. Then up to three supports. Explicit owner, request and deadline. Under 150 words unless a decision, an owner or a date would get lost.

**Proposal or quote.** SCQ from the client's problem, not from the proposer's. See the two proposal patterns in `references/patterns.md`. The company's history goes at the end or in an appendix.

**Report or executive summary.** Findings and recommendation at the top; methodology at the end or in an appendix. The most common mistake is recounting the work in the order it was done.

**Presentation.** Each slide has a title that is a complete sentence. Reading only the titles, in order, conveys the whole argument. The agenda is the key line. The body of each slide proves its title and nothing else.

**Academic text** (thesis, paper, conference talk). Respect the structure required by the journal or institution (IMRaD or another). Within it:
- Abstract: the full pyramid in miniature (problem, question, method, main finding, implication).
- Introduction: the SCQ maps to context, gap in the literature, research question and contribution.
- Discussion and conclusions: each paragraph opens with its claim and then supports it with evidence and citations.
- The methods section can be chronological: there the sequence is the content.

**Class or workshop.** Open with an SCQ that makes the session's question felt. Show the key line at the start as a map. Close by returning to the question.

**Post or narrative text.** Don't impose conclusion-first, because it kills the tension. Use only the internal logic: an identifiable central idea and grouped supports. If the post is an opinion or recommendation piece, the pyramid does help.

**Showing the structure on the page.** Headings that reflect the pyramid's divisions and state the idea; numbering or bullets for groups; key line points as the opening sentences of paragraphs, highlighted, when there are no headings. Between sections, a line that connects to the larger pyramid.

Before-and-after examples (email, short review, mechanism versus reason, academic introduction) are in `references/examples.md`.

## Check before delivering

Do it silently and fix what you find; don't print it.

1. Did I write down the reader's question, and does the main idea answer it in one sentence?
2. Is the first level the kind that question calls for (reasons, steps, parts, options)?
3. Does each group fit under a plural noun and have a nameable order?
4. Did I cover each branch to look for duplicates?
5. Do the syntheses assert something or are they empty?
6. Does the introduction only remind, without arguing?
7. Are all the figures, names and claims from the original intact, and did I add none?
8. Did I follow the three rules at the top (no rewriting without permission, no forcing timelines, no inventing)?
Pliki w paczce (4)
  • SKILL.md 17 KB
  • references/examples.md 3 KB
  • references/patterns.md 5 KB
  • references/problem-definition.md 4 KB

Wersje

W bazie nie ma innych skilli o nazwie minto.

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

  • 100pptx-pyramid-principle-structure
    Układa prezentację dla zarządu według Zasady Piramidy Barbary Minto: najpierw odpowiedź, potem argumenty.
  • 100pyramid-principle
    Układa przekaz według zasady piramidy Barbary Minto: najpierw odpowiedź, potem pogrupowane dowody, dla zarządów, inwestorów i memoriów decyzyjnych.
  • 100minto-pyramid
    Układa komunikację metodą piramidy Minto, od wniosku przez argumenty po szczegóły, w rekomendacjach, streszczeniach dla zarządu, notatkach decyzyjnych i wyjaśnieniach zaczynających się od odpowiedzi.
  • 100top-down-memo
    Pisze według zasady piramidy Minto: najpierw wniosek, potem 2 do 4 argumentów MECE i dowody, w memach, mailach do zarządu i briefingach.
  • 100business-writing
    Stosuje zasadę piramidy Barbary Minto do pisania i redagowania komunikacji biznesowej (maile, notatki, oferty, streszczenia, statusy, prośby o decyzję, raporty): struktura odgórna, wstępy SCQA i testy logiki.
  • 95minto-pyramid
    Przestrukturyzowuje tekst według Piramidy Minto, od wniosku przez pogrupowane powody po dowody, i sprawdza logikę szkicu rekomendacji, memo lub podsumowania.

Uwagi i zgłoszenia

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