@floomhq/skills 1.0.2 → 1.1.0

package/README.md

@@ -1,41 +1,41 @@
-# @floomhq/floom
+# @floomhq/skills
 
-The Floom CLI: one shared skill library, synced across every AI agent.
+The Floom Skills CLI: publish, install, sync, and share AI agent skills.
 
-Docs: <https://floom.dev/docs>
+Docs: <https://skills.floom.dev/docs>
 
 ## Install
 
 ```bash
-npm i -g @floomhq/floom
+npm i -g @floomhq/skills
 ```
 
 Pinned no-install form for automation:
 
 ```bash
-npx -y @floomhq/floom@3.0.2 --help
+npx -y @floomhq/skills@1.1.0 --help
 ```
 
 ## Login
 
 ```bash
-floom login
+floom-skills login
 ```
 
-The login command starts a browser device flow. Sign in at floom.dev with
+The login command starts a browser device flow. Sign in at skills.floom.dev with
 Google or email, approve the device code, and the CLI stores the session at
 `~/.floom/auth.json`.
 
 Check the active account:
 
 ```bash
-floom account
+floom-skills account
 ```
 
 ## First Skill
 
 ```bash
-floom push ~/.claude/skills/my-skill
+floom-skills push ~/.claude/skills/my-skill
 ```
 
 The folder must contain `SKILL.md`. Each push creates a Library version.
@@ -43,16 +43,16 @@ The folder must contain `SKILL.md`. Each push creates a Library version.
 Create a starter skill when the folder does not exist yet:
 
 ```bash
-floom new my-skill --agent claude
+floom-skills new my-skill --agent claude
 ```
 
 ## Bulk Sync
 
 ```bash
-floom sync
+floom-skills sync
 ```
 
-Zero-arg `floom sync` detects installed agents and supported scopes, reviews
+Zero-arg `floom-skills sync` detects installed agents and supported scopes, reviews
 local-to-Library and Library-to-local differences, and applies the selected
 plan. Use `--dry-run` to preview the plan without changing files or Library
 records.
@@ -60,24 +60,25 @@ records.
 Library-to-local only:
 
 ```bash
-floom pull
-floom pull --agent claude,codex
+floom-skills pull
+floom-skills pull --agent claude,codex
 ```
 
 Local-to-Library only:
 
 ```bash
-floom push
+floom-skills push
 ```
 
-Use the installed `floom` command for interactive terminal work. Use the pinned
-`npx -y @floomhq/floom@3.0.2 <command>` form for automation and agent-run
+Use the installed `floom-skills` command for interactive terminal work. Use the pinned
+`npx -y @floomhq/skills@1.1.0 <command>` form for automation and agent-run
 commands that need reproducible CLI behavior.
 
 ## Releasing
 
-Releases publish to npm and bump the Homebrew tap formula automatically via
-`.github/workflows/publish-cli.yml`, triggered by a `cli-v*` tag.
+Releases publish the exact smoke-tested npm tarball via
+`.github/workflows/publish-cli.yml`, triggered by a `skills-v*` tag.
+Provenance is disabled while the source repository remains private.
 
 ### Hard pre-publish smoke gate
 
@@ -93,24 +94,17 @@ and unknown commands silently rendered the dashboard. Only an out-of-band
 real-terminal smoke caught them. This script is that smoke, baked into the
 publish pipeline.
 
-### Before pushing a `cli-v*` tag
+### Before pushing a `skills-v*` tag
 
-Run the local pre-tag check from the repo root:
+Run the same local gates from the repo root:
 
 ```bash
-./scripts/pre-tag-check.sh
+pnpm --filter @floomhq/skills --fail-if-no-match lint
+pnpm --filter @floomhq/skills --fail-if-no-match test
+pnpm --filter @floomhq/skills --fail-if-no-match pack:smoke
+packages/cli/scripts/pre-publish-smoke.sh
 ```
 
-It:
-
-1. Confirms the working tree is clean.
-2. Rebuilds the CLI from a clean `dist/`.
-3. Runs the CLI unit test suite (`pnpm --filter @floomhq/floom test`).
-4. Runs the full pre-publish smoke (same script the workflow runs).
-
-If everything passes, the script prints the exact `git tag` + `git push origin`
-commands. You then push the tag and the workflow takes over.
-
 If anything fails, fix the issue first. Do not push the tag.
 
 ### Smoke-only workflow run
@@ -119,7 +113,7 @@ To validate the smoke script itself without publishing (e.g. after editing
 `scripts/pre-publish-smoke.sh`):
 
 ```
-GitHub → Actions → Publish @floomhq/floom → Run workflow
+GitHub → Actions → Publish @floomhq/skills → Run workflow
   smoke_only: true
 ```
 
@@ -138,14 +132,14 @@ See `scripts/pre-publish-smoke.sh` for the full assertion list. Summary:
 
 | Stage | Asserts |
 |------|---------|
-| 1 | Tarball builds, packs, installs cleanly into isolated `$HOME`; installed `floom --version` matches `package.json` |
-| 2 | **Every** subcommand `--help` exits 0, starts with `Usage: floom`, writes no `~/.floom/auth.json`, prints no "Signed (in|out)" / "Waiting for browser" (P0 #1 from 3.0.0) |
-| 3 | `floom --help \| head -3` and `floom push --help \| head -1` print no EPIPE / "Unhandled error event" (P0 #2 from 3.0.0) |
-| 4 | `floom <unknown>` exits non-zero with "unknown command" + "did you mean" hint (P0 #3 from 3.0.0) |
-| 5 | Bare `floom --help` exits 0 with grouped help |
+| 1 | Tarball builds, packs, installs cleanly into isolated `$HOME`; installed `floom-skills --version` matches `package.json` |
+| 2 | **Every** subcommand `--help` exits 0, starts with `Usage: floom-skills`, writes no `~/.floom/auth.json`, prints no "Signed (in|out)" / "Waiting for browser" (P0 #1 from 3.0.0) |
+| 3 | `floom-skills --help \| head -3` and `floom-skills push --help \| head -1` print no EPIPE / "Unhandled error event" (P0 #2 from 3.0.0) |
+| 4 | `floom-skills <unknown>` exits non-zero with "unknown command" + "did you mean" hint (P0 #3 from 3.0.0) |
+| 5 | Bare `floom-skills --help` exits 0 with grouped help |
 | 6 | Unauth `whoami` / `account` / `logout` exit 0 idempotent; unauth `status` / `sync --json` / `push --json` exit non-zero with no stack trace |
-| 7 | `floom logout extra-positional` is rejected with non-zero exit AND `~/.floom/auth.json` is preserved (no destructive body) |
-| 8 | **Agent detection** picks up fake `.claude/`, `.codex/`, `.cursor/` marker dirs in the isolated `$HOME` (verified by parsing `floom doctor --json`); bare `floom sync` / `floom pull` with planted agents do not crash unauth (clean `signedIn:false` envelope). Note: fan-out *behaviour itself* requires real auth, so it is exercised at the **unit-test layer** by `src/commands/sync.fanout.test.ts`, which the publish workflow runs as a separate hard gate before the smoke. |
+| 7 | `floom-skills logout extra-positional` is rejected with non-zero exit AND `~/.floom/auth.json` is preserved (no destructive body) |
+| 8 | **Agent detection** picks up fake `.claude/`, `.codex/`, `.cursor/` marker dirs in the isolated `$HOME` (verified by parsing `floom-skills doctor --json`); bare `floom-skills sync` / `floom-skills pull` with planted agents do not crash unauth (clean `signedIn:false` envelope). Note: fan-out *behaviour itself* requires real auth, so it is exercised at the **unit-test layer** by `src/commands/sync.fanout.test.ts`, which the publish workflow runs as a separate hard gate before the smoke. |
 
 If any assertion fails, the publish job fails. The smoke script exits non-zero
 on the first failure and prints a summary of every failed check.