home-single-copy
/home-single-copy
Prowadzi lokalny dom danych na jednym laptopie lub komputerze: kopie zapasowe, przywracanie i ocenę przejścia na git.
- Autor
- tikoci ↗
- Repozytorium
- routeros-muse ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.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 04.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
Prowadzi lokalny dom danych na jednym laptopie lub komputerze: kopie zapasowe, przywracanie i ocenę przejścia na git.
Oryginalny opis (EN)
No-server local home: one laptop/desktop copy. Use when: bootstrapping or working locally, backup/restore questions, copy-this-tree or two-machine questions, or evaluating promotion to git.
Jak działa
- Part 1 — The checklist (instantiate → protect → share → promote)
- Part 2 — Skill doc
- Part 3 — Assumptions (decided during template design; this skill assumes)
Podgląd SKILL.md
--- name: home-single-copy description: "No-server local home: one laptop/desktop copy. Use when: bootstrapping or working locally, backup/restore questions, copy-this-tree or two-machine questions, or evaluating promotion to git." topics: [workspace, backup, home] tested: none --- # `home-single-copy` skill (no-disk local home) [template v1 draft] Vendored from the build notes for review with template v1. See also `home-private-git` (promotion target). No secrets below. ## Part 1 — The checklist (instantiate → protect → share → promote) ### 0. Decide this is the home Use single-copy when the router has no usable disk, or the owner simply wants one laptop/desktop copy. Zero ceremony, works fully offline after tool install, lowest owner friction — and trivially consistent, because there are no router-owned dirs to pull. This is workspace-first in its purest form: a prepared directory plus conventions plus skills, no deployment anything. ### 1. Instantiate (minimal — grow on demand) 1. Create the layout subset: START-HERE, `workspace.toml` (`home = "single-copy"`), `inventory/ observations/ operations/` plus `inbox/`. N=1 starts here and stops here. 2. Add `checks/ .agents/skills/ reports/ whiteboard/` only when something needs to live in them. Empty dirs are not instantiated to look complete. 3. Record trilogy pins in `workspace.toml` at bootstrap. ### 2. Backup discipline (the price of no server) Single copy is a single point of loss. The skill requires, and the owner provides (mechanism is the owner's choice — the skill states the requirement, not the tool): 1. A backup exists, its location + cadence recorded in `workspace.toml`. 2. A restore was TESTED at bootstrap (date recorded). An untested backup is not a backup. 3. Session close never skips: uncommitted-thought vs unshaped-draft is tracked the same as the git home (the session-close discipline carries over, minus git) — inbox + last summary tell the next session where things stand. ### 3. Sharing (manual until git — no second live copy) 1. Cross-session continuity is the tree itself: `inbox/` + last session summary (§4). There is no owner-facing share channel besides promoting to git (§5). 2. A second live copy is FORBIDDEN without the §5 guard. Sharing a file tree by copy/sync tools without declaring canonical is how networks silently fork. 3. Drive is never the share mechanism (`anti-drive-live`). 4. Cross-session/cross-environment handoff is a note in the tree (`inbox/` or `operations/*-handoff.md`): point at state, never paste copies. No side channel exists or is needed. ### 4. Multi-session rule (one writer at a time) 1. Session open: read `inbox/` + the last session summary. 2. Session close: write the summary (what changed, what is pending, where state is). 3. Never assume the tree is as you left it — verify, then work. ### 5. Promotion trigger Second machine, second agent, or owner request → the skill AUTO-SUGGESTS bootstrapping `home-private-git` (the git workflow §4). Promotion requires the privacy scrub first: raw pulls stay behind, redacted summaries may travel. Until promotion, §3–§4 hold. ### 6. Second-copy guard If a second copy appears anyway: declare ONE canonical in `workspace.toml` immediately; the other carries an age manifest and is read-only reference. Still never two-way sync. ## Part 2 — Skill doc ### Trigger Load when: bootstrapping or working in a no-server local home; backup/restore questions; any "can I copy this tree / work from two machines" question; promotion-to-git evaluation. ### Prereqs - Local trilogy + pull/checker installed; disk space for captures. - `workspace.toml` exists with home + pins; backup requirement (§2) satisfied before any real network state lands here. ### Access - Local writes free. Router rules unchanged (reads-first, production writes need go-ahead, ask for unknown operators). - Sharing writes happen only via handoff notes or git promotion — never by handing out live tree copies. ### Envs None new. Transport auth reuses the first-contact envs (`CENTRS_*`, CDB-first). ### Outputs - Minimal layout + `workspace.toml` (home, pins, backup record). - Per-session summaries in the tree (§4). - Promotion suggestion with scrub checklist when §5 triggers. ### Verification - Layout present, no unneeded empty dirs claimed as progress. - Backup record exists with location + cadence + tested-restore date. - No undeclared second copy (ask the owner when in doubt — forks hide in "oh, I also copied it to…"). - Checker exit 0 over captures worked this session; claims carry command + output. ### Recovery - Loss/corruption: restore from backup, verify with the checker, record the gap (what sessions are missing) honestly. - Fork discovered: §6 guard immediately — declare canonical, manifest the other, reconcile by re-pull/re-do, never by blind merge of two live trees. ### Limits - Single point of loss until promoted; the backup discipline is load-bearing, not advisory. - Manual sharing; multi-agent use without git promotion forks silently — hence the §5 auto-suggest. - No owner-facing share channel exists besides git promotion and in-tree handoff notes. ## Part 3 — Assumptions (decided during template design; this skill assumes) 1. Handoff is workspace-native (in-tree notes), never a side channel; owner continuity is the tree plus git promotion. 2. Backup mechanism is the owner's choice; only the requirement + tested-restore bit are the skill's business. 3. §5 fires as an auto-suggestion, not an auto-migration — the owner approves promotion.
Wersje
W bazie nie ma innych skilli o nazwie home-single-copy.
Migawka bazy z 13.11.2026 · wersja paczki c31541838366 (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
- 90home-private-git
Przygotowuje prywatne repozytorium git jako domowe miejsce pracy: pierwsze uruchomienie, przenoszenie z jednej kopii i pytania o zakres. - 100mnemoloci-backup
Tworzy kopie zapasowe vaulta Mnemoloci w git, opcjonalnie z kopią zdalną, i przywraca wcześniejsze wersje notatek, na przykład wczorajszą wersję strony. - 95backup-setup
Konfiguruje automatyczne kopie zapasowe vaulta do zsynchronizowanego folderu lub chmury, z weryfikacją archiwów i warstwową retencją. - 100obsidian
Obsługuje vault Obsidian, w tym notatki, tagi, notatki dzienne, kopie zapasowe i synchronizację, wybierając MCP, CLI lub git. - 100ops-backup-restore
Zabezpiecza i przywraca dane w Azure lub AWS: nazywa punkt odtworzenia, blokuje skarbiec kopii i sprawdza przywracanie na osobnej kopii. - 90ha-configuration
Zmienia konfigurację Home Assistant bezpiecznie: pliki YAML, sekrety, sprawdzenie konfiguracji, kopie zapasowe i aktualizacje.