skykoi 2026.3.11 → 2026.3.13

package/docs/cli/agents.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `SkyKoi agents` (list/add/delete/set identity)"
+summary: "CLI reference for `SKYKOI agents` (list/add/delete/set identity)"
 read_when:
   - You want multiple isolated agents (workspaces + routing + auth)
 title: "agents"
 ---
 
-# `SkyKoi agents`
+# `SKYKOI agents`
 
 Manage isolated agents (workspaces + auth + routing).
 
@@ -17,18 +17,18 @@ Related:
 ## Examples
 
 ```bash
-SkyKoi agents list
-SkyKoi agents add work --workspace ~/.skykoi/workspace-work
-SkyKoi agents set-identity --workspace ~/.skykoi/workspace --from-identity
-SkyKoi agents set-identity --agent main --avatar avatars/SkyKoi.png
-SkyKoi agents delete work
+SKYKOI agents list
+SKYKOI agents add work --workspace ~/.SKYKOI/workspace-work
+SKYKOI agents set-identity --workspace ~/.SKYKOI/workspace --from-identity
+SKYKOI agents set-identity --agent main --avatar avatars/SKYKOI.png
+SKYKOI agents delete work
 ```
 
 ## Identity files
 
 Each agent workspace can include an `IDENTITY.md` at the workspace root:
 
-- Example path: `~/.skykoi/workspace/IDENTITY.md`
+- Example path: `~/.SKYKOI/workspace/IDENTITY.md`
 - `set-identity --from-identity` reads from the workspace root (or an explicit `--identity-file`)
 
 Avatar paths resolve relative to the workspace root.
@@ -45,13 +45,13 @@ Avatar paths resolve relative to the workspace root.
 Load from `IDENTITY.md`:
 
 ```bash
-SkyKoi agents set-identity --workspace ~/.skykoi/workspace --from-identity
+SKYKOI agents set-identity --workspace ~/.SKYKOI/workspace --from-identity
 ```
 
 Override fields explicitly:
 
 ```bash
-SkyKoi agents set-identity --agent main --name "SkyKoi" --emoji "🦞" --avatar avatars/SkyKoi.png
+SKYKOI agents set-identity --agent main --name "SKYKOI" --emoji "🦞" --avatar avatars/SKYKOI.png
 ```
 
 Config sample:
@@ -63,10 +63,10 @@ Config sample:
       {
         id: "main",
         identity: {
-          name: "SkyKoi",
+          name: "SKYKOI",
           theme: "space lobster",
           emoji: "🦞",
-          avatar: "avatars/SkyKoi.png",
+          avatar: "avatars/SKYKOI.png",
         },
       },
     ],

package/docs/cli/approvals.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi approvals` (exec approvals for gateway or node hosts)"
+summary: "CLI reference for `SKYKOI approvals` (exec approvals for gateway or node hosts)"
 read_when:
   - You want to edit exec approvals from the CLI
   - You need to manage allowlists on gateway or node hosts
 title: "approvals"
 ---
 
-# `SkyKoi approvals`
+# `SKYKOI approvals`
 
 Manage exec approvals for the **local host**, **gateway host**, or a **node host**.
 By default, commands target the local approvals file on disk. Use `--gateway` to target the gateway, or `--node` to target a specific node.
@@ -19,32 +19,32 @@ Related:
 ## Common commands
 
 ```bash
-SkyKoi approvals get
-SkyKoi approvals get --node <id|name|ip>
-SkyKoi approvals get --gateway
+SKYKOI approvals get
+SKYKOI approvals get --node <id|name|ip>
+SKYKOI approvals get --gateway
 ```
 
 ## Replace approvals from a file
 
 ```bash
-SkyKoi approvals set --file ./exec-approvals.json
-SkyKoi approvals set --node <id|name|ip> --file ./exec-approvals.json
-SkyKoi approvals set --gateway --file ./exec-approvals.json
+SKYKOI approvals set --file ./exec-approvals.json
+SKYKOI approvals set --node <id|name|ip> --file ./exec-approvals.json
+SKYKOI approvals set --gateway --file ./exec-approvals.json
 ```
 
 ## Allowlist helpers
 
 ```bash
-SkyKoi approvals allowlist add "~/Projects/**/bin/rg"
-SkyKoi approvals allowlist add --agent main --node <id|name|ip> "/usr/bin/uptime"
-SkyKoi approvals allowlist add --agent "*" "/usr/bin/uname"
+SKYKOI approvals allowlist add "~/Projects/**/bin/rg"
+SKYKOI approvals allowlist add --agent main --node <id|name|ip> "/usr/bin/uptime"
+SKYKOI approvals allowlist add --agent "*" "/usr/bin/uname"
 
-SkyKoi approvals allowlist remove "~/Projects/**/bin/rg"
+SKYKOI approvals allowlist remove "~/Projects/**/bin/rg"
 ```
 
 ## Notes
 
-- `--node` uses the same resolver as `SkyKoi nodes` (id, name, ip, or id prefix).
+- `--node` uses the same resolver as `SKYKOI nodes` (id, name, ip, or id prefix).
 - `--agent` defaults to `"*"`, which applies to all agents.
 - The node host must advertise `system.execApprovals.get/set` (macOS app or headless node host).
-- Approvals files are stored per host at `~/.skykoi/exec-approvals.json`.
+- Approvals files are stored per host at `~/.SKYKOI/exec-approvals.json`.

package/docs/cli/browser.md

@@ -1,15 +1,15 @@
 ---
-summary: "CLI reference for `skykoi browser` (profiles, tabs, actions, extension relay)"
+summary: "CLI reference for `SKYKOI browser` (profiles, tabs, actions, extension relay)"
 read_when:
-  - You use `skykoi browser` and want examples for common tasks
+  - You use `SKYKOI browser` and want examples for common tasks
   - You want to control a browser running on another machine via a node host
   - You want to use the Chrome extension relay (attach/detach via toolbar button)
 title: "browser"
 ---
 
-# `skykoi browser`
+# `SKYKOI browser`
 
-Manage SkyKoi’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
+Manage SKYKOI’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
 
 Related:
 
@@ -27,38 +27,38 @@ Related:
 ## Quick start (local)
 
 ```bash
-skykoi browser --browser-profile chrome tabs
-skykoi browser --browser-profile SkyKoi start
-skykoi browser --browser-profile SkyKoi open https://example.com
-skykoi browser --browser-profile SkyKoi snapshot
+SKYKOI browser --browser-profile chrome tabs
+SKYKOI browser --browser-profile SKYKOI start
+SKYKOI browser --browser-profile SKYKOI open https://example.com
+SKYKOI browser --browser-profile SKYKOI snapshot
 ```
 
 ## Profiles
 
 Profiles are named browser routing configs. In practice:
 
-- `SkyKoi`: launches/attaches to a dedicated SkyKoi-managed Chrome instance (isolated user data dir).
+- `SKYKOI`: launches/attaches to a dedicated SKYKOI-managed Chrome instance (isolated user data dir).
 - `chrome`: controls your existing Chrome tab(s) via the Chrome extension relay.
 
 ```bash
-skykoi browser profiles
-skykoi browser create-profile --name work --color "#FF5A36"
-skykoi browser delete-profile --name work
+SKYKOI browser profiles
+SKYKOI browser create-profile --name work --color "#FF5A36"
+SKYKOI browser delete-profile --name work
 ```
 
 Use a specific profile:
 
 ```bash
-skykoi browser --browser-profile work tabs
+SKYKOI browser --browser-profile work tabs
 ```
 
 ## Tabs
 
 ```bash
-skykoi browser tabs
-skykoi browser open https://docs.skykoi.com
-skykoi browser focus <targetId>
-skykoi browser close <targetId>
+SKYKOI browser tabs
+SKYKOI browser open https://docs.SKYKOI.com
+SKYKOI browser focus <targetId>
+SKYKOI browser close <targetId>
 ```
 
 ## Snapshot / screenshot / actions
@@ -66,21 +66,21 @@ skykoi browser close <targetId>
 Snapshot:
 
 ```bash
-skykoi browser snapshot
+SKYKOI browser snapshot
 ```
 
 Screenshot:
 
 ```bash
-skykoi browser screenshot
+SKYKOI browser screenshot
 ```
 
 Navigate/click/type (ref-based UI automation):
 
 ```bash
-skykoi browser navigate https://example.com
-skykoi browser click <ref>
-skykoi browser type <ref> "hello"
+SKYKOI browser navigate https://example.com
+SKYKOI browser click <ref>
+SKYKOI browser type <ref> "hello"
 ```
 
 ## Chrome extension relay (attach via toolbar button)
@@ -90,8 +90,8 @@ This mode lets the agent control an existing Chrome tab that you attach manually
 Install the unpacked extension to a stable path:
 
 ```bash
-skykoi browser extension install
-skykoi browser extension path
+SKYKOI browser extension install
+SKYKOI browser extension path
 ```
 
 Then Chrome → `chrome://extensions` → enable “Developer mode” → “Load unpacked” → select the printed folder.

package/docs/cli/channels.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi channels` (accounts, status, login/logout, logs)"
+summary: "CLI reference for `SKYKOI channels` (accounts, status, login/logout, logs)"
 read_when:
   - You want to add/remove channel accounts (WhatsApp/Telegram/Discord/Google Chat/Slack/Mattermost (plugin)/Signal/iMessage)
   - You want to check channel status or tail channel logs
 title: "channels"
 ---
 
-# `SkyKoi channels`
+# `SKYKOI channels`
 
 Manage chat channel accounts and their runtime status on the Gateway.
 
@@ -18,43 +18,43 @@ Related docs:
 ## Common commands
 
 ```bash
-SkyKoi channels list
-SkyKoi channels status
-SkyKoi channels capabilities
-SkyKoi channels capabilities --channel discord --target channel:123
-SkyKoi channels resolve --channel slack "#general" "@jane"
-SkyKoi channels logs --channel all
+SKYKOI channels list
+SKYKOI channels status
+SKYKOI channels capabilities
+SKYKOI channels capabilities --channel discord --target channel:123
+SKYKOI channels resolve --channel slack "#general" "@jane"
+SKYKOI channels logs --channel all
 ```
 
 ## Add / remove accounts
 
 ```bash
-SkyKoi channels add --channel telegram --token <bot-token>
-SkyKoi channels remove --channel telegram --delete
+SKYKOI channels add --channel telegram --token <bot-token>
+SKYKOI channels remove --channel telegram --delete
 ```
 
-Tip: `SkyKoi channels add --help` shows per-channel flags (token, app token, signal-cli paths, etc).
+Tip: `SKYKOI channels add --help` shows per-channel flags (token, app token, signal-cli paths, etc).
 
 ## Login / logout (interactive)
 
 ```bash
-SkyKoi channels login --channel whatsapp
-SkyKoi channels logout --channel whatsapp
+SKYKOI channels login --channel whatsapp
+SKYKOI channels logout --channel whatsapp
 ```
 
 ## Troubleshooting
 
-- Run `SkyKoi status --deep` for a broad probe.
-- Use `SkyKoi doctor` for guided fixes.
-- `SkyKoi channels list` prints `Claude: HTTP 403 ... user:profile` → usage snapshot needs the `user:profile` scope. Use `--no-usage`, or provide a claude.ai session key (`CLAUDE_WEB_SESSION_KEY` / `CLAUDE_WEB_COOKIE`), or re-auth via Claude Code CLI.
+- Run `SKYKOI status --deep` for a broad probe.
+- Use `SKYKOI doctor` for guided fixes.
+- `SKYKOI channels list` prints `Claude: HTTP 403 ... user:profile` → usage snapshot needs the `user:profile` scope. Use `--no-usage`, or provide a claude.ai session key (`CLAUDE_WEB_SESSION_KEY` / `CLAUDE_WEB_COOKIE`), or re-auth via Claude Code CLI.
 
 ## Capabilities probe
 
 Fetch provider capability hints (intents/scopes where available) plus static feature support:
 
 ```bash
-SkyKoi channels capabilities
-SkyKoi channels capabilities --channel discord --target channel:123
+SKYKOI channels capabilities
+SKYKOI channels capabilities --channel discord --target channel:123
 ```
 
 Notes:
@@ -68,9 +68,9 @@ Notes:
 Resolve channel/user names to IDs using the provider directory:
 
 ```bash
-SkyKoi channels resolve --channel slack "#general" "@jane"
-SkyKoi channels resolve --channel discord "My Server/#support" "@someone"
-SkyKoi channels resolve --channel matrix "Project Room"
+SKYKOI channels resolve --channel slack "#general" "@jane"
+SKYKOI channels resolve --channel discord "My Server/#support" "@someone"
+SKYKOI channels resolve --channel matrix "Project Room"
 ```
 
 Notes:

package/docs/cli/config.md

@@ -1,23 +1,23 @@
 ---
-summary: "CLI reference for `SkyKoi config` (get/set/unset config values)"
+summary: "CLI reference for `SKYKOI config` (get/set/unset config values)"
 read_when:
   - You want to read or edit config non-interactively
 title: "config"
 ---
 
-# `SkyKoi config`
+# `SKYKOI config`
 
 Config helpers: get/set/unset values by path. Run without a subcommand to open
-the configure wizard (same as `SkyKoi configure`).
+the configure wizard (same as `SKYKOI configure`).
 
 ## Examples
 
 ```bash
-SkyKoi config get browser.executablePath
-SkyKoi config set browser.executablePath "/usr/bin/google-chrome"
-SkyKoi config set agents.defaults.heartbeat.every "2h"
-SkyKoi config set agents.list[0].tools.exec.node "node-id-or-name"
-SkyKoi config unset tools.web.search.apiKey
+SKYKOI config get browser.executablePath
+SKYKOI config set browser.executablePath "/usr/bin/google-chrome"
+SKYKOI config set agents.defaults.heartbeat.every "2h"
+SKYKOI config set agents.list[0].tools.exec.node "node-id-or-name"
+SKYKOI config unset tools.web.search.apiKey
 ```
 
 ## Paths
@@ -25,15 +25,15 @@ SkyKoi config unset tools.web.search.apiKey
 Paths use dot or bracket notation:
 
 ```bash
-SkyKoi config get agents.defaults.workspace
-SkyKoi config get agents.list[0].id
+SKYKOI config get agents.defaults.workspace
+SKYKOI config get agents.list[0].id
 ```
 
 Use the agent list index to target a specific agent:
 
 ```bash
-SkyKoi config get agents.list
-SkyKoi config set agents.list[1].tools.exec.node "node-id-or-name"
+SKYKOI config get agents.list
+SKYKOI config set agents.list[1].tools.exec.node "node-id-or-name"
 ```
 
 ## Values
@@ -42,9 +42,9 @@ Values are parsed as JSON5 when possible; otherwise they are treated as strings.
 Use `--json` to require JSON5 parsing.
 
 ```bash
-SkyKoi config set agents.defaults.heartbeat.every "0m"
-SkyKoi config set gateway.port 19001 --json
-SkyKoi config set channels.whatsapp.groups '["*"]' --json
+SKYKOI config set agents.defaults.heartbeat.every "0m"
+SKYKOI config set gateway.port 19001 --json
+SKYKOI config set channels.whatsapp.groups '["*"]' --json
 ```
 
 Restart the gateway after edits.

package/docs/cli/configure.md

@@ -1,19 +1,19 @@
 ---
-summary: "CLI reference for `SkyKoi configure` (interactive configuration prompts)"
+summary: "CLI reference for `SKYKOI configure` (interactive configuration prompts)"
 read_when:
   - You want to tweak credentials, devices, or agent defaults interactively
 title: "configure"
 ---
 
-# `SkyKoi configure`
+# `SKYKOI configure`
 
 Interactive prompt to set up credentials, devices, and agent defaults.
 
 Note: The **Model** section now includes a multi-select for the
 `agents.defaults.models` allowlist (what shows up in `/model` and the model picker).
 
-Tip: `SkyKoi config` without a subcommand opens the same wizard. Use
-`SkyKoi config get|set|unset` for non-interactive edits.
+Tip: `SKYKOI config` without a subcommand opens the same wizard. Use
+`SKYKOI config get|set|unset` for non-interactive edits.
 
 Related:
 
@@ -28,6 +28,6 @@ Notes:
 ## Examples
 
 ```bash
-SkyKoi configure
-SkyKoi configure --section models --section channels
+SKYKOI configure
+SKYKOI configure --section models --section channels
 ```

package/docs/cli/cron.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi cron` (schedule and run background jobs)"
+summary: "CLI reference for `SKYKOI cron` (schedule and run background jobs)"
 read_when:
   - You want scheduled jobs and wakeups
   - You’re debugging cron execution and logs
 title: "cron"
 ---
 
-# `SkyKoi cron`
+# `SKYKOI cron`
 
 Manage cron jobs for the Gateway scheduler.
 
@@ -14,7 +14,7 @@ Related:
 
 - Cron jobs: [Cron jobs](/automation/cron-jobs)
 
-Tip: run `SkyKoi cron --help` for the full command surface.
+Tip: run `SKYKOI cron --help` for the full command surface.
 
 Note: isolated `cron add` jobs default to `--announce` delivery. Use `--no-deliver` to keep
 output internal. `--deliver` remains as a deprecated alias for `--announce`.
@@ -26,17 +26,17 @@ Note: one-shot (`--at`) jobs delete after success by default. Use `--keep-after-
 Update delivery settings without changing the message:
 
 ```bash
-SkyKoi cron edit <job-id> --announce --channel telegram --to "123456789"
+SKYKOI cron edit <job-id> --announce --channel telegram --to "123456789"
 ```
 
 Disable delivery for an isolated job:
 
 ```bash
-SkyKoi cron edit <job-id> --no-deliver
+SKYKOI cron edit <job-id> --no-deliver
 ```
 
 Announce to a specific channel:
 
 ```bash
-SkyKoi cron edit <job-id> --announce --channel slack --to "channel:C1234567890"
+SKYKOI cron edit <job-id> --announce --channel slack --to "channel:C1234567890"
 ```

package/docs/cli/dashboard.md

@@ -1,16 +1,16 @@
 ---
-summary: "CLI reference for `SkyKoi dashboard` (open the Control UI)"
+summary: "CLI reference for `SKYKOI dashboard` (open the Control UI)"
 read_when:
   - You want to open the Control UI with your current token
   - You want to print the URL without launching a browser
 title: "dashboard"
 ---
 
-# `SkyKoi dashboard`
+# `SKYKOI dashboard`
 
 Open the Control UI using your current auth.
 
 ```bash
-SkyKoi dashboard
-SkyKoi dashboard --no-open
+SKYKOI dashboard
+SKYKOI dashboard --no-open
 ```

package/docs/cli/devices.md

@@ -1,56 +1,56 @@
 ---
-summary: "CLI reference for `SkyKoi devices` (device pairing + token rotation/revocation)"
+summary: "CLI reference for `SKYKOI devices` (device pairing + token rotation/revocation)"
 read_when:
   - You are approving device pairing requests
   - You need to rotate or revoke device tokens
 title: "devices"
 ---
 
-# `SkyKoi devices`
+# `SKYKOI devices`
 
 Manage device pairing requests and device-scoped tokens.
 
 ## Commands
 
-### `SkyKoi devices list`
+### `SKYKOI devices list`
 
 List pending pairing requests and paired devices.
 
 ```
-SkyKoi devices list
-SkyKoi devices list --json
+SKYKOI devices list
+SKYKOI devices list --json
 ```
 
-### `SkyKoi devices approve <requestId>`
+### `SKYKOI devices approve <requestId>`
 
 Approve a pending device pairing request.
 
 ```
-SkyKoi devices approve <requestId>
+SKYKOI devices approve <requestId>
 ```
 
-### `SkyKoi devices reject <requestId>`
+### `SKYKOI devices reject <requestId>`
 
 Reject a pending device pairing request.
 
 ```
-SkyKoi devices reject <requestId>
+SKYKOI devices reject <requestId>
 ```
 
-### `SkyKoi devices rotate --device <id> --role <role> [--scope <scope...>]`
+### `SKYKOI devices rotate --device <id> --role <role> [--scope <scope...>]`
 
 Rotate a device token for a specific role (optionally updating scopes).
 
 ```
-SkyKoi devices rotate --device <deviceId> --role operator --scope operator.read --scope operator.write
+SKYKOI devices rotate --device <deviceId> --role operator --scope operator.read --scope operator.write
 ```
 
-### `SkyKoi devices revoke --device <id> --role <role>`
+### `SKYKOI devices revoke --device <id> --role <role>`
 
 Revoke a device token for a specific role.
 
 ```
-SkyKoi devices revoke --device <deviceId> --role node
+SKYKOI devices revoke --device <deviceId> --role node
 ```
 
 ## Common options

package/docs/cli/directory.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi directory` (self, peers, groups)"
+summary: "CLI reference for `SKYKOI directory` (self, peers, groups)"
 read_when:
   - You want to look up contacts/groups/self ids for a channel
   - You are developing a channel directory adapter
 title: "directory"
 ---
 
-# `SkyKoi directory`
+# `SKYKOI directory`
 
 Directory lookups for channels that support it (contacts/peers, groups, and “me”).
 
@@ -18,15 +18,15 @@ Directory lookups for channels that support it (contacts/peers, groups, and “m
 
 ## Notes
 
-- `directory` is meant to help you find IDs you can paste into other commands (especially `SkyKoi message send --target ...`).
+- `directory` is meant to help you find IDs you can paste into other commands (especially `SKYKOI message send --target ...`).
 - For many channels, results are config-backed (allowlists / configured groups) rather than a live provider directory.
 - Default output is `id` (and sometimes `name`) separated by a tab; use `--json` for scripting.
 
 ## Using results with `message send`
 
 ```bash
-SkyKoi directory peers list --channel slack --query "U0"
-SkyKoi message send --channel slack --target user:U012ABCDEF --message "hello"
+SKYKOI directory peers list --channel slack --query "U0"
+SKYKOI message send --channel slack --target user:U012ABCDEF --message "hello"
 ```
 
 ## ID formats (by channel)
@@ -43,21 +43,21 @@ SkyKoi message send --channel slack --target user:U012ABCDEF --message "hello"
 ## Self (“me”)
 
 ```bash
-SkyKoi directory self --channel zalouser
+SKYKOI directory self --channel zalouser
 ```
 
 ## Peers (contacts/users)
 
 ```bash
-SkyKoi directory peers list --channel zalouser
-SkyKoi directory peers list --channel zalouser --query "name"
-SkyKoi directory peers list --channel zalouser --limit 50
+SKYKOI directory peers list --channel zalouser
+SKYKOI directory peers list --channel zalouser --query "name"
+SKYKOI directory peers list --channel zalouser --limit 50
 ```
 
 ## Groups
 
 ```bash
-SkyKoi directory groups list --channel zalouser
-SkyKoi directory groups list --channel zalouser --query "work"
-SkyKoi directory groups members --channel zalouser --group-id <id>
+SKYKOI directory groups list --channel zalouser
+SKYKOI directory groups list --channel zalouser --query "work"
+SKYKOI directory groups members --channel zalouser --group-id <id>
 ```

package/docs/cli/dns.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi dns` (wide-area discovery helpers)"
+summary: "CLI reference for `SKYKOI dns` (wide-area discovery helpers)"
 read_when:
   - You want wide-area discovery (DNS-SD) via Tailscale + CoreDNS
-  - You’re setting up split DNS for a custom discovery domain (example: SkyKoi.internal)
+  - You’re setting up split DNS for a custom discovery domain (example: SKYKOI.internal)
 title: "dns"
 ---
 
-# `SkyKoi dns`
+# `SKYKOI dns`
 
 DNS helpers for wide-area discovery (Tailscale + CoreDNS). Currently focused on macOS + Homebrew CoreDNS.
 
@@ -18,6 +18,6 @@ Related:
 ## Setup
 
 ```bash
-SkyKoi dns setup
-SkyKoi dns setup --apply
+SKYKOI dns setup
+SKYKOI dns setup --apply
 ```

package/docs/cli/docs.md

@@ -1,15 +1,15 @@
 ---
-summary: "CLI reference for `SkyKoi docs` (search the live docs index)"
+summary: "CLI reference for `SKYKOI docs` (search the live docs index)"
 read_when:
-  - You want to search the live SkyKoi docs from the terminal
+  - You want to search the live SKYKOI docs from the terminal
 title: "docs"
 ---
 
-# `SkyKoi docs`
+# `SKYKOI docs`
 
 Search the live docs index.
 
 ```bash
-SkyKoi docs browser extension
-SkyKoi docs sandbox allowHostControl
+SKYKOI docs browser extension
+SKYKOI docs sandbox allowHostControl
 ```