docs: few more bits of docs improvement

.agents/skills/update-docs-from-commits/SKILL.md

@@ -21,7 +21,7 @@ Scan recent git history for commits that affect user-facing behavior and draft d
 
 ## Step 1: Identify Relevant Commits
 
-Determine the commit range. The user may provide one explicitly (e.g., "since v0.2.0" or "last 30 commits"). If not, default to commits since the last release tag or the last 50 commits, whichever is smaller.
+Determine the commit range. The user may provide one explicitly (e.g., "since v0.2.0" or "last 30 commits"). If not, default to commits since the head of the main branch.
 
 ```bash
 # Commits since a tag
@@ -95,7 +95,6 @@ Write the doc update following the rules in `docs/CONTRIBUTING.md`. Key reminder
 - **No em dashes** unless used sparingly. Prefer commas or separate sentences.
 - **Start sections with an introductory sentence** that orients the reader.
 - **No superlatives.** Say what the feature does, not how great it is.
-- **One sentence per line** in the source (for clean diffs).
 - **Code examples use `console` language** with `$` prompt prefix.
 - **Include the SPDX header** if creating a new page.
 - **Match existing frontmatter format** if creating a new page.

CONTRIBUTING.md

@@ -42,6 +42,7 @@ Skills live in `.agents/skills/`. Your agent's harness can discover and load the
 | Triage | `triage-issue` | Assess, classify, and route community-filed issues |
 | Platform | `generate-sandbox-policy` | Generate YAML sandbox policies from requirements or API docs |
 | Platform | `tui-development` | Development guide for the ratatui-based terminal UI |
+| Documentation | `update-docs-from-commits` | Scan recent commits and draft doc updates for user-facing changes |
 | Maintenance | `sync-agent-infra` | Detect and fix drift across agent-first infrastructure files |
 | Reference | `sbom` | Generate SBOMs and resolve dependency licenses |
 
@@ -153,14 +154,19 @@ These are the primary `mise` tasks for day-to-day development:
 ## Documentation
 
 If your change affects user-facing behavior (new flags, changed defaults, new features, bug fixes that contradict existing docs), update the relevant pages under `docs/` in the same PR.
-See [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md) for the doc structure, style guide, and formatting rules.
 
-Build and preview docs locally:
+To ensure your doc changes follow NVIDIA documentation style, use the `update-docs-from-commits` skill.
+It scans commits, identifies doc pages that need updates, and drafts content that follows the style guide in `docs/CONTRIBUTING.md`.
+
+To build and preview docs locally:
 
 ```bash
-mise run docs
+mise run docs # to build the docs locally
+mise run docs:serve # to serve locally and automatically rebuild on changes
 ```
 
+See [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md) for more details.
+
 ## Pull Requests
 
 1. Create a feature branch from `main`.

docs/get-started/quickstart.md

@@ -55,17 +55,7 @@ $ uv pip install openshell
 ```
 
 :::{tip}
-To find the CLI reference, run:
-- `openshell --help` to see all available commands.
-- `openshell <command> --help` for detailed usage of any subcommand.
-
-For example:
-
-```console
-$ openshell --help
-$ openshell gateway --help
-$ openshell sandbox create --help
-```
+Run `openshell --help` in your terminal to see the full CLI reference, including all commands and flags. You can also clone the [NVIDIA OpenShell GitHub repository](https://github.com/NVIDIA/OpenShell) and use the `/openshell-cli` skill to load the CLI reference into your agent.
 :::
 
 ## Deploy a Gateway (Optional)
@@ -78,7 +68,7 @@ To start the gateway explicitly or deploy to a remote host, choose the tab that
 ::::{tab-item} Brev
 
 :::{note}
-Deploy an OpenShell gateway on Brev by clicking **Deploy** on the [OpenShell Launchable](https://brev.nvidia.com/launchable/deploy/now?launchableID=env-3AaK9NmCzWp3pVyUDNNFBt805FT).
+Deploy an OpenShell gateway on Brev by clicking **Deploy** on the [OpenShell Launchable](https://brev.nvidia.com/launchable/deploy/now?launchableID=env-3Ap3tL55zq4a8kew1AuW0FpSLsg).
 :::
 
 After the instance starts running, find the gateway URL in the Brev console under **Using Secure Links**.

docs/index.md

@@ -105,12 +105,10 @@ Install the CLI and create your first sandbox in two commands.
 </div>
 ```
 
-Run `openshell --help` in your terminal to see the full CLI reference, including all commands and flags.
-Run `openshell <command> --help` for detailed usage of any subcommand.
+Run `openshell --help` in your terminal to see the full CLI reference, including all commands and flags. You can also clone the [OpenShell repository](https://github.com/NVIDIA/OpenShell) and use the `/openshell-cli` skill to load the CLI reference into your agent.
 
 Proceed to the [Quickstart](get-started/quickstart.md) for more details.
 
-
 ---
 
 ## Explore