Przejdź do treści
Biblioteka skilli
AI i agenci · Nauka i wyjaśnianie

os-ask-simple

/os-ask-simple

Wymusza pytanie użytkownika prostymi słowami przed każdym pytaniem technicznym lub ofertą opcji i przy prośbie o ocenę wyboru technicznego: czy warto, czy nie przekracza potrzeb, czy da się prościej.

Repozytorium
open-steps ↗
Licencja
MIT
Ostatnia zmiana repozytorium
05.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
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Wymusza pytanie użytkownika prostymi słowami przed każdym pytaniem technicznym lub ofertą opcji i przy prośbie o ocenę wyboru technicznego: czy warto, czy nie przekracza potrzeb, czy da się prościej.

Wyzwalacze z opisu

ask simpleask me simplyask me in plain words
Oryginalny opis (EN)

ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. Rewrites the question in plain words and always ends with one mar

Jak działa

  1. Language
  2. When to use
  3. Before anything: is this even a question for them?
  4. Light form - every question
  5. Full form - six checks, for structural choices
  6. Hard rules
  7. Known gotchas
Sekcje z nagłówków SKILL.md, w oryginale · 100 linii, 802 słów
Podgląd SKILL.md
---
name: os-ask-simple
description: >-
  ALWAYS invoke this skill before asking the user any technical question or
  offering options, and whenever they ask to be asked in plain words - "ask
  simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS
  invoke it too when the user asks for your view on a technical choice:
  whether it is worth doing, more than the problem needs, or replaceable by
  something simpler, and which option you would take. Invoke it even when the
  code makes the answer look obvious: the checks are what make the answer more
  than a guess. Rewrites the question in plain words and always ends with one
  marked recommendation. A structural choice first passes six checks, shown as
  a table: effort now, simpler substitute, extra work later, lock-in,
  over-engineering, easy to undo. Doing nothing is always weighed.
allowed-tools:
  - "Read(~/.claude/open-steps/**)"
---

# os-ask-simple

Two jobs. Ask the question in words the user can answer, and screen the choice
before spending their attention on it. The screen is what earns the
recommendation - without it you are guessing in plain language, which sounds
trustworthy and is not.

## Language

Write in the language the user speaks in this session. Detect it from the
conversation. Keep code, file names and identifiers in English.

## When to use

- You are about to ask the user a technical question.
- You are about to offer options.
- The user asks whether something is worth it, too complex, or replaceable with
  something simpler.
- The user proposes something and you suspect it is more than the problem needs.

## Before anything: is this even a question for them?

Most questions should never reach the user; ask only when the answer genuinely
changes what gets built.

- **Can you answer it by looking?** Read the code, the config, the last report.
  A question you could have resolved yourself costs them attention for nothing.
- **Is there a conventional default?** Take it and say you took it.
- **Would both answers lead to the same work?** Then it is not a fork.

## Light form - every question

```
<The question in one plain sentence. No jargon; if a term is unavoidable, give a
three-to-five word analogy.>

Why it matters: <one line, in terms of the product, not the code>
What changes later: <one line>
Easy to undo: <yes, and how - or no, and why>
```

Then the options, through your tool's question picker where it has one (in
Claude Code, AskUserQuestion). Offer two to four, each with a one-line
trade-off in plain words, the recommended one first and marked `(Recommended)`.

Keep the heading to 12 characters or fewer and each label to one to five
words. Claude Code's picker has the same limits, and short labels read well as
plain text too. Where there is no picker, write the same question and options
as plain text, the recommended one first and marked.

## Full form - six checks, for structural choices

Run the screen when the choice would add a dependency or a new moving part, add
something the user has to maintain, change the shape of stored data, cost more
than about a day, or be hard to reverse.

Show it as a table. Answer every row - "not checked" is allowed and honest;
silence is not.

| Check | What goes in the answer |
|---|---|
| How long now | Real effort, in hours or days, plus what has to be touched |
| Simpler substitute | The simplest thing that would also work - or "none found", having looked |
| Extra work for you later | Anything the user must do repeatedly afterwards: approvals, manual steps, watching a dashboard |
| Harder to change later | What this locks in, and what would be expensive to move afterwards |
| Over-engineering | Say yes when it is yes. A row that always answers "no" is decoration |
| Easy to undo | Reversible, and how - or one-way, and why |

Then the recommendation, in one line, as an actual opinion.

## Hard rules

1. **Always weigh doing nothing.** "Change nothing" is a real candidate, often
   the winner. If it lost, say in one line why.
2. **A recommendation is required.** Never lay out options and stop. "It depends"
   is not a recommendation - if it truly depends, say what it depends on and pick
   the option that is right under the more likely condition.
3. **Recommend against the user's own idea when the screen says so.** Plainly, in
   one sentence, with the simpler substitute named. They asked for a filter, not
   for agreement.
4. **Never recommend what you have not screened.** If the six checks were skipped
   because the choice looked small, say the choice looked small.
5. **One question at a time.** Two questions in one message means the second gets
   a careless answer.
6. **Watch your own bias.** The most interesting thing to build is not the
   recommendation. If an option is more fun to implement, that is a reason for
   suspicion, not for preference.

## Known gotchas

- **Two options that end in the same place are one option.** Do not pad the
  picker to look thorough.
- **"Over-engineering: no" answered reflexively kills the whole screen.** The row
  exists to be answered yes sometimes.
- **Effort estimates are guesses.** Say "roughly" and give a range. A confident
  number that turns out wrong costs more trust than a range ever does.
- **The user may pick the option you did not recommend.** That is the point of
  asking. Do it their way without re-arguing, and note the trade-off once.
Pliki w paczce (2)
  • SKILL.md 5 KB
  • references/01-sign-in-now-or-later.md 3 KB

Wersje

W bazie nie ma innych skilli o nazwie os-ask-simple.

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

  • 90os-say-simple
    Przeformułowuje tekst prościej i krócej dla czytelnika niepiszącego kodu: zaczyna od sedna, gdy ktoś nie rozumie odpowiedzi, raportu lub błędu.
  • 96answer-me
    Odpowiada na konkretne pytanie użytkownika bez wprowadzania jakichkolwiek zmian w projekcie.
  • 100asking-the-operator
    Zadaje operatorowi pytanie wielokrotnego wyboru z zadania Kookr, gdy decyzja należy do niego, i działa zgodnie z jego odpowiedzią.
  • 100explain
    Buduje stronę z wyjaśnieniem pojęcia, którego użytkownik nie rozumie, i pokazuje wizualizacje przed kolejnym pytaniem.
  • 100ask-me-again
    Zbiera wszystkie otwarte pytania agenta, sprawdza fakty i proponowane rozwiązania, a potem zadaje je ponownie po jednym, jasno i bez ściany tekstu.
  • 100ask-user-question
    Sprawia, że agent pyta użytkownika o wybór przez strukturalne narzędzie pytań zamiast listy w tekście, z formatem zapasowym.

Uwagi i zgłoszenia

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