@lukeguo12210/canvas-cli 0.0.2 → 0.0.4

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lukeguo12210/canvas-cli",
-  "version": "0.0.2",
-  "description": "Canvas LMS CLI and AI agent skills bundle for technical students.",
+  "version": "0.0.4",
+  "description": "Connect Canvas courses to AI agents: pull modules, files, assignments, pages, folders, and review packs without manual downloads.",
   "type": "module",
   "bin": {
     "canvas": "dist/bin/canvas.js"
@@ -28,9 +28,12 @@
     "canvas-lms",
     "cli",
     "agents",
+    "ai-agents",
     "skills",
     "students",
-    "education"
+    "education",
+    "study",
+    "coursework"
   ],
   "repository": {
     "type": "git",

package/skills/canvas-shared/SKILL.md

@@ -48,6 +48,7 @@ Implemented now:
 
 - `canvas auth login`
 - `canvas auth status`
+- `canvas auth schools search <query>`
 - `canvas auth logout`
 - `canvas config show`
 - `canvas me`
@@ -72,8 +73,8 @@ Planned but not implemented yet:
 ## Core Rules
 
 - Use `canvas auth status` first if auth state is uncertain.
-- If no auth config exists, ask the user to run `canvas auth login`.
-- Never print, paste, summarize, or expose a Canvas personal access token.
+- If no auth config exists, use `canvas auth schools search <query>` and then `canvas auth login --school <query> --token-env <env>` or `canvas auth login --school <query> --token <token>` when the user explicitly provides a PAT.
+- Never print, paste, summarize, or expose a Canvas personal access token after receiving it.
 - Default output is JSON and should be preferred for agents.
 - Use `--format pretty` only when presenting a compact human-facing result.
 - Use `--page-all` when completeness matters.
@@ -112,6 +113,7 @@ Do not include those in review packs unless the user explicitly asks.
 
 ```bash
 canvas auth status --format json
+canvas auth schools search "Columbia" --format json
 canvas courses list --active --page-all --format json
 canvas courses search "course name" --format json
 canvas courses overview <course-id> --format json

package/skills/canvas-shared/references/auth.md

@@ -4,6 +4,9 @@ Implemented auth commands:
 
 ```bash
 canvas auth login
+canvas auth login --school "Columbia" --token-env CANVAS_TOKEN
+canvas auth login --school-url https://courseworks2.columbia.edu --school-name "Columbia University (CourseWorks)" --token "paste-token-here"
+canvas auth schools search "Columbia" --format json
 canvas auth status --format json
 canvas auth logout
 canvas config show --format json
@@ -15,11 +18,49 @@ If `canvas` is not on `PATH`, use the npm exec fallback:
 ```bash
 npm exec --yes --package @lukeguo12210/canvas-cli -- canvas auth status --format json
 npm exec --yes --package @lukeguo12210/canvas-cli -- canvas auth login
+npm exec --yes --package @lukeguo12210/canvas-cli -- canvas auth login --school "Columbia" --token-env CANVAS_TOKEN
 ```
 
 Do not attempt `sudo npm install -g` from inside an agent session. Prefer the fallback above or ask the user to fix their npm global prefix.
 
-## Login Flow
+## Agent Login Flow
+
+Agents can complete login non-interactively when the user explicitly provides a Canvas PAT.
+
+1. Search schools:
+
+```bash
+canvas auth schools search "Columbia" --format json
+```
+
+2. Login with a known school match:
+
+```bash
+canvas auth login --school "Columbia" --token-env CANVAS_TOKEN
+```
+
+or, if the user provides the token directly in chat:
+
+```bash
+canvas auth login --school "Columbia" --token "paste-token-here"
+```
+
+3. For a custom Canvas URL:
+
+```bash
+canvas auth login --school-url https://courseworks2.columbia.edu --school-name "Columbia University (CourseWorks)" --token-env CANVAS_TOKEN
+```
+
+4. Verify:
+
+```bash
+canvas auth status --format json
+canvas courses list --active --page-all --format json
+```
+
+If `--school` matches multiple schools, run `canvas auth schools search <query>` and retry with a more specific value or use `--school-url`.
+
+## Interactive Login Flow
 
 `canvas auth login` is interactive.
 
@@ -40,9 +81,15 @@ Is this your school: Columbia University (CourseWorks) (https://courseworks2.col
 8. Validate token.
 9. Store local config.
 
-## Token Safety
+## Token Handling
+
+The CLI supports agent-provided PATs for initial setup:
+
+- `--token <PAT>`: direct token argument.
+- `--token-env <ENV_NAME>`: read token from an environment variable.
+- `--token-stdin`: read token from stdin.
 
-Never ask the user to paste a token into chat. The token should be pasted into the local terminal prompt from `canvas auth login`.
+Prefer `--token-env` or `--token-stdin` when possible. If the user pastes a PAT into chat, use it only for `canvas auth login`, then do not repeat, print, summarize, or store it anywhere except the Canvas config written by the CLI.
 
 Never print: