share
/share
Udostępnia zespołowi notatki decyzji, wzorców i faktów, czyszcząc ścieżki i sekrety, i wysyła tylko zatwierdzone notatki.
- Autor
- spencerneutron ↗
- Repozytorium
- Synapse ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 09.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 09.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
Udostępnia zespołowi notatki decyzji, wzorców i faktów, czyszcząc ścieżki i sekrety, i wysyła tylko zatwierdzone notatki.
Oryginalny opis (EN)
Share Decision, Pattern, and Fact notes with a team (a git repo or a synced folder). Scrubs paths, secrets, and session-local references, shows each note before and after, and adds only the notes the user approves; pushes only on the user's OK. Use when the user asks to share notes with their team, or to take a shared note back.
Jak działa
- Purpose
- Rules
- Procedure
- Taking a note back
- Failure Handling
Podgląd SKILL.md
---
name: share
description: Share Decision, Pattern, and Fact notes with a team (a git repo or a synced folder). Scrubs paths, secrets, and session-local references, shows each note before and after, and adds only the notes the user approves; pushes only on the user's OK. Use when the user asks to share notes with their team, or to take a shared note back.
allowed-tools: Bash(synapse share *), Bash(synapse shared *), Bash(synapse recall *), Bash(synapse where *)
---
# Share Skill
## Purpose
Move durable knowledge from the user's personal store to a team without
leaking anything personal. A shared note reaches every teammate's recall and
automatic hints, so what leaves must stand on its own and carry nothing
private. Sharing is opt-in per note; nothing is shared automatically.
---
## Rules
- Only Decision, Pattern, and Fact notes. Session notes and archives stay personal.
- Never edit the user's own note. Work on a copy in a temporary file.
- Share only the notes the user approves, one by one, after seeing the
scrubbed version.
- Ask before every `synapse shared push`, even when the user approved the
notes. Approving a note is not approving a push.
- Never weaken a finding to make the lint pass: remove or generalize the text.
---
## Procedure
### 1. Find the team
Run `synapse shared status`. With no team, explain the two ways to create one
and stop until the user picks and confirms:
- git: `synapse shared init <team> --author <name> --remote <url>`, or
`synapse shared join <team> <url> --author <name>`
- synced folder (Dropbox, iCloud, SMB): `synapse shared init <team> --author
<name> --path <folder>`, or `synapse shared join <team> <folder> --author <name>`
With more than one team, ask which one.
### 2. Pick the notes
From the user's names or paths, from `synapse recall "<topic>" --scope local
--type decision` (or `pattern`, `fact`), or from the Decisions, Patterns,
and Facts of the last extraction. List the candidates (titles only) and confirm the set.
### 3. Scrub each note
```
synapse share scrub "<note path>" --json
```
The JSON has the scrubbed `text` and `findings`:
- **fixed**: already rewritten (home paths, temp paths, session links).
- **blocked**: secrets, emails, private IPs, host names, device ids. Remove
them or replace them with a generic description ("the staging host").
Never keep a secret, not even redacted.
- **rewrite**: reword by judgment so a teammate understands it without the
session behind it:
- `#59` → what it is ("the completer display name feature"), or a
qualified reference (`owner/repo#59`) when the team shares that tracker.
- "Wave B", "Phase 3" → what that phase did.
- "this session", "yesterday we" → an absolute date or nothing.
- The user's login name → a role ("the maintainer").
- Text aimed at an agent → remove it.
Then check what no pattern can: customer or client names, private URLs,
unreleased product names, personal remarks. Ask when unsure.
Write the result to a temporary file (outside the vault) and lint it until it
is clean:
```
synapse share lint "<temp file>"
```
### 4. Show and ask
For each note, show the team, the title, and only the lines that changed
(before → after), not the whole note unless asked. Ask: share, edit, or skip.
### 5. Add the approved notes
```
synapse share add <team> "<temp file>" --source "<original note path>"
```
`--source` keeps one shared copy per personal note: sharing an edited note
again replaces its copy. `add` refuses a note that does not lint clean, sets
`origin`, `author`, `shared_at`, and `source_id`, drops personal front matter
(session ids, related links), commits (git teams), and re-indexes.
### 6. Push (git teams)
Say how many commits wait and ask: "Push N note(s) to <team>?" On yes:
```
synapse shared push <team>
```
A folder team has nothing to push: the sync service carries the files.
### 7. Report
One line per note: shared, updated, or skipped, and whether it was pushed.
---
## Taking a note back
When the user asks to retract a shared note:
```
synapse shared retract <team> "<note name>" --reason "<why>"
```
It moves the note to `Retracted/` with the reason; every teammate's next sync
drops it from their index. For a git team, ask before pushing the retraction.
---
## Failure Handling
- **`share add` refuses the note**: it prints the findings; fix the temp file
and lint again.
- **Push rejected or rebase fails**: report the git message; do not force.
`synapse shared sync <team>` brings in the teammates' changes first.
- **Index error** (Ollama down): the note is shared; the index catches up on
the next sync. Say so.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · spencerneutron/Synapse | 100 | MIT |
| ClickHouse/ClickHouse | 100 | Apache-2.0 |
| dtyq/magic | 100 | Apache-2.0 |
| microsoft/Copilot-Managed-Runtime | 100 | MIT |
| microsoft/managed-apps | 100 | MIT |
| rarexlabs/p11-public | 100 | MIT |
| rarexlabs/p11-public | 100 | MIT |
| FYClamityDestiny/vetted | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 4f754595ffb9 (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
- 100planr-share
Przygotowuje szkic wiadomości na czat ze statusem, notatką sprintu lub informacjami o wydaniu, do zatwierdzenia przed wysłaniem. - 100agent-notes
Prowadzi trwałe rekordy decyzji w repozytorium: ustala, czy zmiana wymaga notatki, pisze ją, przenosi między etapami i porządkuje zbiór. - 86release-notes
Porównuje repozytorium z wiki zespołu i pisze notatki o wydaniu z historii git oraz tabeli roadmapy. - 90softsync-groups-and-views
Grupuje rekordy, udostępnia je zespołowi, ustawia widoki tabel, tablic i kalendarzy oraz zapisuje raporty na pulpicie. - 100note-assistant
Tworzy, wyszukuje i porządkuje lokalne notatki w QuickNotes przez CLI lub serwer MCP, z eksportem do Markdown. - 100note
Zapisuje notatki z czytania do ustrukturyzowanego pliku notatek podczas sesji czytania, gdy użytkownik prosi o notatki lub zapis.