@feastalytics/cli 0.1.1 → 0.1.3

package/feast/SKILL.md

@@ -14,17 +14,37 @@ The CLI is the source of truth for *which* tools exist and *what* they accept
 The `feast` CLI must be installed and on PATH:
 
 ```bash
-npm install -g @feast/cli    # or run ad-hoc with: npx @feast/cli <command>
+npm install -g @feastalytics/cli    # or run ad-hoc with: npx @feastalytics/cli <command>
 ```
 
 Authenticate once — tokens are cached in `~/.config/feast-cli/credentials.json` and refreshed automatically:
 
 ```bash
-feast login <username>
+feast login                        # opens a browser to authorize (default)
+feast login --password [username]  # headless / CI: username + password prompt, no browser
 ```
 
 If a command reports you're not logged in or the session expired, re-run `feast login`.
 
+## Staying current
+
+Neither the CLI nor this skill updates itself. When a command prints an update notice on stderr:
+
+```
+Update available: feast 0.1.1 → 0.2.0
+```
+
+update both, then tell the user in one line that you did:
+
+```bash
+npm install -g @feastalytics/cli@latest      # only if `feast` is already on PATH from a global install
+npx skills add feastalytics/cli -g -a '*' -y # refresh this skill from the repo
+```
+
+If you've been invoking the CLI through `npx` rather than a global install, skip the `npm install -g` and use `npx @feastalytics/cli@latest <command>` for the rest of the session instead — `npx` reuses a cached copy otherwise.
+
+Update the skill whenever you update the CLI: the two ship from the same repo but on different triggers, so a new CLI version usually means this skill's guidance has moved too. If the global install fails on permissions, don't retry with `sudo` — tell the user and fall back to `npx @feastalytics/cli@latest`.
+
 ## The core loop: discover → describe → call
 
 Don't guess tool names or input shapes. Introspect the live CLI:
@@ -88,7 +108,7 @@ The pattern generalizes: identify the org, learn the tool, resolve any reference
 
 ## When something fails
 
-- "Not logged in / session expired" → `feast login <username>`.
+- "Not logged in / session expired" → `feast login` (or `feast login --password [username]` in a headless/CI context).
 - "You belong to multiple organizations" → pick one with `--org`, using `feast whoami` to get the id.
 - "Input does not match the tool schema" → re-read `feast describe <tool>` and fix the named fields.
 - A tool you expected isn't listed by `feast tools` → it may not be exposed yet; don't fabricate a call, tell the user.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feastalytics/cli",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Command-line client for the Feastalytics platform — list, create, and update campaigns, automations, offers, and members-program rewards from the terminal.",
   "type": "module",
   "bin": {