@dastyaresocial/ds-cs 0.1.1 → 0.1.2

package/README.md

@@ -3,8 +3,8 @@
 The CLI for [Dastyare Social — CS](https://cs.dastyare.social). Installs agent skills, wires up MCP, and authenticates to a channel.
 
 ```bash
-npx ds-cs init
-npx ds-cs add post-with-media
+npx @dastyaresocial/ds-cs init
+npx @dastyaresocial/ds-cs add post-with-media
 ```
 
 ## Why

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dastyaresocial/ds-cs",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "CLI for Dastyare Social — CS. Install DS-CS skills and third-party agent skills, wire up MCP, and authenticate to a channel.",
   "license": "MIT",
   "type": "module",

package/skills/README.md

@@ -3,9 +3,9 @@
 First-party skills for [Dastyare Social — CS](https://cs.dastyare.social). Install them with:
 
 ```bash
-npx ds-cs init
-npx ds-cs add                  # browse everything
-npx ds-cs add post-with-media  # or install one by name
+npx @dastyaresocial/ds-cs init
+npx @dastyaresocial/ds-cs add                  # browse everything
+npx @dastyaresocial/ds-cs add post-with-media  # or install one by name
 ```
 
 ## What is here
@@ -60,7 +60,7 @@ Add `metadata.internal: true` to hide a skill from discovery until `INSTALL_INTE
 While inside a DS-CS checkout, `ds-cs add` installs from this directory rather than from GitHub, so edits take effect immediately:
 
 ```bash
-npx ds-cs add brand-config --force
+npx @dastyaresocial/ds-cs add brand-config --force
 ```
 
 Run it from a scratch directory to test what a user actually gets:

package/src/index.mjs

@@ -31,7 +31,8 @@ const VERSION = await readVersion();
 const USAGE = `${bold("ds-cs")} — skills and tooling for Dastyare Social — CS
 
 ${bold("Usage")}
-  ds-cs <command> [options]
+  npx @dastyaresocial/ds-cs <command> [options]
+  (or \`ds-cs <command>\` once installed / linked globally)
 
 ${bold("Commands")}
   init [dir]              Prepare a project for DS-CS skills