@dataworks-technology/cli 1.3.0 → 1.4.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dataworks-technology/cli",
-  "version": "1.3.0",
+  "version": "1.4.1",
   "description": "The official command-line interface for the Dataworks Data Engine",
   "type": "module",
   "license": "MIT",
@@ -36,18 +36,20 @@
     "dev": "node --import tsx ./bin/dev.js",
     "format": "prettier --write .",
     "format:check": "prettier --check .",
-    "generate": "bun scripts/generate-commands.ts",
-    "generate:check": "bun scripts/generate-commands.ts --check",
+    "generate": "bun scripts/generate-commands.ts && bun scripts/generate-metrics.ts",
+    "generate:check": "bun scripts/generate-commands.ts --check && bun scripts/generate-metrics.ts --check",
     "lint": "tsc --noEmit",
-    "typecheck": "tsc --noEmit",
     "maintain:sdk": "bun scripts/maintenance/update-sdk.ts",
     "postinstall": "node ./bin/postinstall.js",
+    "preinstall": "if [ -f scripts/get-sdk-authtoken.ts ]; then bun scripts/get-sdk-authtoken.ts ./; fi",
     "prepack": "bun run build && bun run test",
     "prepare": "husky",
+    "sdk": "bun scripts/get-sdk-authtoken.ts ./",
     "smoke:litellm": "bun scripts/maintenance/smoke-agent.ts",
     "sync:plugin-version": "bun scripts/sync-plugin-version.ts",
     "test": "vitest run",
-    "test:watch": "vitest"
+    "test:watch": "vitest",
+    "typecheck": "tsc --noEmit"
   },
   "oclif": {
     "bin": "dw",
@@ -84,6 +86,7 @@
   "devDependencies": {
     "@commitlint/cli": "19.8.1",
     "@commitlint/config-conventional": "19.8.1",
+    "@dataworks/sdk": "3.5.0",
     "@types/node": "22.18.0",
     "husky": "9.1.7",
     "lint-staged": "16.1.5",

package/plugins/dataworks/.claude-plugin/plugin.json

@@ -1,17 +1,10 @@
 {
   "name": "dataworks",
-  "version": "1.3.0",
+  "version": "1.4.1",
   "description": "Query athlete metrics from Dataworks using the authenticated local CLI session.",
-  "author": {
-    "name": "Dataworks Technology"
-  },
+  "author": { "name": "Dataworks Technology" },
   "homepage": "https://github.com/Dataworks-Technology/Dataworks-CLI",
   "repository": "https://github.com/Dataworks-Technology/Dataworks-CLI",
   "license": "MIT",
-  "keywords": [
-    "dataworks",
-    "metrics",
-    "sport",
-    "data-explorer"
-  ]
+  "keywords": ["dataworks", "metrics", "sport", "data-explorer"]
 }

package/plugins/dataworks/.codex-plugin/plugin.json

@@ -1,20 +1,12 @@
 {
   "name": "dataworks",
-  "version": "1.3.0",
+  "version": "1.4.1",
   "description": "Query athlete metrics from Dataworks using the authenticated local CLI session.",
-  "author": {
-    "name": "Dataworks Technology",
-    "url": "https://dataworks.live/"
-  },
+  "author": { "name": "Dataworks Technology", "url": "https://dataworks.live/" },
   "homepage": "https://github.com/Dataworks-Technology/Dataworks-CLI",
   "repository": "https://github.com/Dataworks-Technology/Dataworks-CLI",
   "license": "MIT",
-  "keywords": [
-    "dataworks",
-    "metrics",
-    "sport",
-    "data-explorer"
-  ],
+  "keywords": ["dataworks", "metrics", "sport", "data-explorer"],
   "skills": "./skills/",
   "mcpServers": "./.mcp.json",
   "interface": {
@@ -23,9 +15,7 @@
     "longDescription": "Resolve athletes and return normalized GPS, heart-rate, and other Dataworks metric values through one read-only tool.",
     "developerName": "Dataworks Technology",
     "category": "Data",
-    "capabilities": [
-      "Read"
-    ],
+    "capabilities": ["Read"],
     "websiteURL": "https://dataworks.live/",
     "defaultPrompt": [
       "Give me the last 30 GPS values for James Haigh",

package/plugins/dataworks/skills/query-dataworks-metrics/SKILL.md

@@ -16,23 +16,43 @@ in Claude Code. Do not substitute raw GraphQL or guess that setup succeeded.
 
 - Pass `athlete_id` when the user provides a Dataworks athlete public ID.
 - Otherwise pass `athlete_name`; let the tool resolve it and surface ambiguity.
-- Pass the user's metric wording directly. The tool understands GPS/location and
-  heart-rate/HR/BPM aliases, plus common speed, altitude, cadence, power, and
-  timing names.
+- Map the user's wording onto a canonical metric name from the catalogue below.
+  Case, spaces, hyphens and underscores are ignored, so "Heart Rate" resolves to
+  `heartrate`. Do not invent a metric name.
 - Default to `limit: 30` and `order: newest` only when the user did not specify
   a count or order.
 - Preserve explicit `from` and `to` times as ISO 8601 date-times.
 - Pass `event_id`, `dataset_datasource_id`, or `tenant_id` only when explicitly
   supplied or already resolved. Never guess an ID.
-- For an unknown custom metric, pass its exact name and explicit
-  `metric_category`.
+- For a genuinely custom metric absent from the catalogue, pass its exact name
+  and an explicit `metric_category`.
+
+## Metric catalogue
+
+Canonical names, grouped by Data Explorer category. This list is generated from
+`@dataworks/sdk`, the same source the Console's Data Explorer uses.
+
+<!-- generated:metrics start -->
+
+- **METRICS_TYPE_A** — `latlong`, `net-time`, `checkpoint-time`, `leg-time`, `sub-time`, `checkpoint`, `segment`, `distance`, `distance-swim`, `distance-bike`, `distance-run`, `lap`, `sector`, `status`, `is-drafting`, `total-drafting-seconds`, `heading-degrees`, `yoyo-count`
+- **METRICS_TYPE_B** — `speed`, `location-speed`, `altitude`, `cadence-cycling`, `cadence`, `active-energy-burned`, `horizontal-accuracy`, `gap-to-leader`, `gap-to-ahead`, `time-to-leader`, `rank`, `speed-bike`, `pace`, `pace-swim`, `pace-run`
+- **METRICS_TYPE_C** — `heartrate`, `power`, `power-cycling`, `pwr_instant`
+<!-- generated:metrics end -->
+
+Aliases also accepted: `gps`/`location`/`position` → `latlong`;
+`hr`/`bpm`/`pulse` → `heartrate`; `watts` → `power`; `rpm` → `cadence`;
+`elevation` → `altitude`; `calories` → `active-energy-burned`;
+`placing` → `rank`.
+
+There is no `timing` metric — use `net-time`, `checkpoint-time`, `leg-time`, or
+`sub-time`.
 
 Examples:
 
 - “Give me the last 30 GPS values for James Haigh” → `athlete_name: "James
 Haigh"`, `metric: "GPS"`, `limit: 30`, `order: "newest"`.
-- “Latest heart rate for athlete ID X” → `athlete_id: "X"`, `metric: "heart
-rate"`, `limit: 1`.
+- “Tell me James Haigh's maximum heart rate” → `athlete_name: "James Haigh"`,
+  `metric: "heartrate"`, then take the maximum over the returned rows.
 - “Cadence for Sam since noon” → `athlete_name: "Sam"`, `metric: "cadence"`,
   `from: <the unambiguous ISO 8601 time requested>`.
 
@@ -45,4 +65,6 @@ numeric with unit `bpm` when the source value is valid.
 
 If the tool reports `ATHLETE_AMBIGUOUS`, present its candidates and ask the user
 to choose. For `AUTH_REQUIRED` or `TENANT_REQUIRED`, follow the recovery command
-in the error and retry. Never expose credentials or session material.
+in the error and retry. For `METRIC_CATEGORY_REQUIRED`, the error's `suggestions`
+list the closest canonical names — retry with one rather than asking the user to
+spell the metric. Never expose credentials or session material.