@hireobi/cli 0.1.7 → 0.1.8

package/package.json

@@ -1,9 +1,30 @@
 {
   "name": "@hireobi/cli",
-  "version": "0.1.7",
-  "description": "Obi AI Search Employee CLI and Skill by Heysurface, Inc.",
+  "version": "0.1.8",
+  "description": "Obi, the AI Search Employee: CLI and Skill for your AI assistant",
+  "keywords": [
+    "obi",
+    "ai-search",
+    "generative-engine-optimization",
+    "geo",
+    "aeo",
+    "chatgpt",
+    "claude-code",
+    "cursor",
+    "codex",
+    "agent-skill",
+    "cli"
+  ],
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://hireobi.com",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/hireobi/cli.git"
+  },
+  "bugs": {
+    "url": "https://github.com/hireobi/cli/issues",
+    "email": "support@hireobi.com"
+  },
   "type": "module",
   "publishConfig": {
     "access": "public",
@@ -14,15 +35,11 @@
     "node": ">=22"
   },
   "bin": {
-    "heysurface": "dist/heysurface.js",
     "obi": "dist/obi.js"
   },
   "files": [
     "LICENSE",
-    "dist/heysurface.js",
     "dist/obi.js",
-    "skills/heysurface/SKILL.md",
-    "skills/heysurface/references/*.md",
     "skills/obi/SKILL.md",
     "skills/obi/references/*.md",
     "README.md"

package/skills/obi/SKILL.md

@@ -13,7 +13,7 @@ Follow the customer's latest explicit language request; otherwise keep the langu
 
 Keep routine replies brief: the useful result, a material gap if one exists, and one next action. Show more evidence or detail when it helps a decision or the customer asks. Avoid repeated introductions, internal implementation plans and raw JSON dumps. Use ordinary conversation for corrections: invite the customer to write what should change, then wait for their words.
 
-Prefer the `obi` executable; `heysurface` remains a compatible alias. Both installed Skill names use these same instructions; invocation syntax depends on the host.
+Use the `obi` executable; invocation syntax depends on the host.
 
 ## Expert judgment
 
@@ -53,4 +53,4 @@ Lead with the outcome, material uncertainty and one useful next action. On an in
 
 Separate site observations, customer confirmations, host inferences and independently measured answers. Request only the private extracts needed for the agreed scope; keep secrets and unrelated workspace material local. A local draft or patch is a reviewable suggestion until the customer accepts it. The Skill runs when invoked; while the harness is closed, saved server measurements can continue but host research and reasoning wait for resumption.
 
-Stay in customer mode even inside the Heysurface source repository. A product-use failure is explained and recovered in this conversation. Open a development task, branch or pull request only after an explicit separate software-development request.
+Stay in customer mode even inside the Obi source repository. A product-use failure is explained and recovered in this conversation. Open a development task, branch or pull request only after an explicit separate software-development request.

package/skills/obi/references/host-work.md

@@ -14,7 +14,7 @@ Read in parallel when the host offers subagents: acquisition stays one process p
 
 ## Adaptive research and tool recovery
 
-When the customer asks you to resume after an error or a stop, say in your reply, in plain words: which work you resume (the selected case, the work ID and its version), that you first re-read its current state (`harness show`, and `status` for the case) before any retry or write, that you continue from the saved checkpoint rather than starting over, and that each partial save carries a new replay key. Name the exact error the customer saw. Describe commands and tools in plain words in the reply; give a command line or a tool such as `/chrome` only when the customer has to run it, and keep the Heysurface harness out of the customer's way.
+When the customer asks you to resume after an error or a stop, say in your reply, in plain words: which work you resume (the selected case, the work ID and its version), that you first re-read its current state (`harness show`, and `status` for the case) before any retry or write, that you continue from the saved checkpoint rather than starting over, and that each partial save carries a new replay key. Name the exact error the customer saw. Describe commands and tools in plain words in the reply; give a command line or a tool such as `/chrome` only when the customer has to run it, and keep the Obi harness out of the customer's way.
 
 Reuse relevant project context already authorized for this mission, keeping its source, date and uncertainty. Private context remains distinct from public site evidence and customer-confirmed facts. Read priority home, product, pricing, legal and buyer-specific pages first. As soon as they support an offer and buyer hypothesis, show it with citations and material gaps; keep it provisional while continuing the scoped inventory, and submit the first batch as soon as the home, pricing, product and about pages are interpreted so the server holds partial evidence. A useful conversational pattern is “I found X; it matters for your buyer because Y; I am checking Z next”, in the customer’s language, without another consent question. Separate positioning, buyer situations and served markets from legal identity and office location using [business judgment](business-judgment.md). Choose the next investigation by the missing fact that changes the buyer decision, rather than a fixed intake questionnaire.