coursmith 0.1.0 → 0.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "coursmith",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Publish AI-written courses to Coursmith from Claude Code, Codex, Cursor, OpenCode or any agent with a shell.",
   "repository": {
     "type": "git",

package/skill/coursmith-course/SKILL.md

@@ -9,9 +9,9 @@ You write a course as a folder containing `course.json` and an `assets/` directo
 `coursmith` CLI, and submit it. A review agent on the portal then approves it, asks for a revision or
 rejects it. Your job ends when the course is approved, or when you have explained the review outcome to the user.
 
-Run the CLI as `coursmith <command> --json`. It is installed from the private repository (the npm package
-`coursmith` is not published yet); if the command is missing, ask the user to follow the installation guide
-at `/install` before continuing. With `--json` every command prints one JSON document; read it instead of guessing.
+Run the CLI as `npx --yes coursmith@latest <command> --json`. The public npm package includes the CLI and this skill;
+no GitHub access or global installation is needed. If `npx` is missing, ask the user to install Node.js 20 or newer
+and follow the guide at `/install`. With `--json` every command prints one JSON document; read it instead of guessing.
 
 Reference files in this skill folder (read them when you reach the matching step):
 
@@ -26,10 +26,10 @@ Reference files in this skill folder (read them when you reach the matching step
 
 ## 1. Log in
 
-1. Run `coursmith whoami --json`. If it prints a `username`, continue to step 2.
-2. Otherwise run `coursmith login --no-wait --json`. Show the user the `verificationUri` and the
+1. Run `npx --yes coursmith@latest whoami --json`. If it prints a `username`, continue to step 2.
+2. Otherwise run `npx --yes coursmith@latest login --no-wait --json`. Show the user the `verificationUri` and the
    `userCode` and ask them to open the link, check the code and click **Approve**.
-3. When the user confirms, run `coursmith login --resume --json` and check that it prints `logged_in`.
+3. When the user confirms, run `npx --yes coursmith@latest login --resume --json` and check that it prints `logged_in`.
 
 ## 2. Agree on the course with the user
 
@@ -92,7 +92,7 @@ Write section by section and keep the language, difficulty and terminology consi
 
 ## 6. Validate until clean
 
-Run `coursmith validate <folder> --json`. It prints `{ "ok": ..., "issues": [...] }`; each issue has
+Run `npx --yes coursmith@latest validate <folder> --json`. It prints `{ "ok": ..., "issues": [...] }`; each issue has
 `severity`, `code`, `path` (for example `sections[1].steps[0].blocks[2]`) and `message`.
 
 Fix every `error`, then run it again. Repeat until `ok` is `true`. Fix warnings too when they are cheap
@@ -100,10 +100,10 @@ Fix every `error`, then run it again. Repeat until `ok` is `true`. Fix warnings
 
 ## 7. Submit and follow the review
 
-1. Run `coursmith submit <folder> --json`. It uploads the course and prints `status: "in_review"`
+1. Run `npx --yes coursmith@latest submit <folder> --json`. It uploads the course and prints `status: "in_review"`
    with a `submissionId`. The CLI writes `.coursmith.json` in the folder; keep it, because it links later
    submissions to the same course.
-2. Run `coursmith status --dir <folder> --wait --json` (it waits up to 10 minutes; run it again if
+2. Run `npx --yes coursmith@latest status --dir <folder> --wait --json` (it waits up to 10 minutes; run it again if
    the status is still `in_review`).
 3. Act on the `status`:
    - `approved`: give the user the `courseUrl`. Mention any optional suggestions in `review.issues`.
@@ -124,7 +124,7 @@ the current one stays online; keep step ids stable so learners keep their progre
 | CLI output | What to do |
 |---|---|
 | `not_logged_in` / exit code 3 | Go back to step 1. |
-| `client_outdated` | Ask the user to update the CLI from the repository (`git pull`, rebuild, `npm install -g ./packages/cli`), then retry. |
+| `client_outdated` | Retry with `npx --yes coursmith@latest` so npm fetches the latest CLI. |
 | `validation_failed` from `submit` | Run `validate` and fix the issues it lists. |
 | `rate_limited` | The user reached the daily submission limit; try again tomorrow. |
 | `assets.content_type` / `assets.invalid` | The file content does not match its extension, or it is corrupt. Re-export it. |