@botdocs/cli 0.6.0 → 0.8.0

package/dist/lib/ref.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Parse a BotDoc ref like `@user/slug` or `user/slug` into its parts.
+ *
+ * Mirrors the inline `parseRef` already in `commands/install.ts` and
+ * `commands/edit.ts` — kept here for reuse by `publish`/`unpublish`.
+ * The existing duplicates can be folded into this helper in a future
+ * refactor without behavior change.
+ *
+ * Throws on a malformed input so callers can surface a clear message
+ * instead of silently dispatching a malformed API request.
+ */
+export declare function parseRef(raw: string): {
+    username: string;
+    slug: string;
+};
+/**
+ * True when `source` looks like a BotDoc ref (e.g. `@me/my-skill` or
+ * `me/my-skill`), false when it looks like a local filesystem path.
+ *
+ * Used by `botdocs publish <source>` to overload one verb by argument
+ * shape — ref-form dispatches to the publish-toggle API, anything else
+ * goes through the existing file/dir/zip upload flow.
+ *
+ * Heuristic (lean toward "is a ref" only when unambiguous):
+ *
+ * - `@…` → ref. The leading `@` is unambiguous; no filesystem path
+ *   starts with `@`.
+ * - Starts with `./`, `..`, or `/` → path. Absolute and explicit
+ *   relative paths are never refs.
+ * - Contains a `.` (e.g. `foo.md`, `foo.zip`, `dir/file.md`) → path.
+ *   File extensions are the strongest signal we're looking at a file.
+ * - Contains exactly one `/` with non-empty parts on either side → ref.
+ *   `user/slug` and `org/repo`-style.
+ * - Otherwise → path. Bare names like `my-skill` resolve as directory
+ *   paths under the existing upload flow.
+ *
+ * False positives (a real directory named `user/slug` with no `.`) will
+ * surface as a clean "BotDoc not found" 404 from the API — not silent
+ * data loss, just a clearer error than letting the upload flow choke
+ * on a non-existent path.
+ */
+export declare function isRefForm(source: string): boolean;

package/dist/lib/ref.js

@@ -0,0 +1,60 @@
+/**
+ * Parse a BotDoc ref like `@user/slug` or `user/slug` into its parts.
+ *
+ * Mirrors the inline `parseRef` already in `commands/install.ts` and
+ * `commands/edit.ts` — kept here for reuse by `publish`/`unpublish`.
+ * The existing duplicates can be folded into this helper in a future
+ * refactor without behavior change.
+ *
+ * Throws on a malformed input so callers can surface a clear message
+ * instead of silently dispatching a malformed API request.
+ */
+export function parseRef(raw) {
+    const cleaned = raw.startsWith('@') ? raw.slice(1) : raw;
+    const parts = cleaned.split('/');
+    if (parts.length !== 2 || !parts[0] || !parts[1]) {
+        throw new Error(`Invalid ref: ${raw} (expected @user/slug)`);
+    }
+    return { username: parts[0], slug: parts[1] };
+}
+/**
+ * True when `source` looks like a BotDoc ref (e.g. `@me/my-skill` or
+ * `me/my-skill`), false when it looks like a local filesystem path.
+ *
+ * Used by `botdocs publish <source>` to overload one verb by argument
+ * shape — ref-form dispatches to the publish-toggle API, anything else
+ * goes through the existing file/dir/zip upload flow.
+ *
+ * Heuristic (lean toward "is a ref" only when unambiguous):
+ *
+ * - `@…` → ref. The leading `@` is unambiguous; no filesystem path
+ *   starts with `@`.
+ * - Starts with `./`, `..`, or `/` → path. Absolute and explicit
+ *   relative paths are never refs.
+ * - Contains a `.` (e.g. `foo.md`, `foo.zip`, `dir/file.md`) → path.
+ *   File extensions are the strongest signal we're looking at a file.
+ * - Contains exactly one `/` with non-empty parts on either side → ref.
+ *   `user/slug` and `org/repo`-style.
+ * - Otherwise → path. Bare names like `my-skill` resolve as directory
+ *   paths under the existing upload flow.
+ *
+ * False positives (a real directory named `user/slug` with no `.`) will
+ * surface as a clean "BotDoc not found" 404 from the API — not silent
+ * data loss, just a clearer error than letting the upload flow choke
+ * on a non-existent path.
+ */
+export function isRefForm(source) {
+    if (!source)
+        return false;
+    if (source.startsWith('@'))
+        return true;
+    if (source.startsWith('./') || source.startsWith('../') || source.startsWith('/')) {
+        return false;
+    }
+    if (source.includes('.'))
+        return false;
+    const parts = source.split('/');
+    if (parts.length !== 2)
+        return false;
+    return Boolean(parts[0] && parts[1]);
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@botdocs/cli",
-  "version": "0.6.0",
+  "version": "0.8.0",
   "description": "CLI for BotDocs — author, publish, install, and sync agent skills across Claude, Claude Code, Cursor, Codex, ChatGPT, Windsurf, Copilot, Gemini, Antigravity, and OpenCode.",
   "keywords": [
     "botdocs",

package/templates/agents.md

@@ -119,7 +119,8 @@ the user and recommend they set one.
 | `init [name]` | Scaffold a new skill directory. |
 | `validate <source>` | Pre-publish structural check. |
 | `search <query>` | Search the registry. |
-| `publish <source>` | Publish from a file, directory, or zip. |
+| `publish <source>` | Publish from a file, directory, or zip — or pass `@user/slug` to mark an existing draft live. |
+| `unpublish <ref>` | Hide a published BotDoc from `/explore` (sets the `draft` flag back; prompts unless `--yes`). |
 | `install <ref>` | Install a skill or bundle (auto-detects destinations). |
 | `sync [ref]` | Apply available updates to installed skills. |
 | `uninstall <ref>` | Remove an installed skill or bundle. |