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

meet

/meet

Przygotowuje materiał wyjaśniający przed spotkaniem badawczym i pisze notatkę po nim, a także poprawia cel w GOAL.md.

Licencja
MIT
Ostatnia zmiana repozytorium
30.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 30.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

Przygotowuje materiał wyjaśniający przed spotkaniem badawczym i pisze notatkę po nim, a także poprawia cel w GOAL.md.

Wyzwalacze z opisu

prepare the meeting materialprepare for the meetingsummarize the meetingwrite the meeting notesthe meeting is over미팅 자료 만들어미팅 준비해설명 자료 만들어
Oryginalny opis (EN)

Handles the before and after of one research meeting. Before the meeting, it creates explanatory material (markdown and slides) so the user understands how the method works and why the results came out as they did. After the meeting, it writes the meeting note and edits GOAL.md if the user adjusted the goal itself. Use it for "prepare the meeting material", "prepare for the meeting", "summarize the meeting", "write the meeting notes", "the meeting is over", "미팅 자료 만들어", "미팅 준비해", "설명 자료 만들어", "미팅 정리해", "회의록 써", "미팅 끝났다".

Jak działa

  1. This material does not decide
  2. Read
  3. Section order
  4. How to explain
  5. Do not omit
  6. Saving and confirming before the meeting
  7. Meeting note
  8. GOAL.md
  9. Procedure after the meeting
Sekcje z nagłówków SKILL.md, w oryginale · 115 linii, 1 786 słów
Podgląd SKILL.md
---
name: meet
description: Handles the before and after of one research meeting. Before the meeting, it creates explanatory material (markdown and slides) so the user understands how the method works and why the results came out as they did. After the meeting, it writes the meeting note and edits GOAL.md if the user adjusted the goal itself. Use it for "prepare the meeting material", "prepare for the meeting", "summarize the meeting", "write the meeting notes", "the meeting is over", "미팅 자료 만들어", "미팅 준비해", "설명 자료 만들어", "미팅 정리해", "회의록 써", "미팅 끝났다".
---

# Meeting (meet)

This skill handles the before and after of one meeting. Before the meeting it creates explanatory material (Part 1), and after the meeting it writes the meeting note (Part 2).

# Part 1. Before the meeting: explanatory material

The purpose of this meeting is for the user to understand. Rather than reporting what was done, the material explains step by step how the method works and why the results came out as they did.

Create two pieces of material.

1. **Markdown material** `meetings/YYYY-MM-DD-slides.md`: the source of the meeting content. Write it in the section order below.
2. **Slides** `meetings/YYYY-MM-DD-slides.html`: the markdown material drawn in the form shown in the meeting. Do not add or remove content. Read `slides/RULES.md` in the plugin folder (`../../slides/RULES.md` relative to this skill folder) and build the slides with its rules and `slides/template.html`.

## This material does not decide

- It does not draw conclusions. Causes and interpretations are presented as candidates, each with its evidence.
- It does not make decisions. Items to be decided are shown as options with pros and cons. If an option is recommended, mark it `recommended` with the reason, but do not write it as if it were decided.
- While creating the explanatory material, do not edit GOAL.md or the meeting notes. That is done in Part 2 after the meeting.

## Read

1. `GOAL.md`: background, goal, success criteria, schedule
2. The most recent meeting note `meetings/YYYY-MM-DD-note.md`: decisions, action items, deferred questions. If there is none, this is the first meeting
3. Previous meeting material `meetings/*-slides.md`: to check which concepts were already explained
4. The `git log` subjects and bodies since that meeting date, and run records and result files. Examples are taken from these records

## Section order

| Section | Content |
|---|---|
| Questions for this meeting | 1 to 3 questions this material explains. Example: "Why do 65% of runs diverge at learning rate 0.1?" |
| Reminder of the last meeting | One slide. For each previous action item, its status (done, in progress, not done with the reason). For each success criterion, its position (met, not met with the current level, not yet measured). For the first meeting, the goal and success criteria in GOAL.md |
| How it works | First, one slide on how the problem is abstracted: what is the input, what is the output, and which assumption makes that possible. Then show the full architecture diagram, in the order the data flows. For each part related to the questions, open with its input and output with example values, then zoom in on its computation steps. Follow one example from an actual run record from start to end, showing the input, processing, and output at each step |
| Results and causes | For each result, show how the metric is computed on one example, why the metric or test is used, and what its value means. Then show the candidate causes and the records that show each cause (which example, which part of which log). Attach conditions and sources to numbers, and distinguish measured values from estimates |
| Not yet explained | Phenomena whose cause was not found, and what to look at to find it |
| Understanding check | A few sentences stating what the user should know at the end of this meeting. This slide lets the user check that it matches their understanding |
| Decisions needed, next plan | Only when there are any. For each decision, one slide that draws every option side by side, then one slide with the pros and cons. Follow `Draw proposals and options` in `slides/RULES.md`. The next plan is given per option. When the decision is about what to improve, first list the functions with their current performance as in `Material for discussing improvements` in `slides/RULES.md` |

Write the section name in the eyebrow. Example: `How it works 2/4`. Follow `Order of explanation` in `slides/RULES.md`, including section dividers when the material is long.

## How to explain

- **Whether to explain a concept depends on whether it was already explained in this project.** Do not skip a concept because it is at graduate level or a "common term". The previous meeting material (`meetings/*-slides.md`) is the list of concepts already explained.
  - Concepts explained in previous material are recalled in one line.
  - Concepts never explained are explained even if they are common terms: a one-line definition, the role it plays in this method, and one example from actual records. On the slides, the concept is drawn as in `Draw new concepts` in `slides/RULES.md`. Example: "Label smoothing: a target distribution that moves part of the target probability from the correct class to the other classes. In this experiment it is used to reduce the model's overconfidence in the correct answer."
  - Do not write only a textbook definition. What it does inside this method is the point.
- **Spend slides on new concepts and new results.** Do not explain again at length what was already explained.
- **Use established terms and define them before use.** Follow `Terms and wording` in `slides/RULES.md`: established terms instead of colloquial descriptions, definitions on or before the first slide that uses a term, symbols only where needed with one meaning each, and named targets instead of words such as `we`.
- **Do not refer to steps by number only.** Write `data augmentation (③)` instead of `③`.
- **Take examples from actual records.** Attach the source (run path, example id). When a made-up example is used, mark it `illustrative`.
- **Attach an example or evidence to every claim.** Follow `Every claim has an example or evidence` in `slides/RULES.md`. This applies to the markdown material as well as the slides.
- **Do not assert a single cause.** Distinguish what the records show from estimates.
- **Explain a problem over several slides.** A failure, divergence, or wrong result is explained in steps (expected behavior, where it differs, observed symptom, mechanism per candidate cause, consequence), one slide per step with a visual, as in `Explain a problem step by step over several slides` in `slides/RULES.md`. In the markdown material, write one subsection per step.
- **Show how each value is obtained.** Follow `Show how each value is obtained` in `slides/RULES.md`: the computation of each metric on one example, the reason for each test, which component sets each value, the full rule of any post-processing done in this project, and how one component's output enters the next.
- **Do not quote the conversation.** Write decisions and arguments, not the user's words, as in `Do not quote the conversation` in `slides/RULES.md`.
- **Draw what is proposed.** Every option, new component, new data type, or new criterion that does not exist yet is drawn as in `Draw proposals and options` in `slides/RULES.md`. In the markdown material, write for each option what the diagram shows: which parts change, where the loss is computed, one sample of the data.

## Do not omit

- No action item from the previous meeting note is missing from the reminder.
- Every number has conditions and a source. A number whose source could not be found is not written, or is marked `source unconfirmed`.
- If numbers differ between documents, do not hide it; show both in `Not yet explained`.
- After writing `Results and causes`, check it against the questions by perspective in `references/questions.md`. If a question about these results was missed, put it in `Not yet explained`.

## Saving and confirming before the meeting

1. Write the markdown material to `meetings/YYYY-MM-DD-slides.md`. The date is the meeting date.
2. Build the slides `meetings/YYYY-MM-DD-slides.html` from the markdown material. One section of the markdown becomes several slides.
3. Run the checks in `slides/RULES.md`, including `slides/check.mjs`, which moves through every slide in every language. Fix every error it reports. Read the messages it prints in order and fix breaks in the connection between slides.
4. Open the slides in a browser and show them to the user. Commit only when the user requests it.

# Part 2. After the meeting: meeting note

After the meeting, do two things. Write the meeting note, and edit GOAL.md if the user adjusted the goal itself.

## Meeting note

Write the meeting note in the user's language by default. The user's language is the language the user writes in during the conversation. If the user requests a specific language, write it in that language. Section names in the template below are given in English; write them in the language of the note. If a previous meeting note exists, use the same section names as that note.

Write it to `meetings/YYYY-MM-DD-note.md`. The date is the meeting date, the same date as the meeting material (`YYYY-MM-DD-slides.md`). It has only three sections.

```markdown
# Meeting YYYY-MM-DD

## Decisions
- What the user decided. One sentence per item. If the user gave a reason, write it too.

## Action items
- Action items. If there are branches (sub-questions), put the branch name first. The reminder in the next meeting material checks this list item by item.

## Deferred questions
- Questions that were postponed without a decision this time.
```

- Write as decisions only what the user said. Anything Claude proposed during the meeting that the user did not decide goes in `Deferred questions`.
- Write action items specifically enough that the next meeting can judge whether they are done. Example: `add seed 1 and 2 runs on CIFAR-100` instead of `run more experiments`.
- Do not write a summary or the course of the discussion.

## GOAL.md

Edit GOAL.md only when the user decided to adjust the background, goal, success criteria, or schedule themselves. Decisions to change the method, implementation, or experiment design do not change GOAL.md. Such decisions are recorded only in the `Decisions` section of the meeting note.

When editing:
- Write in the language GOAL.md is already written in, unless the user requests another language.
- Replace the changed sentence. Do not append a new paragraph at the end of a section.
- Do not write "the previous goal was ..." or "changed in the YYYY-MM-DD meeting". The meeting notes and git keep the history.

## Procedure after the meeting

1. From the meeting conversation, extract what the user decided, the action items, and the deferred questions. Show the full meeting note in the response and get confirmation. Do not replace it with a summary or only a file path.
2. When the user confirms, save the meeting note.
3. If GOAL.md needs editing, show the proposed change for each section as the sentence before and the sentence after. When the user confirms, save it.
4. Commit only when the user requests it.
Pliki w paczce (2)
  • SKILL.md 11 KB
  • references/questions.md 2 KB

Wersje

W bazie nie ma innych skilli o nazwie meet.

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

  • 100wrapup
    Tworzy materiał prezentacyjny o projekcie badawczym dla osób spoza zespołu, z dokumentu i slajdów na podstawie notatek.
  • 100slides
    Tworzy slajdy z bieżącej rozmowy, najpierw zapisując z niej dokument w markdownie, a potem budując prezentację.
  • 100meeting-note
    Pisze notatkę ze spotkania z transkrypcji Google Meet, notatek lub zdjęcia tablicy, a potem proponuje zadania, oczekiwania i szkic podsumowania.
  • 90meeting-prep
    Przygotowuje jednostronicowy brief przed spotkaniem: kto w nim uczestniczy, co ostatnio ustalono, co użytkownik jest winien rozmówcom i czego od nich chce.
  • 90meeting-prep
    Buduje briefing przed spotkaniem: kto będzie w sali, na czym mu zależy, jaki jest cel użytkownika i jakie pytania zadać.
  • 90meeting-notes
    Wyciąga notatki i protokoły ze spotkań z transkryptów Teams, Zoom, Google Meet lub surowego tekstu, z decyzjami i zadaniami.

Uwagi i zgłoszenia

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