@lukeguo12210/canvas-cli 0.0.1

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

@@ -0,0 +1,46 @@
+# Canvas Output Reference
+
+Default output is JSON.
+
+All command results should use this shape:
+
+```json
+{
+  "ok": true,
+  "data": {},
+  "meta": {
+    "request": {
+      "method": "GET",
+      "path": "/api/v1/courses"
+    }
+  }
+}
+```
+
+Errors use:
+
+```json
+{
+  "ok": false,
+  "error": {
+    "code": "NO_AUTH_CONFIG",
+    "message": "No Canvas auth config found. Run canvas auth login.",
+    "retryable": false
+  }
+}
+```
+
+## Formats
+
+```bash
+--format json      # default, best for agents
+--format pretty    # compact human display
+--format table     # simple list display
+--format ndjson    # batch/streaming workflows
+```
+
+Use JSON for reasoning and tool chaining. Use pretty only when the user wants a readable summary.
+
+## Redaction
+
+The CLI redacts token-like values from output. Agents must still avoid asking users to paste tokens into chat.

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

@@ -0,0 +1,24 @@
+# Canvas Pagination Reference
+
+Canvas list endpoints can be paginated.
+
+Use:
+
+```bash
+canvas courses list --active --page-all --format json
+```
+
+General flags:
+
+```bash
+--page-all
+--page-limit <n>
+--page-size <n>
+--page-delay <ms>
+```
+
+Important rule:
+
+Canvas pagination follows HTTP `Link` headers. Do not synthesize next-page URLs manually.
+
+When completeness matters, use `--page-all`. For quick exploratory commands, one page may be enough.