add-managed-tool
/add-managed-tool
Dodaje zarządzane narzędzie zewnętrzne, np. rust-analyzer czy git: wykrycie, instalację, testy i wiersz w panelu.
- Autor
- jabbott-iii ↗
- Repozytorium
- Tidepool ↗
- Licencja
- Apache-2.0
- 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.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Dodaje zarządzane narzędzie zewnętrzne, np. rust-analyzer czy git: wykrycie, instalację, testy i wiersz w panelu.
Argumenty
/add-managed-tool <tool> <what Tidepool needs it for>
Oryginalny opis (EN)
Use when Tidepool must find, install, update or drive a new outside program (or change how it handles an existing one), such as rust-analyzer, git, an SDK package, Xcode tools, a debug adapter or an LSP server. Adds the descriptor, detection, install plan, tests and Toolchains-panel row per ADR-0002.
Jak działa
- 1. Research the tool (with the web tools; cite sources)
- 2. Descriptor (toolchains/<tool>.toml)
- 3. Code in tidepool-toolchain
- 4. Tests
- 5. UI and docs
- 6. Report
Podgląd SKILL.md
--- name: add-managed-tool description: Use when Tidepool must find, install, update or drive a new outside program (or change how it handles an existing one), such as rust-analyzer, git, an SDK package, Xcode tools, a debug adapter or an LSP server. Adds the descriptor, detection, install plan, tests and Toolchains-panel row per ADR-0002. argument-hint: "<tool> <what Tidepool needs it for>" --- # Add or update a managed tool Request: `$ARGUMENTS` Outside programs are managed tools (ADR-0002): Tidepool installs, updates, configures and drives them through their official channels, and never bundles or reimplements them. Read `docs/subsystems/toolchains.md` and the "Managed tools" table in `docs/02-dependency-policy.md` first. ## 1. Research the tool (with the web tools; cite sources) - Official install and update channel per OS (installer, package manager, vendor tool such as `rustup` or `sdkmanager`), and whether it needs admin rights. - Official download URL and published checksum, if Tidepool downloads anything itself. - License, and how the user accepts it. - How to detect it: env vars, standard locations, `PATH` name, version command and output format. Check the installed tool's `--help` if this session has it. - Output formats Tidepool will parse (machine-readable flags such as `--porcelain`, `--message-format=json`, `-z`). - If a fact can't be verified, write "unverified" and leave the roadmap box unchecked with a `⏳` note. ## 2. Descriptor (`toolchains/<tool>.toml`) - `id`, purpose, platforms, minimum and recommended versions, detection rules, install/update steps per OS, download URL + SHA-256 (pinned; never fetched at runtime), license entry, and the features it unlocks. - Run `cargo xtask tools`. Until M5.1 lands it exits 1 as not yet implemented; say so rather than report a pass. ## 3. Code in `tidepool-toolchain` - Detection and version parsing (with a timeout). - Install and update plans: every step is listed to the user before anything runs; downloads go through `download` and are SHA-256 checked; license prompts and admin commands run in the integrated terminal when the user presses Run; nothing is piped into prompts. - Spawning through `process`/`sessions` only: argv vector, explicit env, output caps, kill on shutdown. Secrets only through `SecretArg` / `SecretEnv`. - Respect workspace files that pin versions (`rust-toolchain.toml`, Gradle wrapper) and workspace trust (ADR-0014). ## 4. Tests - A fake tool in `crates/testkit/fake-tools/` reproducing real output for found, missing, outdated and error cases, including slow responses. - Parser fuzz target for any output format parsed. - A gated real-tool test (`TIDEPOOL_IT_<AREA>=1`) that prints `SKIPPED: <reason>` when unavailable. - A test that no constructed argv contains a secret, if the tool takes any. ## 5. UI and docs - A Toolchains-panel card (status dot, version, path, actions) and, if needed, the tool's own panel in `editor`. - Add or update the row in `docs/02-dependency-policy.md` → "Managed tools" and in `docs/subsystems/toolchains.md`. - Ask `security-reviewer` to review. ## 6. Report Sources checked, descriptor values, tests run with results, gated tests not run, and anything still unverified.
Wersje
W bazie nie ma innych skilli o nazwie add-managed-tool.
Migawka bazy z 13.11.2026 · wersja paczki d5c34812cce9 (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
- 100diagnose-lspmux
Diagnozuje problemy z połączeniem lspmux i rust-analyzer, gdy narzędzia MCP zawodzą, rust_server_status pokazuje błędy albo rust-analyzer nie odpowiada. - 100rs-symbol-analyzer
Analizuje strukturę projektu Rust na podstawie symboli LSP: wypisuje struktury, cechy i funkcje. - 100evaluating-third-party-tools
Ocenia, czy zewnętrzne repozytorium, narzędzie lub biblioteka są przydatne i bezpieczne, zanim cokolwiek zostanie zainstalowane. - 96e2e-coverage-analyzer
Sprawdza pokrycie testami e2e zmian w gałęzi git i dopisuje brakujące przypadki testowe. - 90write-rust-tests
Pisze testy w języku Rust, które sprawdzają poprawność kodu i zachowanie funkcji w projekcie. - 100run-rust-tests
Uruchamia testy Rust po zmianach w kodzie, żeby sprawdzić ich poprawność.