ethos-cli 0.1.3 → 0.1.5

package/package.json

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

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

@@ -11,13 +11,14 @@ pass `--api-url` for local development or an explicitly requested environment.
 
 ## Flow
 
-Always keep CSV upload browser-first:
+Always keep CSV upload in the Codex in-app Browser:
 
-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.
+1. Open Ethos in the in-app Browser with the CSV upload deep link.
+2. Immediately ask the user for ICP, buying signals, person targets, and max contacts while they upload.
+3. Poll that same in-app Browser tab until the upload-complete URL appears.
+4. Save the uploaded table id from that URL.
 5. Create the `people_sourcing` agent and Codex-created column with the CLI.
+6. Run the column for the FIRST 3 ROWS ONLY. Tell the user you're running for 3 rows to see if the results are good. If yes, the next step is to run on the whole table. If not, refine the agent based on their feedback so it finds the right people.
 
 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
@@ -42,13 +43,7 @@ the user explicitly wants a non-browser setup.
 
 ## 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:
+Open this URL in the Codex in-app Browser:
 
 ```sh
 APP_BASE_URL="https://ethos.hello-cluster.com"
@@ -58,24 +53,26 @@ if [ -n "${CODEX_THREAD_ID:-}" ]; then
 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.
+Use the Browser plugin/in-app Browser to navigate to `$UPLOAD_URL` and tell
+the user to upload the CSV there. Do not use `open`, Chrome, Safari, or any
+external/default browser for this flow.
 
-If the in-app browser gets stuck on an auth page such as `Redirecting to sign
-in`, or the CLI claim/approval page does not complete cleanly inside the in-app
-browser, switch the auth/upload handoff to Chrome or the system browser. Open
-the same claim URL or `UPLOAD_URL` there and continue the browser-first upload
-flow; do not spend time debugging embedded-browser auth state during the skill.
+After opening the upload modal, immediately ask:
+
+```text
+Please describe your ICP, any signals that would make them a good fit for your product or service, and where that data may live. You can keep typing while the CSV uploads.
+```
 
-After the upload, the app redirects to:
+Then poll the in-app Browser URL every 2 seconds while the user uploads and answers.
+The ONLY upload-completion indicator is this URL shape:
 
 ```text
 /tables/<TABLE_ID>?codex_flow=find-people-at-companies&uploaded=1
 ```
 
-When `codex_thread_id` is present, the app also returns to the Codex thread.
-Save the table id from the deep-link URL. Start inspecting the imported table,
-but do not let CLI inspection block the natural next user prompt:
+When the browser URL matches that shape, save the table id from the URL. Start
+inspecting the imported table, but do not let CLI inspection block the natural
+next user prompt:
 
 ```sh
 ethos tables get "$TABLE_ID" --json
@@ -90,7 +87,7 @@ cannot recover across accessible orgs and the table still cannot be read.
 
 ## Collect The Brief
 
-Immediately after the browser upload and return, ask for anything still missing:
+After the upload-complete URL appears, ask only for anything still missing:
 
 - ICP fit criteria for companies.
 - Buying-signal criteria to prioritize.
@@ -166,15 +163,36 @@ The `--created-by-codex` flag is required. It marks the column with
 lets the table UI show the Codex callout and auto-scroll to the new column when
 it appears.
 
+Only run the agent for 3 rows on the first run, so the user can give feedback.
+
 ## Keep Browser On The Table
 
-The browser should already be on the uploaded table from the deep-link return.
-If it is not, navigate to:
+After the `source-people` command succeeds, bring the browser back to the table:
 
 ```sh
 "$APP_BASE_URL/tables/$TABLE_ID"
 ```
 
-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.
+Then tell the user the agent is running on the first 3 rows. Do not surface
+agent ids, run ids, table ids, or similar internal ids unless the user asks for
+them or you are actively debugging.
+
+## How to communicate with the user
+
+While you execute the flow, keep communication simple and approachable. Avoid
+explaining UI behavior that should happen automatically when everything is
+working. Do not mention internal Ethos concepts unless explicitly necessary.
+
+For example, instead of 
+
+"I’ll create the people-sourcing agent with those criteria, then run it only on the first 3 rows so you can judge the results before expanding."
+
+say
+
+"I’ll create an agent to find people with those criteria, then run it only on the first 3 rows so you can judge the results before expanding. Give me a second to set it up, you will see the agent start working in ethos soon."
+
+If you need input from the user, make it very clear by bolding it and maybe mentioning it on a new line.
+
+E.g.:
+
+"**Next, please give me the following information** ..."