ethos-cli 0.1.1 → 0.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ethos-cli",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Commander-based CLI for Ethos table operations",
   "homepage": "https://github.com/cluster-software/ethos#readme",
   "repository": {

package/skills/find-people-at-companies.md

@@ -1,6 +1,6 @@
 ---
 name: find-people-at-companies
-description: Import a company CSV into Ethos, collect ICP and buying-signal criteria, create a people_sourcing agent, run it on the first rows, and open the table. Use when the user asks to find ICP-matching people at companies from a CSV or invokes /find-people-at-companies.
+description: Open Ethos in the browser for company CSV upload, return to Codex through the upload deep link, collect ICP and buying-signal criteria, create a people_sourcing agent, and run it on the uploaded table. Use when the user asks to find ICP-matching people at companies from a CSV or invokes /find-people-at-companies.
 ---
 
 # find-people-at-companies
@@ -9,15 +9,19 @@ Use this when the user wants Ethos to source people at a list of companies.
 The production CLI default is `https://api.ethos.hello-cluster.com`, so only
 pass `--api-url` for local development or an explicitly requested environment.
 
-## Inputs
+## Flow
 
-If the user has not already provided these, ask only for what is missing:
+Always keep CSV upload browser-first:
 
-- Company CSV path.
-- ICP fit criteria for companies.
-- Buying-signal criteria to prioritize.
-- Person titles/functions to return.
-- Desired max people per company. Default to 3 when unspecified.
+1. Open Ethos in the browser with the CSV upload deep link.
+2. Let the user upload the company CSV in the app.
+3. Return to Codex from the app's upload-complete deep link.
+4. Collect the user's ICP, buying signals, person targets, and max contacts.
+5. Create the `people_sourcing` agent and Codex-created column with the CLI.
+
+Do not run `ethos tables import-csv` for this skill unless the user explicitly
+asks for a CLI-only/non-browser fallback. The browser upload is part of the
+product flow and must not be replaced by CLI import.
 
 ## Authenticate
 
@@ -36,18 +40,60 @@ ethos auth login --codex-thread-id "$CODEX_THREAD_ID"
 The browser claim flow handles production auth. Do not ask for API tokens unless
 the user explicitly wants a non-browser setup.
 
-## Import The CSV
+## Open Browser Upload
+
+Choose the app origin:
+
+- Use the current Ethos browser origin when the user is already looking at one.
+- Use a user-provided app origin when explicitly working in local development.
+- Otherwise use `https://ethos.hello-cluster.com`.
+
+Open this URL in the browser:
 
 ```sh
-ethos tables import-csv "$CSV_PATH" --entity-type company --json
+APP_BASE_URL="https://ethos.hello-cluster.com"
+UPLOAD_URL="$APP_BASE_URL/tables?codex_flow=find-people-at-companies&open_import=1"
+if [ -n "${CODEX_THREAD_ID:-}" ]; then
+  UPLOAD_URL="$UPLOAD_URL&codex_thread_id=$CODEX_THREAD_ID"
+fi
+```
+
+Use the Browser plugin/in-app browser when available. If no browser-control tool
+is available, run `open "$UPLOAD_URL"` and tell the user to upload the CSV there.
+
+After the upload, the app redirects to:
+
+```text
+/tables/<TABLE_ID>?codex_flow=find-people-at-companies&uploaded=1
 ```
 
-Save `response.table_id`, `response.view_ids[0]`, and the relevant company
-input column ids from `response.columns`.
+When `codex_thread_id` is present, the app also returns to the Codex thread.
+Save the table id from the deep-link URL, then inspect the imported table:
+
+```sh
+ethos tables get "$TABLE_ID" --json
+```
+
+Save `response.table_id`, `response.view_ids[0]`, and useful company input
+column ids from `response.columns`. Prefer the CLI/API ids when available; do
+not announce URL extraction unless troubleshooting.
+
+## Collect The Brief
+
+Only after the browser upload and return, ask for anything still missing:
+
+- ICP fit criteria for companies.
+- Buying-signal criteria to prioritize.
+- Person titles/functions to return.
+- Desired max people per company. Default to 3 when unspecified.
+
+Do not create the agent or people-sourcing column until the user has provided
+enough targeting context.
 
 ## Create The Agent
 
-Create a `people_sourcing` agent. Use these abilities by default:
+Create a `people_sourcing` agent after the brief is ready. Use these abilities
+by default:
 
 ```sh
 ethos agents create \
@@ -83,7 +129,7 @@ The instructions should include:
 
 ## Source People
 
-Run against the imported table view:
+Run against the uploaded table view:
 
 ```sh
 ethos tables source-people "$TABLE_ID" \
@@ -99,13 +145,20 @@ ethos tables source-people "$TABLE_ID" \
 Use multiple `--input-column` flags when the table has separate useful company
 fields such as name, domain, LinkedIn URL, and description.
 
-## Open And Report
+The `--created-by-codex` flag is required. It marks the column with
+`config.created_by = "codex"` and `config.source_label = "ran by codex"`, which
+lets the table UI show the Codex callout and auto-scroll to the new column when
+it appears.
+
+## Keep Browser On The Table
 
-Open the table in the production app:
+The browser should already be on the uploaded table from the deep-link return.
+If it is not, navigate to:
 
 ```sh
-open "https://ethos.hello-cluster.com/tables/$TABLE_ID"
+"$APP_BASE_URL/tables/$TABLE_ID"
 ```
 
-Then report the table URL, run id, and the agent id. Keep the response concise
-and mention that the run is visible in Ethos.
+Then report the table URL, run id, and agent id. Keep the response concise and
+mention that the Codex-created column should appear and auto-scroll into view in
+Ethos.