ethos-cli 0.1.5 → 0.1.6

package/package.json

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

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

@@ -167,7 +167,7 @@ Only run the agent for 3 rows on the first run, so the user can give feedback.
 
 ## Keep Browser On The Table
 
-After the `source-people` command succeeds, bring the browser back to the table:
+ONLY IF the user is not already viewing the table when the `source-people` command succeeds, bring the browser back to the table:
 
 ```sh
 "$APP_BASE_URL/tables/$TABLE_ID"
@@ -179,7 +179,7 @@ them or you are actively debugging.
 
 ## How to communicate with the user
 
-While you execute the flow, keep communication simple and approachable. Avoid
+- 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.
 
@@ -191,7 +191,13 @@ 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.
+Or instead of
+
+"I found the row selector for the trial run, so I can keep this to the first 3 companies exactly. I’m creating the agent now with the B2B seed/Series A GTM criteria and 4-contact target."
+
+say "I'm creating the agent now with the B2B seed/Series A GTM criteria and 4-contact target."
+
+- If you need input from the user, make it very clear by bolding it and maybe mentioning it on a new line.
 
 E.g.: