tow-setup
/tow-setup
Konfiguruje TOW w vaultcie Obsidian, łączy go z projektem i rejestruje metadane projektu, także przy przenoszeniu plików.
- Autor
- NamhyeonKo ↗
- Repozytorium
- tag-ontology-wiki ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.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 12.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
Konfiguruje TOW w vaultcie Obsidian, łączy go z projektem i rejestruje metadane projektu, także przy przenoszeniu plików.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when setting up TOW in an Obsidian vault, connecting a vault for project use, or registering project metadata. Triggers: "set up TOW", "connect my vault", "register this project with TOW", "start a new vault with TOW", "use TOW with my existing vault", "move my TOW files to tow/", "migrate my vault".
Jak działa
- Workflow
Podgląd SKILL.md
---
name: tow-setup
description: >-
Use when setting up TOW in an Obsidian vault, connecting a vault for project use, or
registering project metadata. Triggers: "set up TOW", "connect my vault", "register this
project with TOW", "start a new vault with TOW", "use TOW with my existing vault",
"move my TOW files to tow/", "migrate my vault".
---
# tow-setup
Read the [conventions](../../docs/methodology.md) and the [TOW recipe](../../docs/recipe.md) (§1–2 PARA layout). Branch on the current location: run `tow config` and use its reported vault root/layout; if no vault is resolved yet, use `tow --root <vault> config` only for a vault path the user identifies. In a project, register the project and vault connection without changing host configuration. Current vault files live in visible `tow/`; project metadata remains in `.tow/`.
`tow` is not a command on your PATH: run the executable `scripts/tow.py` two directories above this file by its absolute path (with `python3` if the host can't execute it), for example `"<plugin-root>/scripts/tow.py" config`.
## Workflow
1. **Inspect names and settings first.** Determine whether the current folder is inside a `tow/` vault, an older `.tow/` vault, a legacy vault (`tow.json`, a non-empty `Tag-Dictionary.json` or `Category-Dictionary.md` at its root), or a project. An empty root `Tag-Dictionary.json` (`{}`) by itself is the plugin's starter, not a legacy marker; if `tow init` reports it, initialize the `tow/` layout and do not delete the root file. Inspect folder/file names and configuration; don't read project document contents as setup input. Never infer a vault from `.obsidian` or the active Obsidian vault.
2. **Inside a vault.** If `tow/`, `.tow/`, or a legacy vault is already recognized, report its effective configuration. Otherwise ask whether the user wants TOW setup, their chosen PARA/custom layout, and which optional dictionaries they want; no preference is inferred from folders. For a new vault with no marker, target it explicitly with `tow --root <vault> init` and show every path it proposes. Apply with `tow --root <vault> init --apply` only if the user approves the complete preview; pass `--dictionaries` when the user chose dictionaries in a free-form vault. For a custom layout, first propose the exact `tow/config.json` settings (including `"scope": "vault"` and chosen folder/dictionary paths) and selected starter files. When the default paths suit a vault without settings, preview with `tow --root <vault> init --scope vault` (add `--dictionaries` only if chosen): it records the scope and creates no PARA folders. Otherwise preview with `tow --root <vault> init`. After approval, add `--apply` to the same command only if its complete preview matches the approved plan; otherwise create only the approved subset with file tools, preserving existing files. When `init` says the folder has notes outside the PARA folders, ask the PARA-or-own-layout question before applying anything. Never create a dictionary just to satisfy a helper check. For a request to move existing TOW files, or when a legacy/`.tow/` config prints its migrate hint, first update the Tag Ontology plugin to 0.10.1 or later on every device, then preview `tow --root <vault> migrate` and apply only after approval with `tow --root <vault> migrate --apply`. If the preview warns that the migrated search scope is empty (no PARA folders, typical of a vault used only with the Tag Ontology plugin), ask whether to keep the existing folders or adopt PARA; for the existing folders, preview and apply with `--scope vault` instead. `--scope` is refused where a config file already decides the scope; propose that file's exact edit instead. Keep old files by default; after an applied migration TOW reads and writes only `tow/`, so tell the user the kept originals (root `Tag-Dictionary.json`, `.tow/`) no longer change and are not the dictionary to edit. Migration carries root `Tag-Dictionary.md` into `tow/tags.md` and the Markdown category rule document into `tow/categories.md`; tell the user to update notes that link to those old files if they later remove them. Only after the user confirms plugin 0.10.1 or later is installed on every device may you offer removal as a separate approved plan: preview `tow --root <vault> migrate --remove-legacy`, then apply with `tow --root <vault> migrate --remove-legacy --apply` only after approval and verification.
3. **Record the connection.** Show `tow connect <vault>` and wait for approval before `tow connect <vault> --apply`; confirm with `tow connect`. It writes the user's personal `~/.tow/config.json`, never a project file. Outside a vault, `TOW_VAULT` overrides the saved connection. Inside a vault, the nearest ancestor vault takes precedence over both personal connections; use `--root` for an explicit choice. Setup does not edit host configuration.
4. **Set up from a project.** Determine the project root and `tow config` vault connection. If no vault is connected, ask the user to set up the vault first. Ask whether project `.tow/` metadata should be local or shared. Before project registration, inspect root/folder names only with host file tools to identify dependency/build folders; propose excludes only for folders actually found (for example `node_modules`, `vendor` or `dist`) and get approval. Show the complete vault `tow/tags.md` manual text before copying it; ask for any desired edits to remove private notes. Preview `tow project init --mode <local-or-shared> [--exclude <glob> ...]` as selected, then apply only after approval with `--apply`. This creates project `.tow/config.json`, `documents.json`, the project tag dictionary/manual and `.tow/.gitignore` (`*` in local mode, `documents.local.json` in shared mode). To share a local project later, replace `*` with `documents.local.json`; never delete that file. After `tow project init --apply`, make any user-requested manual edits to the project copy `.tow/tags.md` before committing shared-mode metadata. After registration, use `tow project files` for names-only Markdown/Git-status discovery; list untracked and ignored paths before any content read, and read those only when the user selects them. It never writes project documents or stores the vault path in the project.
5. **Align the Tag Ontology plugin.** Read the warning line from `tow config`. If it says the plugin dictionary path differs or could not be checked, explain that plugin 0.10.1 and later auto-detect `tow/tag-dictionary.json`, then `.tow/tag-dictionary.json`, then the stored path unless a custom path was chosen. Tell the user to align the plugin's “Dictionary path” setting with the effective configured `tagDictionary` path (normally `tow/tag-dictionary.json`). Never edit `.obsidian/` settings.
6. **Print host access guidance.** Show only relevant snippets for the user's host; substitute the actual vault root and configured note folders. These are permission hints, not changes TOW makes:
- Claude Code reads: `Read(//<vault>/**)` or `permissions.additionalDirectories`; send-vault writes: `Edit(//<vault>/<note folder>/**)` or per-call approval.
- Codex reads outside the workspace are not blocked by the default sandbox; writes require configured vault note folders in `sandbox_workspace_write.writable_roots` or approval. Permission profiles are beta and do not cover MCP.
- Antigravity: `read_file(<vault>)` and, only if sending is wanted, `write_file(<vault>/<note folder>)` permission rules.
State that skills and TOW do not provide an OS-level access boundary; host tools and shell can have different permissions. Never bypass access denial or edit host settings/configuration.
7. **Verify and report.** Re-run the applicable `tow config`, `tow connect`, or `tow project status` and check only the approved setup changes. A remaining `search scope is empty` warning means helper searches still read no note; report it as unresolved. Confirm existing notes/project documents were untouched. Report skipped setup choices and the next useful `tow-query` or `tow-send-vault` action.
Wersje
W bazie nie ma innych skilli o nazwie tow-setup.
Migawka bazy z 13.11.2026 · wersja paczki 8e0f495dba4f (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
- 100tow-send-vault
Wysyła wybraną treść projektu do połączonego vaulta Obsidian jako nową notatkę na wyraźną prośbę. - 100tow-link
Łączy notatki w vaultcie linkami wiki przy istniejących wzmiankach o tytułach i aliasach, także dla nowo zapisanych notatek. - 100setup
Łączy projekt z folderem w vaultcie Obsidian, by każda sesja Claude Code zapisywała notatkę i zaczynała od briefu. - 100kb-init
Konfiguruje nową bazę wiedzy lub vault Obsidian, tworząc szkielet projektu. - 85sync-vault-cli
Przeszukuje, czyta i diagnozuje pliki w chmurowym vaulcie Sync przez polecenia CLI obsidian sync-vault. - 100vault-setup
Interaktywnie konfiguruje vault Obsidian: drugi mózg, baza wiedzy, bootstrap nowego vaulta i ustawienia zarządzania wiedzą osobistą.