databay-cli 0.1.0__tar.gz

databay_cli-0.1.0/.gitignore

@@ -0,0 +1,5 @@
+__pycache__/
+.venv/
+.pytest_cache/
+.ruff_cache/
+dist/

databay_cli-0.1.0/CHANGELOG.md

@@ -0,0 +1,46 @@
+# Changelog
+
+`databay-cli`: the Databay SDK and the `databay` command. semantic-release writes each version's section from
+the conventional commits since the one before (see `docs/cli.md`). This package's version is separate from
+`api_version`, the version of the API a client speaks.
+
+<!-- version list -->
+
+## v0.1.0 (2026-11-13)
+
+- Initial Release
+
+## What the first release holds
+
+### Added
+
+- First release of the SDK and the `databay` command: sign in, projects, sources, pipes, warehouses,
+  SQL queries and dashboards, generated from the Databay client contract.
+- The agent skill, installed with `databay skill install`.
+- `databay org list` and `databay org switch <organization>`: choose the active organization, which the
+  server stores and every token names; switching refreshes the token and clears the active project.
+- `databay login --org <organization>`; without it, a person in several organizations with none active
+  is asked on a terminal, and gets `org_choice_required` when the CLI cannot ask.
+- `databay status` reports `needs_org_choice`.
+- `databay schema-change state [--pipe-uuid] [--state]`: each pipe with an unfinished schema change,
+  worst first; `databay schema-change pending --status` picks the event statuses to list.
+- `databay metrics list`, `databay metrics describe <metric>` and `databay metrics query <metric>` with
+  `--by`, `--grain`, `--last` or `--from`/`--to`, `--where member=value` (also `!=`, `>`, `>=`, `<`, `<=`),
+  `--order member[:desc]`, `--limit`, `--warehouse`, `--model-version`, `--explain` and `--dry-run`; a query sends
+  `X-Databay-Caller: cli`, or `agent` with `--caller agent`, which the agent skill passes on every query.
+  `databay warehouse-access-role get-metrics|set-metrics` read and set a role's
+  metric grants. The agent skill teaches list, describe, query and explain, and labels a `databay sql`
+  fallback `answer_path: raw_sql`.
+- `databay metric-models push|validate|publish|show-draft|show-published|list|import-dbt`: a project's own
+  metric model, which the agent skill teaches (validate, push, publish, import from dbt).
+  `databay project-privilege list|grant|revoke`: a member's privileges in a project.
+- `databay metric-models metric-list|metric-add|metric-update|metric-remove|set-breakdowns|changes`: edit one
+  metric or one table's breakdowns on the draft's `--revision` (`draft_changed` when it moved), and see what a
+  publish changes; `publish --revision` publishes the draft that was checked. `databay project my-access` shows
+  the caller's role and privileges. Dashboard cards take metric specs (`spec_version` 2).
+- `databay api-key-project bi-connection <key_id> <project_id>`: where a BI tool signs in with an API key.
+- The agent skill teaches the metric form commands, metric cards and connecting a BI tool.
+- On a terminal, an error answered with a 5xx prints its `trace_id`.
+- Dashboards follow the server's cards model: a card belongs to the project (`dashboards-card`), is put
+  on dashboards with `dashboards-placement`, and a dashboard takes `--refresh-interval-s`;
+  `dashboards-home` reads or sets the project's Overview dashboard and pins cards to it.

databay_cli-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

databay_cli-0.1.0/PKG-INFO

@@ -0,0 +1,42 @@
+Metadata-Version: 2.5
+Name: databay-cli
+Version: 0.1.0
+Summary: Databay SDK and the databay CLI, generated from the Databay client contract
+Project-URL: Homepage, https://databurst.tech
+Project-URL: Repository, https://github.com/data-burst/databay-clients
+Project-URL: Changelog, https://github.com/data-burst/databay-clients/blob/main/python/CHANGELOG.md
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.12
+Requires-Dist: click<9,>=8.1.7
+Requires-Dist: httpx<1,>=0.27.2
+Requires-Dist: keyring<26,>=25.5.0
+Requires-Dist: platformdirs<5,>=4.3.6
+Requires-Dist: pydantic<3,>=2.9.2
+Requires-Dist: rich>=13.9.4
+Description-Content-Type: text/markdown
+
+# databay-cli
+
+The SDK and the `databay` command for a [Databay](https://databurst.tech) server. The agent skill that
+ships with it lets an agent such as Claude Code drive the server through the command.
+
+Needs Python 3.12 or newer, on Linux or macOS. The package is `databay-cli`; the `databay` project on
+PyPI is unrelated.
+
+Until the first PyPI release, install it from the repository:
+
+```bash
+uv tool install "git+https://github.com/data-burst/databay-clients#subdirectory=python"
+databay login --server https://<host>
+databay skill install --target claude
+```
+
+Install, sign in and releases: [docs/cli.md](https://github.com/data-burst/databay-clients/blob/main/docs/cli.md).
+Changes: [CHANGELOG.md](https://github.com/data-burst/databay-clients/blob/main/python/CHANGELOG.md).
+
+Licensed under Apache-2.0: see the `LICENSE` file in the package.

databay_cli-0.1.0/README.md

@@ -0,0 +1,20 @@
+# databay-cli
+
+The SDK and the `databay` command for a [Databay](https://databurst.tech) server. The agent skill that
+ships with it lets an agent such as Claude Code drive the server through the command.
+
+Needs Python 3.12 or newer, on Linux or macOS. The package is `databay-cli`; the `databay` project on
+PyPI is unrelated.
+
+Until the first PyPI release, install it from the repository:
+
+```bash
+uv tool install "git+https://github.com/data-burst/databay-clients#subdirectory=python"
+databay login --server https://<host>
+databay skill install --target claude
+```
+
+Install, sign in and releases: [docs/cli.md](https://github.com/data-burst/databay-clients/blob/main/docs/cli.md).
+Changes: [CHANGELOG.md](https://github.com/data-burst/databay-clients/blob/main/python/CHANGELOG.md).
+
+Licensed under Apache-2.0: see the `LICENSE` file in the package.

databay_cli-0.1.0/pyproject.toml

@@ -0,0 +1,113 @@
+[project]
+name = "databay-cli"
+version = "0.1.0"
+description = "Databay SDK and the databay CLI, generated from the Databay client contract"
+readme = "README.md"
+requires-python = ">=3.12"
+license = "Apache-2.0"
+classifiers = [
+    "Operating System :: POSIX :: Linux",
+    "Operating System :: MacOS",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+]
+dependencies = [
+    "click>=8.1.7,<9",
+    "httpx>=0.27.2,<1",
+    "keyring>=25.5.0,<26",
+    "platformdirs>=4.3.6,<5",
+    "pydantic>=2.9.2,<3",
+    "rich>=13.9.4",
+]
+
+[project.urls]
+Homepage = "https://databurst.tech"
+Repository = "https://github.com/data-burst/databay-clients"
+Changelog = "https://github.com/data-burst/databay-clients/blob/main/python/CHANGELOG.md"
+
+[project.scripts]
+databay = "databay.cli.main:main"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.3.4",
+    "pyyaml>=6.0.2",
+    "ruff>=0.15.12",
+]
+
+[build-system]
+# Exact, so the wheel a tag publishes is built by the backend the PR was tested with.
+requires = ["hatchling==1.32.4"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/databay"]
+
+# python-semantic-release, run by the release workflow from python/; see docs/cli.md.
+[tool.semantic_release]
+tag_format = "python/v{version}"
+commit_message = "chore(release): databay-cli v{version} [skip ci]"
+# Start at 0.x like the unreleased package: without it, the first release is 1.0.0.
+allow_zero_version = true
+# release_client.py owns the version: pyproject.toml, uv.lock and the generated version.py.
+build_command = "python3 tools/release_client.py stamp \"$NEW_VERSION\""
+# semantic-release stages these from the repository root, unlike the changelog, which it finds from python/.
+assets = ["python/pyproject.toml", "python/uv.lock", "python/src/databay/version.py"]
+
+[tool.semantic_release.changelog]
+mode = "update"
+
+[tool.semantic_release.changelog.default_templates]
+# The first release would otherwise list every commit since the repository began.
+mask_initial_release = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-ra"
+
+[tool.ruff]
+line-length = 120
+# Generated by tools/gen_client.py; the regeneration check owns them.
+extend-exclude = [
+    "src/databay/models",
+    "src/databay/operations",
+    "src/databay/resources",
+    "src/databay/cli/commands",
+    "src/databay/api.py",
+    "src/databay/spec.py",
+    "src/databay/error_codes.py",
+    "src/databay/version.py",
+]
+
+[tool.ruff.lint]
+select = ["ALL"]
+ignore = [
+    "D1",
+    "D203",
+    "D211",
+    "D212",
+    "COM812",
+    "ISC001",
+    "EM101",
+    "EM102",
+    "TRY003",
+    "CPY001",
+    "S101",
+    "PLR0913",
+    "FBT001",
+    "FBT002",
+    # Docstrings say what a function returns ("The project ``op`` is sent for.").
+    "D401",
+    # The exception names are part of the SDK's API (DatabayServerUnavailable, DatabayResponseInvalid).
+    "N818",
+    "PLR0917",
+    "C901",
+    "PLR0912",
+    "PLR0915",
+]
+
+[tool.ruff.lint.per-file-ignores]
+# Command-line scripts run by path: they print their result, the type mapping returns early per case, and
+# the generator imports the client's runtime modules only after registering the package namespace.
+"tools/**" = ["T201", "INP001", "PLR0911", "PLC0415"]
+"tests/**" = ["ANN", "D", "INP001", "PLR2004", "S105", "S106", "S603", "S607", "SLF001", "ARG001", "PT011", "PLC0415", "TC002", "TC003"]

databay_cli-0.1.0/src/databay/__init__.py

@@ -0,0 +1,5 @@
+"""Databay SDK and CLI: ``from databay import Databay``."""
+
+from .sdk import Databay
+
+__all__ = ["Databay"]

databay_cli-0.1.0/src/databay/__main__.py

@@ -0,0 +1,7 @@
+"""Run ``python -m databay`` like the ``databay`` command."""
+
+import sys
+
+from databay.cli.main import main
+
+sys.exit(main())

databay_cli-0.1.0/src/databay/agent_skill.py

@@ -0,0 +1,184 @@
+"""
+The agent skill that ships in ``databay/skill/``: where each agent loads it, and installing it there.
+
+The installed ``SKILL.md`` carries the CLI version in its frontmatter (``metadata``), so
+``databay status`` can tell a copy from another CLI version. Standard library only.
+"""
+
+from __future__ import annotations
+
+import re
+import shutil
+import uuid
+from dataclasses import dataclass
+from pathlib import Path
+from typing import Literal
+
+from databay.errors import DatabayError, DatabayUsageError
+
+Scope = Literal["user", "project"]
+SCOPES: tuple[Scope, ...] = ("user", "project")
+
+#: Each supported agent's skills folder, under the home (user scope) or the working directory
+#: (project scope). Codex reads ``~/.agents/skills`` and ``.agents/skills`` from the working
+#: directory up to the project root (openai/codex ``codex-rs/ext/skills/src/host_roots.rs``).
+TARGETS: dict[str, Path] = {"claude": Path(".claude") / "skills", "codex": Path(".agents") / "skills"}
+
+SKILL_NAME = "databay"
+VERSION_KEY = "databay-cli-version"
+SOURCE = Path(__file__).resolve().parent / "skill"
+_VERSION_LINE = re.compile(rf"^\s+{re.escape(VERSION_KEY)}:\s*\"?([^\"\s]+)\"?\s*$", re.MULTILINE)
+
+
+@dataclass(frozen=True, slots=True)
+class Installed:
+    """
+    A skill folder found at ``path``.
+
+    ``version`` is the CLI version its ``SKILL.md`` records; when it is ``None``, ``problem`` says
+    why (no ``SKILL.md``, unreadable, no frontmatter, or no version in it).
+    """
+
+    target: str
+    scope: Scope
+    path: Path
+    version: str | None
+    problem: str | None
+
+
+def skill_dir(target: str, scope: Scope, *, home: Path, cwd: Path) -> Path:
+    """The folder ``target`` loads the skill from; an unknown target is ``unsupported_target``."""
+    if target not in TARGETS:
+        raise DatabayUsageError(
+            f"no skill format for target {target!r}; supported targets: {', '.join(TARGETS)}",
+            code="unsupported_target",
+            details={"target": target},
+        )
+    base = home if scope == "user" else cwd
+    return base / TARGETS[target] / SKILL_NAME
+
+
+def _present(path: Path) -> bool:
+    """Something is at ``path``: a folder, a file or a symlink, broken or not."""
+    return path.exists() or path.is_symlink()
+
+
+def _frontmatter_end(text: str) -> int | None:
+    """The index of the closing ``---`` line of ``text``'s frontmatter, or ``None`` when it has none."""
+    if not text.startswith("---\n"):
+        return None
+    end = text.find("\n---\n", 3)
+    return end if end >= 0 else None
+
+
+def rendered_skill(version: str) -> str:
+    """The packaged ``SKILL.md`` with ``version`` added to its frontmatter as ``metadata.databay-cli-version``."""
+    path = SOURCE / "SKILL.md"
+    text = path.read_text(encoding="utf-8")
+    end = _frontmatter_end(text)
+    if end is None:
+        raise DatabayError(f"{path} has no --- frontmatter")
+    if re.search(r"^metadata:", text[:end], re.MULTILINE):
+        raise DatabayError(f"{path} declares metadata itself; the installer writes that block")
+    return f'{text[:end]}\nmetadata:\n  {VERSION_KEY}: "{version}"{text[end:]}'
+
+
+def read_installed(target: str, scope: Scope, path: Path) -> Installed:
+    """The copy at ``path``: the version its ``SKILL.md`` records, or the reason none could be read."""
+    skill = path / "SKILL.md"
+    try:
+        # CRLF is accepted: an editor on another platform may have rewritten the file.
+        text = skill.read_text(encoding="utf-8").replace("\r\n", "\n")
+    except FileNotFoundError:
+        return Installed(target, scope, path, None, f"{skill} does not exist")
+    except (OSError, UnicodeDecodeError) as exc:
+        return Installed(target, scope, path, None, f"{skill} cannot be read ({type(exc).__name__})")
+    end = _frontmatter_end(text)
+    if end is None:
+        return Installed(target, scope, path, None, f"{skill} has no --- frontmatter")
+    found = _VERSION_LINE.search(text[:end])
+    if found is None:
+        return Installed(target, scope, path, None, f"{skill} records no metadata.{VERSION_KEY}")
+    return Installed(target, scope, path, found.group(1), None)
+
+
+def project_dirs(*, home: Path, cwd: Path) -> list[Path]:
+    """
+    ``cwd`` and its parents, where a project-scope copy may sit, nearest first.
+
+    The walk stops at the home: a copy there is the user-scope one.
+    """
+    found = []
+    for directory in [cwd, *cwd.parents]:
+        if directory == home or directory in home.parents:
+            break
+        found.append(directory)
+    return found
+
+
+def find_installed(*, home: Path, cwd: Path) -> list[Installed]:
+    """Every installed copy: per target, the user one, then project ones from ``cwd`` up."""
+    bases: list[tuple[Scope, Path]] = [("user", home), *[("project", d) for d in project_dirs(home=home, cwd=cwd)]]
+    found = []
+    for target, folder in TARGETS.items():
+        for scope, base in bases:
+            path = base / folder / SKILL_NAME
+            if _present(path):
+                found.append(read_installed(target, scope, path))
+    return found
+
+
+def install(
+    target: str, scope: Scope, *, force: bool, version: str, home: Path, cwd: Path
+) -> tuple[Path, Installed | None]:
+    """
+    Write the skill (``SKILL.md`` and ``references/``) where ``target`` loads it.
+
+    Returns the folder it wrote and the copy it replaced, if any. A copy from another version
+    (or of no readable version) is replaced only with ``force``; otherwise it is ``skill_exists``.
+    The new copy is staged beside the old one and swapped in; a failed swap puts the old one back.
+    """
+    destination = skill_dir(target, scope, home=home, cwd=cwd)
+    previous = read_installed(target, scope, destination) if _present(destination) else None
+    if previous is not None and previous.version != version and not force:
+        installed = previous.version or f"an unknown version ({previous.problem})"
+        raise DatabayUsageError(
+            f"{destination} holds the databay skill of CLI {installed}; this CLI is {version}",
+            code="skill_exists",
+            next_command=f"databay skill install --target {target} --scope {scope} --force",
+            details={"path": str(destination), "installed_version": previous.version, "cli_version": version},
+        )
+    staging = destination.parent / f".{SKILL_NAME}-new-{uuid.uuid4().hex}"
+    try:
+        destination.parent.mkdir(parents=True, exist_ok=True)
+        shutil.copytree(SOURCE / "references", staging / "references")
+        (staging / "SKILL.md").write_text(rendered_skill(version), encoding="utf-8")
+        _swap(staging, destination, has_previous=previous is not None)
+    except OSError as exc:
+        raise DatabayError(
+            f"could not write the skill to {destination}: {type(exc).__name__}: {exc.strerror or exc}",
+            code="skill_write_failed",
+            details={"path": str(destination)},
+        ) from None
+    finally:
+        if staging.exists():
+            shutil.rmtree(staging)
+    return destination, previous
+
+
+def _swap(staging: Path, destination: Path, *, has_previous: bool) -> None:
+    """Move ``staging`` to ``destination``; the copy already there is moved aside first and removed after."""
+    if not has_previous:
+        staging.rename(destination)
+        return
+    aside = destination.parent / f".{SKILL_NAME}-old-{uuid.uuid4().hex}"
+    destination.rename(aside)
+    try:
+        staging.rename(destination)
+    except OSError:
+        aside.rename(destination)
+        raise
+    if aside.is_symlink() or not aside.is_dir():
+        aside.unlink()
+        return
+    shutil.rmtree(aside)