@getfrontline/cli 1.0.1 → 1.0.4

package/dist/skills/max-auth/SKILL.md

@@ -1,76 +1,76 @@
----
-name: max-auth
-description: Manage Max CLI authentication — store per-user API key (synced with Frontline CLI), sign out, and inspect the active profile. Use when the user needs Max terminal auth, whoami, or clearing credentials.
----
-
-## Prerequisites
-
-- The `max` CLI must be installed (`npm i -g @frontline/cli` — provides both `frontline` and `max` binaries).
-- A **per-user API key** from the Frontline web app (Settings → API keys). The browser SSO (Firebase) flow is **paused** in the CLI; `MAX_CLI_AUTH_URL` is not required for the current flow.
-
-## How credentials work
-
-- `max auth login <api-key>` saves the same key to the **Max** store (`max-cli`) and the **Frontline** store (`frontline-cli`) under the **same profile name**, so `max` and `frontline` stay aligned.
-- `max` commands call the **Public API** (`…/public/v1/max/...`) with `Authorization: Bearer <apiKey>` (USER key, same as SoR).
-- Public API base URL: same as `frontline` — `FRONTLINE_BASE_URL`, profile `baseUrl`, or `--base-url` on each command (`max auth login --base-url …` persists it on the Frontline profile).
-- API key resolution: `--api-key` → `MAX_API_KEY` / `FRONTLINE_API_KEY` → Max profile `apiKey` → Frontline profile `apiKey` (same name).
-
-## Commands
-
-### Sign in (save API key)
-
-```bash
-max auth login <api-key> [--profile <name>] [--base-url <url>]
-```
-
-| Option             | Description                                                                                          |
-| ------------------ | ---------------------------------------------------------------------------------------------------- |
-| `<api-key>`        | Per-user API key (required argument)                                                                 |
-| `--profile <name>` | Profile to save under (default: current; if set, also switches active profile for Max and Frontline) |
-| `--base-url <url>` | Public API root for **both** `max` and `frontline` on that profile (must end with `/public/v1`)      |
-
-**Examples:**
-
-```bash
-max auth login flk_abc123
-
-max auth login flk_abc123 --profile staging \
-  --base-url https://staging-api.example.com/public/v1
-```
-
-### Sign out
-
-```bash
-max auth logout [--profile <name>] [--keep-frontline]
-```
-
-| Option             | Description                                                    |
-| ------------------ | -------------------------------------------------------------- |
-| `--profile <name>` | Profile to clear (default: current)                            |
-| `--keep-frontline` | Only clear the Max store; leave the matching Frontline profile |
-
-By default, the matching Frontline profile is removed too.
-
-### Check profile / credentials
-
-```bash
-max auth whoami [--json] [--profile <name>]
-```
-
-Shows API key preview, `maxApiBaseUrl`, whether a matching Frontline profile exists, and Max config path (no JWT decode; browser SSO is paused).
-
-### Config path
-
-```bash
-max config-path
-```
-
-## Troubleshooting
-
-- **"No API key saved for profile …"** — run `max auth login <api-key>` or `frontline auth login <api-key>` with the same `--profile`.
-- **"No Max API key found"** — same as above, or set `MAX_API_KEY` / `FRONTLINE_API_KEY`.
-- **401 on Max** — key revoked or wrong; create a new key in the app and run `max auth login` again.
-
-## Browser SSO note
-
-The legacy flow (`max auth login` with no argument, hosted page + localhost callback) is commented out in the package. To restore it later, see git history and `packages/cli/src/max/browserLogin.ts`.
+---
+name: max-auth
+description: Manage Max CLI authentication — store per-user API key (synced with Frontline CLI), sign out, and inspect the active profile. Use when the user needs Max terminal auth, whoami, or clearing credentials.
+---
+
+## Prerequisites
+
+- The `max` CLI must be installed (`npm i -g @frontline/cli` — provides both `frontline` and `max` binaries).
+- A **per-user API key** from the Frontline web app (Settings → API keys). The browser SSO (Firebase) flow is **paused** in the CLI; `MAX_CLI_AUTH_URL` is not required for the current flow.
+
+## How credentials work
+
+- `max auth login <api-key>` saves the same key to the **Max** store (`max-cli`) and the **Frontline** store (`frontline-cli`) under the **same profile name**, so `max` and `frontline` stay aligned.
+- `max` commands call the **Public API** (`…/public/v1/max/...`) with `Authorization: Bearer <apiKey>` (USER key, same as SoR).
+- Public API base URL: same as `frontline` — `FRONTLINE_BASE_URL`, profile `baseUrl`, or `--base-url` on each command (`max auth login --base-url …` persists it on the Frontline profile).
+- API key resolution: `--api-key` → `MAX_API_KEY` / `FRONTLINE_API_KEY` → Max profile `apiKey` → Frontline profile `apiKey` (same name).
+
+## Commands
+
+### Sign in (save API key)
+
+```bash
+max auth login <api-key> [--profile <name>] [--base-url <url>]
+```
+
+| Option             | Description                                                                                          |
+| ------------------ | ---------------------------------------------------------------------------------------------------- |
+| `<api-key>`        | Per-user API key (required argument)                                                                 |
+| `--profile <name>` | Profile to save under (default: current; if set, also switches active profile for Max and Frontline) |
+| `--base-url <url>` | Public API root for **both** `max` and `frontline` on that profile (must end with `/public/v1`)      |
+
+**Examples:**
+
+```bash
+max auth login flk_abc123
+
+max auth login flk_abc123 --profile staging \
+  --base-url https://staging-api.example.com/public/v1
+```
+
+### Sign out
+
+```bash
+max auth logout [--profile <name>] [--keep-frontline]
+```
+
+| Option             | Description                                                    |
+| ------------------ | -------------------------------------------------------------- |
+| `--profile <name>` | Profile to clear (default: current)                            |
+| `--keep-frontline` | Only clear the Max store; leave the matching Frontline profile |
+
+By default, the matching Frontline profile is removed too.
+
+### Check profile / credentials
+
+```bash
+max auth whoami [--json] [--profile <name>]
+```
+
+Shows API key preview, `maxApiBaseUrl`, whether a matching Frontline profile exists, and Max config path (no JWT decode; browser SSO is paused).
+
+### Config path
+
+```bash
+max config-path
+```
+
+## Troubleshooting
+
+- **"No API key saved for profile …"** — run `max auth login <api-key>` or `frontline auth login <api-key>` with the same `--profile`.
+- **"No Max API key found"** — same as above, or set `MAX_API_KEY` / `FRONTLINE_API_KEY`.
+- **401 on Max** — key revoked or wrong; create a new key in the app and run `max auth login` again.
+
+## Browser SSO note
+
+The legacy flow (`max auth login` with no argument, hosted page + localhost callback) is commented out in the package. To restore it later, see git history and `packages/cli/src/max/browserLogin.ts`.

package/dist/skills/max-chat/SKILL.md

@@ -1,111 +1,111 @@
----
-name: max-chat
-description: Send messages to the Max AI assistant and manage conversations from the terminal. Use when the user wants to chat with Max, send a quick question, start a new conversation, or open an interactive chat session.
----
-
-## Prerequisites
-
-- The `max` CLI must be installed (`npm i -g @frontline/cli` — provides both `frontline` and `max` binaries).
-- The user must have a per-user API key saved: `max auth login <api-key>` (or `frontline auth login` on the same profile).
-
-## Commands
-
-### Quick message (shorthand)
-
-```bash
-max "Your question here"
-max --new "Start a fresh conversation"
-```
-
-This is the fastest way to send a single message to Max. It uses the last active conversation by default, or `--new` to start a fresh one.
-
-Calls the **Public API**: `POST /public/v1/max/conversations/message` (Bearer = user API key). Responses use `{ "ok": boolean, "data": ... }`. Default stdout is **one-line JSON**; no spinner lines.
-
-| Flag                   | Description                                                 |
-| ---------------------- | ----------------------------------------------------------- |
-| `--new`                | Start a new conversation instead of continuing the last one |
-| `--conversation <id>`  | Send to a specific conversation ID                          |
-| `--no-wait`            | Do not poll for the assistant reply (fire and forget)       |
-| `--timeout <seconds>`  | Max seconds to wait for assistant reply (default: 60)       |
-| `--json`               | Print only the POST response JSON (no poll)                 |
-| `--pretty`             | Print assistant plain text from `data` instead of JSON      |
-| `--profile <name>`     | Use a specific Max CLI profile                              |
-| `--base-url <url>`     | Override Public API root (…/public/v1) for this run         |
-| `--api-base-url <url>` | Deprecated alias for `--base-url`                           |
-| `--api-key <key>`      | Override per-user API key for this run                      |
-| `--debug`              | Show HTTP request/response diagnostics                      |
-
-**Example:**
-
-```bash
-# Quick question using last conversation
-max "What agents do I have?"
-
-# Start a new conversation
-max --new "Help me set up a new workflow"
-
-# Send to a specific conversation
-max --conversation 123 "Continue from here"
-```
-
-### Send a message (explicit command)
-
-```bash
-max chat send <message...> [--new] [--conversation <id>] [--json] [--debug]
-```
-
-Same as the shorthand above but under the `chat send` subcommand. Default stdout is **one-line JSON**; **`--pretty`** for assistant plain text from `data`.
-
-### Interactive chat (REPL)
-
-```bash
-max chat repl [--profile <name>] [--debug] [--timeout <seconds>]
-max chat
-```
-
-Opens an interactive readline session for back-and-forth conversation with Max.
-
-| REPL Command | Description                              |
-| ------------ | ---------------------------------------- |
-| `:help`      | Show available REPL commands             |
-| `:new`       | Start a new conversation on next message |
-| `:conv <id>` | Switch to a specific conversation ID     |
-| `:exit`      | Exit the REPL                            |
-| `Ctrl+C`     | Exit the REPL                            |
-
-**Example:**
-
-```bash
-# Start interactive chat
-max chat
-
-# Start with a specific profile
-max chat repl --profile work --debug
-```
-
-### Conversations (Public API)
-
-```bash
-max conversations list
-max conversations get <id>
-max conversations update <id> --data '{"key":"value"}'
-max conversations abort <id>
-# alias: max conv list
-```
-
-See `max conversations --help` for flags (`--profile`, `--base-url`, `--api-key`, `--debug`).
-
-## Conversation management
-
-- Max automatically remembers the last conversation ID in your profile. Subsequent messages continue that conversation.
-- Use `--new` to explicitly start a fresh conversation.
-- Use `--conversation <id>` to jump to a specific conversation.
-- In the REPL, use `:new` and `:conv <id>` to manage conversations interactively.
-
-## Troubleshooting
-
-- **"No Max API key found"**: run `max auth login <api-key>` or `frontline auth login <api-key>` on the same profile.
-- **"Message cannot be empty"**: provide a non-empty message string.
-- **Timeout waiting for reply**: increase `--timeout` or use `--no-wait` and check the conversation later.
-- Use `--debug` to see the full HTTP request URL, headers, and response status for diagnosing issues.
-- Use `--json` for machine-readable output that can be piped to `jq` or other tools.
+---
+name: max-chat
+description: Send messages to the Max AI assistant and manage conversations from the terminal. Use when the user wants to chat with Max, send a quick question, start a new conversation, or open an interactive chat session.
+---
+
+## Prerequisites
+
+- The `max` CLI must be installed (`npm i -g @frontline/cli` — provides both `frontline` and `max` binaries).
+- The user must have a per-user API key saved: `max auth login <api-key>` (or `frontline auth login` on the same profile).
+
+## Commands
+
+### Quick message (shorthand)
+
+```bash
+max "Your question here"
+max --new "Start a fresh conversation"
+```
+
+This is the fastest way to send a single message to Max. It uses the last active conversation by default, or `--new` to start a fresh one.
+
+Calls the **Public API**: `POST /public/v1/max/conversations/message` (Bearer = user API key). Responses use `{ "ok": boolean, "data": ... }`. Default stdout is **one-line JSON**; no spinner lines.
+
+| Flag                   | Description                                                 |
+| ---------------------- | ----------------------------------------------------------- |
+| `--new`                | Start a new conversation instead of continuing the last one |
+| `--conversation <id>`  | Send to a specific conversation ID                          |
+| `--no-wait`            | Do not poll for the assistant reply (fire and forget)       |
+| `--timeout <seconds>`  | Max seconds to wait for assistant reply (default: 60)       |
+| `--json`               | Print only the POST response JSON (no poll)                 |
+| `--pretty`             | Print assistant plain text from `data` instead of JSON      |
+| `--profile <name>`     | Use a specific Max CLI profile                              |
+| `--base-url <url>`     | Override Public API root (…/public/v1) for this run         |
+| `--api-base-url <url>` | Deprecated alias for `--base-url`                           |
+| `--api-key <key>`      | Override per-user API key for this run                      |
+| `--debug`              | Show HTTP request/response diagnostics                      |
+
+**Example:**
+
+```bash
+# Quick question using last conversation
+max "What agents do I have?"
+
+# Start a new conversation
+max --new "Help me set up a new workflow"
+
+# Send to a specific conversation
+max --conversation 123 "Continue from here"
+```
+
+### Send a message (explicit command)
+
+```bash
+max chat send <message...> [--new] [--conversation <id>] [--json] [--debug]
+```
+
+Same as the shorthand above but under the `chat send` subcommand. Default stdout is **one-line JSON**; **`--pretty`** for assistant plain text from `data`.
+
+### Interactive chat (REPL)
+
+```bash
+max chat repl [--profile <name>] [--debug] [--timeout <seconds>]
+max chat
+```
+
+Opens an interactive readline session for back-and-forth conversation with Max.
+
+| REPL Command | Description                              |
+| ------------ | ---------------------------------------- |
+| `:help`      | Show available REPL commands             |
+| `:new`       | Start a new conversation on next message |
+| `:conv <id>` | Switch to a specific conversation ID     |
+| `:exit`      | Exit the REPL                            |
+| `Ctrl+C`     | Exit the REPL                            |
+
+**Example:**
+
+```bash
+# Start interactive chat
+max chat
+
+# Start with a specific profile
+max chat repl --profile work --debug
+```
+
+### Conversations (Public API)
+
+```bash
+max conversations list
+max conversations get <id>
+max conversations update <id> --data '{"key":"value"}'
+max conversations abort <id>
+# alias: max conv list
+```
+
+See `max conversations --help` for flags (`--profile`, `--base-url`, `--api-key`, `--debug`).
+
+## Conversation management
+
+- Max automatically remembers the last conversation ID in your profile. Subsequent messages continue that conversation.
+- Use `--new` to explicitly start a fresh conversation.
+- Use `--conversation <id>` to jump to a specific conversation.
+- In the REPL, use `:new` and `:conv <id>` to manage conversations interactively.
+
+## Troubleshooting
+
+- **"No Max API key found"**: run `max auth login <api-key>` or `frontline auth login <api-key>` on the same profile.
+- **"Message cannot be empty"**: provide a non-empty message string.
+- **Timeout waiting for reply**: increase `--timeout` or use `--no-wait` and check the conversation later.
+- Use `--debug` to see the full HTTP request URL, headers, and response status for diagnosing issues.
+- Use `--json` for machine-readable output that can be piped to `jq` or other tools.

package/dist/skills/notes-and-tasks/SKILL.md

@@ -1,53 +1,54 @@
 ---
-name: notes-and-tasks
+name: activities-and-tasks
 description: >
-    How to create, read, update, and delete notes and tasks attached to rows
+    How to create, read, update, and delete activities and tasks attached to rows
     in tables and objects using the Frontline CLI.
 allowed-tools: Bash(frontline:*)
 ---
 
-# Notes & Tasks
+# Activities & Tasks
 
-Notes and tasks are sub-resources attached to individual rows. They let you
-track follow-ups, comments, and to-do items without polluting row fields.
+Activities and tasks are sub-resources attached to individual rows. They let you
+track follow-ups, comments, interactions, and to-do items without polluting row fields.
 
-## Notes
+## Activities
 
-Notes are simple text entries attached to a row.
+Activities log manual interactions on a row. Each activity has a **type**:
+`NOTE`, `EMAIL`, `PHONE_CALL`, `MEETING`, or `WHATSAPP`.
 
-### List Notes
+### List Activities
 
 ```bash
-frontline object note list <object> <row-id>
-frontline table note list <table> <row-id>
+frontline object activity list <object> <row-id>
 ```
 
-### Create a Note
+### Create an Activity
 
 ```bash
-frontline object note create <object> <row-id> --content "Follow up next week"
-frontline table note create <table> <row-id> --content "Check inventory levels"
+# Simple note (default type)
+frontline object activity create <object> <row-id> --content "Follow up next week"
+
+# With a specific type
+frontline object activity create <object> <row-id> --content "Called re: pricing" --type PHONE_CALL
+frontline object activity create <object> <row-id> --content "Discussed contract" --type MEETING
 ```
 
-### Get a Note by ID
+### Get an Activity by ID
 
 ```bash
-frontline object note get <object> <note-id>
-frontline table note get <table> <note-id>
+frontline object activity get <object> <activity-id>
 ```
 
-### Update a Note
+### Update an Activity
 
 ```bash
-frontline object note update <object> <note-id> --content "Updated: follow up tomorrow"
-frontline table note update <table> <note-id> --content "Updated content"
+frontline object activity update <object> <activity-id> --content "Updated: follow up tomorrow"
 ```
 
-### Delete a Note
+### Delete an Activity
 
 ```bash
-frontline object note delete <object> <note-id>
-frontline table note delete <table> <note-id>
+frontline object activity delete <object> <activity-id>
 ```
 
 ---
@@ -60,7 +61,6 @@ Tasks have content, optional due dates, assignees, and a completion state.
 
 ```bash
 frontline object task list <object> <row-id>
-frontline table task list <table> <row-id>
 ```
 
 ### Create a Task
@@ -111,18 +111,18 @@ frontline object task delete <object> <task-id>
 
 ```bash
 # 1. Find the row you want to annotate
-frontline object record list sor__deals --search "Acme"
+frontline object record list deals --search "Acme"
 # → row ID = 6625abc123def456
 
-# 2. Add a note
-frontline object note create sor__deals 6625abc123def456 \
-  --content "Discussed pricing on call"
+# 2. Log a phone call activity
+frontline object activity create deals 6625abc123def456 \
+  --content "Discussed pricing on call" --type PHONE_CALL
 
 # 3. Add a follow-up task with a due date
-frontline object task create sor__deals 6625abc123def456 \
+frontline object task create deals 6625abc123def456 \
   --content "Send revised proposal" \
   --due-date 2026-05-15
 
 # 4. Later, mark it complete
-frontline object task complete sor__deals 7
+frontline object task complete deals 7
 ```

package/dist/skills/pipeline-setup/SKILL.md

@@ -176,33 +176,33 @@ frontline object record list <object> --query '{
 ## Complete Example: Support Ticket Pipeline
 
 ```bash
-# 1. The Status field already exists on sor__tickets as a predefined field.
+# 1. The Status field already exists on tickets as a predefined field.
 #    Check its field ID and existing options:
-frontline object field list sor__tickets
+frontline object field list tickets
 # → Status field ID = 64, existing options: New, On You, On Customer, On Hold, Closed
 
 # 2. Add more stages to the existing Status field (optionsEditable: true)
-frontline object option create sor__tickets 64 --data '{"name": "Escalated", "color": "Bright Red"}'
-frontline object option create sor__tickets 64 --data '{"name": "Waiting on Vendor", "color": "Amber"}'
+frontline object option create tickets 64 --data '{"name": "Escalated", "color": "Bright Red"}'
+frontline object option create tickets 64 --data '{"name": "Waiting on Vendor", "color": "Amber"}'
 
 # 3. Also add a priority field
-frontline object field create sor__tickets --data '{
+frontline object field create tickets --data '{
   "name": "Priority",
   "type": "select",
   "metadata": { "mode": "singleSelect" }
 }'
 # → { id: 11, ... }
 
-frontline object option create sor__tickets 11 --data '{"name": "Critical", "color": "Bright Red"}'
-frontline object option create sor__tickets 11 --data '{"name": "High", "color": "Magenta"}'
-frontline object option create sor__tickets 11 --data '{"name": "Medium", "color": "Amber"}'
-frontline object option create sor__tickets 11 --data '{"name": "Low", "color": "Gray"}'
+frontline object option create tickets 11 --data '{"name": "Critical", "color": "Bright Red"}'
+frontline object option create tickets 11 --data '{"name": "High", "color": "Magenta"}'
+frontline object option create tickets 11 --data '{"name": "Medium", "color": "Amber"}'
+frontline object option create tickets 11 --data '{"name": "Low", "color": "Gray"}'
 
 # 4. Create record type with relevant fields
-frontline object field list sor__tickets
+frontline object field list tickets
 # → Suppose: 1=Subject, 10=Status, 11=Priority, 5=Assignee, 3=Description
 
-frontline object record-type create sor__tickets --data '{
+frontline object record-type create tickets --data '{
   "name": "support_board",
   "displayName": "Support Board",
   "columnIds": [1, 10, 11, 5, 3]
@@ -210,14 +210,14 @@ frontline object record-type create sor__tickets --data '{
 # → { id: 4, ... }
 
 # 5. Create kanban view grouped by Status — directly on the object
-frontline object view create sor__tickets --data '{
+frontline object view create tickets --data '{
   "name": "Ticket Board",
   "type": "KANBAN",
   "metadata": { "groupingColumnId": 10 }
 }'
 
 # 6. Create a table view too (for list browsing)
-frontline object view create sor__tickets --data '{
+frontline object view create tickets --data '{
   "name": "All Tickets",
   "type": "TABLE",
   "metadata": {}

package/dist/skills/relations/SKILL.md

@@ -34,7 +34,7 @@ frontline object field create <source-obj> --data '{
 Before working with relations, inspect the object schema to find relation names:
 
 ```bash
-frontline object schema sor__people
+frontline object schema people
 ```
 
 The output includes a `relations` array:
@@ -42,8 +42,13 @@ The output includes a `relations` array:
 ```json
 {
     "relations": [
-        { "name": "company", "target": "sor__companies", "mode": "multi", "display_field": "Name" },
-        { "name": "deals", "target": "sor__deals", "mode": "multi", "display_field": "Name" }
+        {
+            "name": "company",
+            "target": "companies",
+            "mode": "multi",
+            "display_field": "Name"
+        },
+        { "name": "deals", "target": "deals", "mode": "multi", "display_field": "Name" }
     ]
 }
 ```
@@ -60,7 +65,7 @@ frontline object relation link <object> <source-id> <relation> <target-id>
 
 ```bash
 # Link a person to a company
-frontline object relation link sor__people 6625abc123def456 Companies 6625def789abc012
+frontline object relation link people 6625abc123def456 Companies 6625def789abc012
 ```
 
 - **Idempotent**: linking the same target twice won't create duplicates.
@@ -76,7 +81,7 @@ frontline object relation unlink <object> <source-id> <relation> <target-id>
 
 ```bash
 # Remove person from company
-frontline object relation unlink sor__people 6625abc123def456 Companies 6625def789abc012
+frontline object relation unlink people 6625abc123def456 Companies 6625def789abc012
 ```
 
 ## Get Related Records (Forward Lookup)
@@ -89,7 +94,7 @@ frontline object relation get <object> <source-id> <relation>
 
 ```bash
 # Get all companies linked to this person
-frontline object relation get sor__people 6625abc123def456 Companies
+frontline object relation get people 6625abc123def456 Companies
 ```
 
 Returns an array of related records with their full data.
@@ -104,10 +109,10 @@ frontline object relation find-by <object> <relation> <target-id> [--page N] [--
 
 ```bash
 # Find all people linked to a specific company
-frontline object relation find-by sor__people Companies 6625def789abc012
+frontline object relation find-by people Companies 6625def789abc012
 
 # With pagination
-frontline object relation find-by sor__people Companies 6625def789abc012 --page 1 --page-size 20
+frontline object relation find-by people Companies 6625def789abc012 --page 1 --page-size 20
 ```
 
 Returns a paginated result: `{ rows, total_count, total_pages, current_page }`.
@@ -116,23 +121,23 @@ Returns a paginated result: `{ rows, total_count, total_pages, current_page }`.
 
 ```bash
 # 1. Show current company links
-frontline object relation get sor__people <person-id> Companies
+frontline object relation get people <person-id> Companies
 
 # 2. Unlink from old company
-frontline object relation unlink sor__people <person-id> Companies <old-company-id>
+frontline object relation unlink people <person-id> Companies <old-company-id>
 
 # 3. Link to new company
-frontline object relation link sor__people <person-id> Companies <new-company-id>
+frontline object relation link people <person-id> Companies <new-company-id>
 
 # 4. Verify
-frontline object relation get sor__people <person-id> Companies
+frontline object relation get people <person-id> Companies
 ```
 
 ## Workflow: Find All Deals for a Company
 
 ```bash
 # Find deals linked to a company (reverse: deals that point to this company)
-frontline object relation find-by sor__deals Company <company-id>
+frontline object relation find-by deals Company <company-id>
 ```
 
 ## Filtering by Relation
@@ -142,10 +147,10 @@ You can also filter records by relations using the query system
 
 ```bash
 # Find people with no company
-frontline object record list sor__people --query '{"path": "[Company]", "operator": "isNull"}'
+frontline object record list people --query '{"path": "[Company]", "operator": "isNull"}'
 
 # Find people linked to specific companies
-frontline object record list sor__people --query '{
+frontline object record list people --query '{
   "path": "[Company]",
   "operator": "containsAny",
   "value": ["6625def789abc012", "6625def789abc999"]