ethos-cli 0.8.0 → 0.8.1

package/package.json

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

package/skills/enrich-contact-info.md

@@ -22,6 +22,12 @@ Prefer Ethos MCP tools when available:
 2. Inspect the sample result or open the returned table URL.
 3. Call `enrich_contact_info` with the returned contact-info column ID and `scope: "empty"`.
 
+The `table_id` must be a PEOPLE table, never the company table a sourcing run
+started from. After people sourcing, `inspect_table_summary` on the company
+table returns the linked `people_table_id` once it exists; if it does not exist
+yet, call `create_people_table` on the company table first and enrich the table
+it returns.
+
 Use the CLI sections below only when MCP tools are unavailable or the user
 explicitly asks for the local CLI.
 

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

@@ -21,6 +21,10 @@ Prefer Ethos MCP tools when available:
 3. Poll `get_upload_handoff_status` until it returns a `result_table_id`.
 4. Use `search_ethos_tools` for table inspection if column/view IDs are needed.
 5. Call `source_people_from_company_table`, then run a small sample first.
+6. Poll `inspect_table_summary` on the company table until the sourcing run in
+   `recent_runs` is terminal, then call `create_people_table` to materialize the
+   linked people table. Run `enrich_contact_info` and campaign steps against
+   that people table id, never the company table.
 
 Use the CLI/hook sections below only when MCP tools are unavailable or the user
 explicitly asks for the local CLI. Avoid creating duplicate handoffs when MCP,

package/skills/find-people.md

@@ -18,8 +18,13 @@ development or an explicitly requested environment.
 Prefer Ethos MCP tools when available:
 
 1. Call `find_people` with the final natural-language query.
-2. Poll `get_find_people_status` with the returned `search_id`.
-3. Return the people table ID/URL, counts, status, and refinement suggestions.
+2. If the response status is `needs_refinement` with no `search_id`, the query
+   was declined before starting; follow the response `next_action` — either
+   rewrite the query to describe both companies and people, or pivot to
+   `create_table` + `source_people_from_company_table` using
+   `data.company_names`. Do not retry the same query.
+3. Poll `get_find_people_status` with the returned `search_id`.
+4. Return the people table ID/URL, counts, status, and refinement suggestions.
 
 Use the CLI sections below only when MCP tools are unavailable or the user
 explicitly asks for the local CLI.
@@ -130,10 +135,14 @@ ethos find-people start --query "$QUERY" --json
 Save `response.search_id`, `response.parsedParams`, `response.status`, and
 `response.progressMessage`.
 
-If the command returns `success: false`, inspect `error.suggestedAction` and
-`error.parsedParams`. When `suggestedAction` is not `combinedSearch`, tell the
-user the parser understood only company criteria or only person criteria, then
-rewrite the query so it includes both target companies and target individuals.
+If the command returns `success: false`, inspect `error.suggestedAction`,
+`error.companyNames`, and `error.parsedParams`. Queries that name specific
+employers are converted to a search over exactly those companies automatically,
+so a decline means the parse could not be run as-is. When `error.companyNames`
+is non-empty, do not retry the same query; pivot to the
+find-people-at-companies flow (create a company table with those companies and
+run people sourcing on it). Otherwise rewrite the query so it includes both
+target companies and target individuals.
 
 After a successful start, summarize the parsed params in plain language. Do not
 paste the full JSON unless the user asks for it.