@getfrontline/cli 1.0.0

package/dist/skills/frontline-agents/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: frontline-agents
+description: List, filter, and inspect Frontline AI agents using the Frontline CLI. Use when the user asks about their agents, wants to see agent status, flows, or analytics.
+---
+
+## Prerequisites
+
+- The `frontline` CLI must be installed (`npm i -g @frontline/cli`).
+- The user must be authenticated (`frontline auth login`).
+
+## Commands
+
+### List all agents
+
+```bash
+frontline agents list [--status <status>] [--json] [--debug]
+```
+
+| Flag                | Description                                        |
+| ------------------- | -------------------------------------------------- |
+| `--status <status>` | Filter by status: `active`, `inactive`, or `draft` |
+| `--json`            | Output raw JSON instead of a table                 |
+| `--api-key <key>`   | Override the stored API key for this request       |
+| `--profile <name>`  | Use a specific CLI profile                         |
+| `--debug`           | Show HTTP request/response diagnostics             |
+
+**Example:**
+
+```bash
+# List all active agents
+frontline agents list --status active
+
+# Get agent list as JSON for programmatic use
+frontline agents list --json
+```
+
+**Output columns:** `id`, `name`, `status`, `createdAt`, `updatedAt`
+
+### Get flows for a specific agent
+
+```bash
+frontline agents flows <agentId> [--status <status>] [--json] [--debug]
+```
+
+| Flag                | Description                            |
+| ------------------- | -------------------------------------- |
+| `<agentId>`         | **(required)** The agent ID            |
+| `--status <status>` | Filter by flow status                  |
+| `--json`            | Output raw JSON                        |
+| `--api-key <key>`   | Override API key                       |
+| `--profile <name>`  | Use a specific CLI profile             |
+| `--debug`           | Show HTTP request/response diagnostics |
+
+**Example:**
+
+```bash
+# List all flows for agent abc-123
+frontline agents flows abc-123
+
+# Filter active flows only
+frontline agents flows abc-123 --status active --json
+```
+
+**Output columns:** `id`, `name`, `status`, `runCount`, `createdAt`
+
+### Get analytics for a specific agent
+
+```bash
+frontline agents analytics <agentId> [--start-date <YYYY-MM-DD>] [--end-date <YYYY-MM-DD>] [--json] [--debug]
+```
+
+| Flag                  | Description                            |
+| --------------------- | -------------------------------------- |
+| `<agentId>`           | **(required)** The agent ID            |
+| `--start-date <date>` | Start date in `YYYY-MM-DD` format      |
+| `--end-date <date>`   | End date in `YYYY-MM-DD` format        |
+| `--json`              | Output raw JSON                        |
+| `--api-key <key>`     | Override API key                       |
+| `--profile <name>`    | Use a specific CLI profile             |
+| `--debug`             | Show HTTP request/response diagnostics |
+
+**Example:**
+
+```bash
+# Get analytics for agent abc-123 for a date range
+frontline agents analytics abc-123 --start-date 2025-01-01 --end-date 2025-01-31
+
+# Get analytics as JSON
+frontline agents analytics abc-123 --json
+```
+
+**Output:** Summary (totalCredits, totalConversations), Credits by Date table, Conversations by Channel table.
+
+## Troubleshooting
+
+- **"No API key found"**: run `frontline auth login` to authenticate.
+- 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.
+- Use `--profile <name>` if you have multiple Frontline accounts configured.

package/dist/skills/frontline-api/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: frontline-api
+description: Make raw HTTP requests to the Frontline Public API using the Frontline CLI. Use as an escape hatch when a specific endpoint does not have a dedicated CLI command, or when exploring the API.
+---
+
+## Prerequisites
+
+- The `frontline` CLI must be installed (`npm i -g @frontline/cli`).
+- The user must be authenticated (`frontline auth login`).
+
+## Commands
+
+### Make a raw API GET request
+
+```bash
+frontline api get <path> [--query <key=value>...] [--json] [--debug]
+```
+
+| Flag                 | Description                                                                     |
+| -------------------- | ------------------------------------------------------------------------------- |
+| `<path>`             | **(required)** API path relative to the base URL (e.g. `/agents`, `/workflows`) |
+| `--query <pairs...>` | Query parameters as `key=value` pairs (repeatable)                              |
+| `--json`             | Output as JSON (default for raw requests)                                       |
+| `--api-key <key>`    | Override the stored API key for this request                                    |
+| `--profile <name>`   | Use a specific CLI profile                                                      |
+| `--debug`            | Show HTTP request/response diagnostics                                          |
+
+**Important:** Only `GET` requests are supported currently. Passing any other method will result in an error.
+
+**Example:**
+
+```bash
+# Raw GET request to the agents endpoint
+frontline api get /agents
+
+# Raw GET with query parameters
+frontline api get /agents --query status=active --query limit=10
+
+# With debug output to see full request details
+frontline api get /billing --debug
+```
+
+**Output:** Always returns raw JSON response from the API.
+
+## When to use this skill
+
+- When you need to access an API endpoint that does not have a dedicated CLI command.
+- When you want to explore the API response structure.
+- When building automation scripts that need raw API data.
+
+## Discovering available endpoints
+
+Run `frontline --help` to see all available commands. If a resource is not listed, you can try calling it directly via `frontline api get /resource-name`.
+
+## Troubleshooting
+
+- **"No API key found"**: run `frontline auth login` to authenticate.
+- **"Only GET requests are supported"**: the raw API command currently only supports GET. POST/PUT/DELETE are not yet available.
+- Use `--debug` to see the full HTTP request URL, headers, and response status for diagnosing issues.

package/dist/skills/frontline-billing/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: frontline-billing
+description: Query Frontline billing plan information using the Frontline CLI. Use when the user asks about their billing, credits, plan, or subscription.
+---
+
+## Prerequisites
+
+- The `frontline` CLI must be installed (`npm i -g @frontline/cli`).
+- The user must be authenticated (`frontline auth login`).
+
+## Commands
+
+### Get current billing information
+
+```bash
+frontline billing get [--json] [--debug]
+```
+
+| Flag               | Description                                  |
+| ------------------ | -------------------------------------------- |
+| `--json`           | Output raw JSON instead of key-value display |
+| `--api-key <key>`  | Override the stored API key for this request |
+| `--profile <name>` | Use a specific CLI profile                   |
+| `--debug`          | Show HTTP request/response diagnostics       |
+
+**Example:**
+
+```bash
+# View current billing plan
+frontline billing get
+
+# Get billing info as JSON
+frontline billing get --json
+```
+
+**Output fields:** `Plan`, `Credits Used` (e.g. `1500 / 10000`), `Subscription Renews` (date).
+
+## Troubleshooting
+
+- **"No API key found"**: run `frontline auth login` to authenticate.
+- 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/frontline-workflows/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: frontline-workflows
+description: List, filter, and inspect Frontline workflows using the Frontline CLI. Use when the user asks about their workflows, wants to see workflow status, run counts, or analytics.
+---
+
+## Prerequisites
+
+- The `frontline` CLI must be installed (`npm i -g @frontline/cli`).
+- The user must be authenticated (`frontline auth login`).
+
+## Commands
+
+### List all workflows
+
+```bash
+frontline workflows list [--status <status>] [--json] [--debug]
+```
+
+| Flag                | Description                                        |
+| ------------------- | -------------------------------------------------- |
+| `--status <status>` | Filter by status: `active`, `inactive`, or `draft` |
+| `--json`            | Output raw JSON instead of a table                 |
+| `--api-key <key>`   | Override the stored API key for this request       |
+| `--profile <name>`  | Use a specific CLI profile                         |
+| `--debug`           | Show HTTP request/response diagnostics             |
+
+**Example:**
+
+```bash
+# List all workflows
+frontline workflows list
+
+# List only active workflows as JSON
+frontline workflows list --status active --json
+```
+
+**Output columns:** `id`, `name`, `status`, `triggerType`, `runsCount`, `lastRunDate`
+
+### Get analytics for a specific workflow
+
+```bash
+frontline workflows analytics <workflowId> [--start-date <YYYY-MM-DD>] [--end-date <YYYY-MM-DD>] [--json] [--debug]
+```
+
+| Flag                  | Description                            |
+| --------------------- | -------------------------------------- |
+| `<workflowId>`        | **(required)** The workflow ID         |
+| `--start-date <date>` | Start date in `YYYY-MM-DD` format      |
+| `--end-date <date>`   | End date in `YYYY-MM-DD` format        |
+| `--json`              | Output raw JSON                        |
+| `--api-key <key>`     | Override API key                       |
+| `--profile <name>`    | Use a specific CLI profile             |
+| `--debug`             | Show HTTP request/response diagnostics |
+
+**Example:**
+
+```bash
+# Get workflow analytics for a date range
+frontline workflows analytics 42 --start-date 2025-01-01 --end-date 2025-01-31
+
+# Get workflow analytics as JSON
+frontline workflows analytics 42 --json
+```
+
+**Output:** Summary section, Runs by Date table (date, totalRuns, successfulRuns, failedRuns, totalCredits).
+
+## Troubleshooting
+
+- **"No API key found"**: run `frontline auth login` to authenticate.
+- 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.
+- Use `--profile <name>` if you have multiple Frontline accounts configured.

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

@@ -0,0 +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`.

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

@@ -0,0 +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.

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

@@ -0,0 +1,128 @@
+---
+name: notes-and-tasks
+description: >
+    How to create, read, update, and delete notes and tasks attached to rows
+    in tables and objects using the Frontline CLI.
+allowed-tools: Bash(frontline:*)
+---
+
+# Notes & 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.
+
+## Notes
+
+Notes are simple text entries attached to a row.
+
+### List Notes
+
+```bash
+frontline object note list <object> <row-id>
+frontline table note list <table> <row-id>
+```
+
+### Create a Note
+
+```bash
+frontline object note create <object> <row-id> --content "Follow up next week"
+frontline table note create <table> <row-id> --content "Check inventory levels"
+```
+
+### Get a Note by ID
+
+```bash
+frontline object note get <object> <note-id>
+frontline table note get <table> <note-id>
+```
+
+### Update a Note
+
+```bash
+frontline object note update <object> <note-id> --content "Updated: follow up tomorrow"
+frontline table note update <table> <note-id> --content "Updated content"
+```
+
+### Delete a Note
+
+```bash
+frontline object note delete <object> <note-id>
+frontline table note delete <table> <note-id>
+```
+
+---
+
+## Tasks
+
+Tasks have content, optional due dates, assignees, and a completion state.
+
+### List Tasks
+
+```bash
+frontline object task list <object> <row-id>
+frontline table task list <table> <row-id>
+```
+
+### Create a Task
+
+```bash
+# Simple task
+frontline object task create <object> <row-id> --content "Call the client"
+
+# With due date
+frontline object task create <object> <row-id> \
+  --content "Send proposal" \
+  --due-date 2026-05-01
+
+# With assignees (comma-separated user IDs)
+frontline object task create <object> <row-id> \
+  --content "Review contract" \
+  --assignees 12,34
+```
+
+### Get a Task by ID
+
+```bash
+frontline object task get <object> <task-id>
+```
+
+### Update a Task
+
+```bash
+frontline object task update <object> <task-id> --data '{"content":"Revised task","dueDate":"2026-06-01"}'
+```
+
+### Complete / Uncomplete a Task
+
+```bash
+frontline object task complete <object> <task-id>
+frontline object task uncomplete <object> <task-id>
+```
+
+### Delete a Task
+
+```bash
+frontline object task delete <object> <task-id>
+```
+
+---
+
+## Typical Workflow
+
+```bash
+# 1. Find the row you want to annotate
+frontline object record list sor__deals --search "Acme"
+# → row ID = 6625abc123def456
+
+# 2. Add a note
+frontline object note create sor__deals 6625abc123def456 \
+  --content "Discussed pricing on call"
+
+# 3. Add a follow-up task with a due date
+frontline object task create sor__deals 6625abc123def456 \
+  --content "Send revised proposal" \
+  --due-date 2026-05-15
+
+# 4. Later, mark it complete
+frontline object task complete sor__deals 7
+```