meeting-notes
/meeting-notes
Zamienia nowe nagrania i transkrypcje spotkań w ustrukturyzowane notatki śledzone w rejestrze, z plikiem roboczym dla każdej osoby.
- Autor
- SHOTClubhouse ↗
- Repozytorium
- shotos ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zamienia nowe nagrania i transkrypcje spotkań w ustrukturyzowane notatki śledzone w rejestrze, z plikiem roboczym dla każdej osoby.
Oryginalny opis (EN)
Turns new meeting recordings or transcripts into structured notes, tracked in a ledger, with a rolling file per person or organisation. Use when catching up on meetings or processing recordings. Drafts only; never sent to attendees.
Jak działa
- Context and handoff
- Start here
- When not to use this
- Steps
- Output
- Checks
Podgląd SKILL.md
--- name: meeting-notes description: Turns new meeting recordings or transcripts into structured notes, tracked in a ledger, with a rolling file per person or organisation. Use when catching up on meetings or processing recordings. Drafts only; never sent to attendees. --- # Meeting notes Convert new recordings into notes that stay useful, and never process the same recording twice or lose one silently. Stage: Track. Rules: 3 Read back the real result, 4 Claim only what you can show. ## Context and handoff Read the agenda and source transcript or notes. Verify names, commitments and dates against the source, and mark disputed or missing details. Use `decision-record` for a material decision and link to the original meeting record. ## Start here **Minimum to start:** the transcript or recording ID, the agreed scope and the ledger (on a first run, the agreed source; the ledger is created in step 1). **First output:** the per-meeting note with decisions, actions and open questions at the top, and speakers marked unidentified where unconfirmed. **Uncertain:** disputed owners, dates and gaps in the transcript are listed under open questions rather than smoothed over. **Handoff:** pull out decisions and actions awaiting confirmation for the owner, each with who must confirm. ## When not to use this Skip it for a live meeting that has no recording yet, for a request to publish or send notes to attendees (draft only; the owner sends), and for recordings the owner has marked private. ## Steps 1. **Open the ledger.** Read the processed-recordings ledger in place ([ledger-template.md](ledger-template.md)). Read the last completed coverage checkpoint. If the legacy watermark is the latest processed recording, recheck that boundary and any recorded gaps before treating coverage as complete. On the first run, record the agreed source and start. 2. **List recordings in scope.** Set a cutoff with its timezone. Include the boundary timestamp, earlier gaps and source corrections you know about. Match by stable recording ID and record the source revision when available. A partial listing or pasted transcript can support an individual note. Coverage needs the complete inventory. Keep private recordings outside the agreed scope. 3. **Apply the agreed length filter.** If none is agreed, process every recording and ask once. Record an eligible short recording as "skipped, too short" with its length and the agreed rule. Keep recordings the owner flags as material in scope regardless of length. Preserve the original recording. 4. **Read the transcript first.** Use the full transcript as the record of what was said. Use the calendar entry only for context: title, attendees, organisation. Do not fill gaps in the transcript from the calendar. 5. **Confirm identity.** Before naming anyone, check who spoke: use self-identification, a verified speaker map or the owner's confirmation. A calendar attendee list can suggest a match but does not identify a speaker. If a speaker is unclear, write "unidentified speaker" and ask. Never guess a name or an organisation. 6. **Write the notes** using [template.md](template.md): purpose, decisions, actions with owner and date where stated, open questions, and anything said that conflicts with earlier notes. 7. **Update the rolling file.** Keep one dated entry per recording ID and a short standing position for the person or organisation. For a retry, reconcile the existing entry. For a corrected source revision, compare it with the revision already checked and update that same note and rolling entry. Record what changed and its source. Route disputed decisions or action owners for confirmation before changing the standing position. 8. **Verify, then record coverage.** Read back the per-meeting note and rolling entry. Check names, numbers, dates and actions against the transcript before marking that revision processed. Keep inaccessible transcripts, material identity questions and failed writes pending with their reasons. Read back the ledger. Advance the checkpoint when the source listing is complete and each in-scope ID is verified or explicitly skipped under the agreed rule. Otherwise retain the checkpoint and report where to retry. See the [retry example](retry-example.md). 9. **Stop at the boundary.** Sending notes to attendees or creating tasks elsewhere needs the owner's yes. ## Output Per-meeting notes, the updated rolling file and the updated ledger. ## Checks - The retry matches stable IDs. An incomplete listing or pending recording keeps the last completed coverage in place. - A corrected transcript updates the existing entry and records its revision. - Short recordings were checked against the agreed filter and any owner exceptions. - No person or organisation was named without confirmation. - Notes match the transcript; calendar data is labelled as context. - A processed row has a checked note and rolling entry. Ledger edits were read back.
Pliki w paczce (5)
- README.md 3 KB
- SKILL.md 5 KB
- ledger-template.md 1 KB
- retry-example.md 2 KB
- template.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · SHOTClubhouse/shotos | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| cdeweyx/conor-os | 100 | MIT |
| nimadorostkar/Claude-Skills-collection | 100 | MIT |
| microclaw/microclaw | 100 | MIT |
| scratchpad-sh/skills | 100 | MIT |
| codeape-7/ai-agent-workflowgroup | 100 | MIT |
| Andrew-eGov/meeting-notes-agent | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 8163c287d5ce (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
- 90meeting-notes-to-tasks
Przenosi notatki ze spotkań do zadań: wyciąga decyzje i zadania i zapisuje je w narzędziu do śledzenia. - 95summarize-meeting
Zamienia transkrypcję spotkania w notatki z datą, uczestnikami, tematem, decyzjami, punktami i zadaniami do wykonania. - 100foresight
Czyta transkrypcje, podsumowania i notatki spotkań z aplikacji Google AI Edge Foresight na macOS, szkicuje z nich notatki ze spotkań i opcjonalnie zapisuje je z powrotem. - 100meeting-intelligence
Analizuje transkrypty spotkań, wyciąga decyzje, zadania, blokery i nastroje oraz generuje e-maile follow-up ze strukturalnym podsumowaniem i śledzeniem zadań. - 90meeting-action-items
Zamienia notatki i nagrania ze spotkań na decyzje i zadania z właścicielem, terminem i odnośnikiem, a potem tworzy je w narzędziu zadań. - 100meeting-minutes
Generuje strukturalne protokoły spotkań z transkryptów, także przy prośbach o notatki ze spotkania lub streszczenie spotkania.