systemlink-cli 1.13.5__tar.gz → 1.13.7__tar.gz

{systemlink_cli-1.13.5 → systemlink_cli-1.13.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: systemlink-cli
-Version: 1.13.5
+Version: 1.13.7
 Summary: SystemLink Integrator CLI - cross-platform CLI for SystemLink workflows and templates.
 License-File: LICENSE
 Author: Fred Visser

{systemlink_cli-1.13.5 → systemlink_cli-1.13.7}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "systemlink-cli"
-version = "1.13.5"
+version = "1.13.7"
 description = "SystemLink Integrator CLI - cross-platform CLI for SystemLink workflows and templates."
 authors = ["Fred Visser <fred.visser@emerson.com>"]
 packages = [{ include = "slcli" }]

{systemlink_cli-1.13.5 → systemlink_cli-1.13.7}/slcli/_version.py

@@ -1,4 +1,4 @@
 """Version information for slcli."""
 
 # This file is auto-generated. Do not edit manually.
-__version__ = "1.13.5"
+__version__ = "1.13.7"

{systemlink_cli-1.13.5 → systemlink_cli-1.13.7}/slcli/main.py

@@ -64,7 +64,7 @@ def _configure_rich_click_command_groups() -> None:
         "slcli": [
             {
                 "name": "Configure",
-                "commands": ["config", "login", "logout", "info", "completion"],
+                "commands": ["config", "login", "logout", "info", "completion", "example"],
             },
             {
                 "name": "Administer",
@@ -89,7 +89,7 @@ def _configure_rich_click_command_groups() -> None:
             },
             {
                 "name": "Validate & Plan",
-                "commands": ["testmonitor", "template", "spec", "workitem", "example"],
+                "commands": ["testmonitor", "template", "spec", "workitem"],
             },
         ]
     }

{systemlink_cli-1.13.5 → systemlink_cli-1.13.7}/slcli/skills/slcli/SKILL.md

@@ -24,6 +24,16 @@ compatibility: >-
 metadata:
   author: ni-kismet
   version: "2.0"
+---
+
+## Command style
+
+Prefer long option names in generated commands and examples. Use `--format json`,
+`--take 25`, `--workspace Default`, and `--output path.json` instead of `-f json`,
+`-t 25`, `-w Default`, or `-o path.json`.
+
+Only mention short aliases when explicitly documenting that they exist.
+
 #   --system SYSTEM_ID    Assign a system (by minion/system ID). Repeatable.
 #   --fixture ASSET_ID    Assign a fixture/slot (by asset ID, asset type FIXTURE). Repeatable.
 #   --dut ASSET_ID        Assign a DUT (by asset ID, asset type DEVICE_UNDER_TEST). Repeatable.
@@ -36,22 +46,22 @@ slcli workitem schedule <WORK_ITEM_ID> \
   [--system SYSTEM_ID]... [--fixture ASSET_ID]... [--dut ASSET_ID]...
 
 # Work item template subgroup
-slcli workitem template list [-w WORKSPACE] [--filter TEXT] [-t INT] [-f json]
-slcli workitem template get <TEMPLATE_ID> [-f json]
-slcli workitem template create --name TEXT --type TEXT --template-group TEXT [-w WORKSPACE] [OPTIONS]
+slcli workitem template list [--workspace WORKSPACE] [--filter TEXT] [--take INT] [--format json]
+slcli workitem template get <TEMPLATE_ID> [--format json]
+slcli workitem template create --name TEXT --type TEXT --template-group TEXT [--workspace WORKSPACE] [OPTIONS]
 slcli workitem template update <TEMPLATE_ID> [--name TEXT] [--description TEXT] [--summary TEXT]
 slcli workitem template delete <TEMPLATE_ID>... [--yes]
 
 # Workflow subgroup
-slcli workitem workflow list [-w WORKSPACE] [-t INT] [-f json]
-slcli workitem workflow get [--id WORKFLOW_ID] [--name NAME] [-f json]
+slcli workitem workflow list [--workspace WORKSPACE] [--take INT] [--format json]
+slcli workitem workflow get [--id WORKFLOW_ID] [--name NAME] [--format json]
 slcli workitem workflow init [--name TEXT] [--directory DIR]   # Scaffold a local workflow file
-slcli workitem workflow create --file PATH [-w WORKSPACE]      # Create from JSON file
-slcli workitem workflow import --file PATH [-w WORKSPACE]      # Import workflow from JSON
-slcli workitem workflow export [--id WORKFLOW_ID] [--name NAME] [-o FILE]  # Export to JSON
+slcli workitem workflow create --file PATH [--workspace WORKSPACE]      # Create from JSON file
+slcli workitem workflow import --file PATH [--workspace WORKSPACE]      # Import workflow from JSON
+slcli workitem workflow export [--id WORKFLOW_ID] [--name NAME] [--output FILE]  # Export to JSON
 slcli workitem workflow update --id WORKFLOW_ID --file PATH    # Update from JSON file
 slcli workitem workflow delete --id WORKFLOW_ID [--yes]
-slcli workitem workflow preview [--file PATH] [--id WORKFLOW_ID] [--html] [--no-open] [-o FILE]
+slcli workitem workflow preview [--file PATH] [--id WORKFLOW_ID] [--html] [--no-open] [--output FILE]
 ```
 
 **Create work item options:**
@@ -82,9 +92,9 @@ Scaffold, package, and publish custom web applications to SystemLink.
 ```bash
 slcli webapp init <DIRECTORY>                      # Scaffold the Angular starter
 slcli webapp manifest init <DIRECTORY> [OPTIONS]  # Create nipkg.config.json for packaging
-slcli webapp pack [FOLDER] [--config FILE] [-o OUTPUT_FILE]  # Package a webapp into a .nipkg
-slcli webapp list [-w WORKSPACE] [-t INT] [-f json]
-slcli webapp get <WEBAPP_ID> [-f json]
+slcli webapp pack [FOLDER] [--config FILE] [--output OUTPUT_FILE]  # Package a webapp into a .nipkg
+slcli webapp list [--workspace WORKSPACE] [--take INT] [--format json]
+slcli webapp get <WEBAPP_ID> [--format json]
 slcli webapp publish PATH [--workspace NAME]             # Upload and publish a webapp
 slcli webapp delete <WEBAPP_ID>
 slcli webapp open <WEBAPP_ID>                            # Open webapp URL in browser
@@ -95,19 +105,19 @@ slcli webapp open <WEBAPP_ID>                            # Open webapp URL in br
 Create, inspect, import, export, and revert saved software states managed by the SystemLink Systems State service.
 
 ```bash
-slcli state list [-w WORKSPACE] [--architecture CHOICE] [--distribution CHOICE] [-t INT] [-f json]
-slcli state get <STATE_ID> [-f json]
+slcli state list [--workspace WORKSPACE] [--architecture CHOICE] [--distribution CHOICE] [--take INT] [--format json]
+slcli state get <STATE_ID> [--format json]
 slcli state create --name TEXT --distribution CHOICE --architecture CHOICE [OPTIONS]
 slcli state update <STATE_ID> [OPTIONS]
 slcli state delete <STATE_ID> [--yes]
 
 slcli state import --name TEXT --distribution CHOICE --architecture CHOICE --file PATH [OPTIONS]
-slcli state replace-content <STATE_ID> --file PATH [--change-description TEXT] [-f json]
+slcli state replace-content <STATE_ID> --file PATH [--change-description TEXT] [--format json]
 slcli state export <STATE_ID> [--version VERSION] [--inline | --output FILE]
 slcli state capture <SYSTEM_ID> [--inline | --output FILE]
 
-slcli state history <STATE_ID> [-t INT] [-f json]
-slcli state version <STATE_ID> <VERSION> [-f json]
+slcli state history <STATE_ID> [--take INT] [--format json]
+slcli state version <STATE_ID> <VERSION> [--format json]
 slcli state revert <STATE_ID> <VERSION> [--yes]
 ```
 
@@ -148,7 +158,7 @@ Install pre-built demo configurations (systems, assets, DUTs, templates, etc.)
 for training, testing, or evaluation.
 
 ```bash
-slcli example list [-f json]                             # List available examples
+slcli example list [--format json]                       # List available examples
 slcli example info <EXAMPLE_ID>                          # Show example details
 slcli example install <EXAMPLE_ID> [--workspace NAME]    # Provision example resources
 slcli example delete <EXAMPLE_ID> [--workspace NAME]     # Remove provisioned resources
@@ -175,7 +185,7 @@ SystemLink Enterprise (SLE) or require a specific microservice to be deployed.
 
 ```bash
 slcli info                # Shows platform type and service health
-slcli info -f json        # Machine-readable; check .services for per-service status
+slcli info --format json # Machine-readable; check .services for per-service status
 ```
 
 | Command group                | Required service     | SLE | SLS | Notes                                   |
@@ -231,7 +241,7 @@ to disable caching for debugging.
 
 ## Key rules
 
-1. **Always use `-f json`** when piping output to `jq` or doing programmatic analysis.
+1. **Always use `--format json`** when piping output to `jq` or doing programmatic analysis.
 2. **Use `--summary --group-by`** for aggregation instead of fetching all records and counting.
 3. **Use convenience filters first** (e.g., `--status FAILED`), fall back to `--filter` for complex queries.
 4. **Parameterize `--filter` queries** — use `--substitution` instead of string interpolation.

{systemlink_cli-1.13.5 → systemlink_cli-1.13.7}/slcli/skills/systemlink-notebook/SKILL.md

@@ -20,6 +20,84 @@ argument-hint: 'Describe the notebook purpose and what data it should report on'
 - Creating a test data analysis notebook
 - Deploying a notebook to SystemLink via `slcli`
 
+## Important: Python Client Quirks
+
+The `nisystemlink-clients` Python package has a few ergonomics quirks to be aware of:
+
+### API naming inconsistency
+
+Client methods use Python `snake_case`, but request model fields use `camelCase`. This requires careful attention:
+
+```python
+# ❌ WRONG: Using Python snake_case (very intuitive but incorrect)
+CreateResultRequest(program_name="My Test", file_ids=[file_id])
+
+# ✅ CORRECT: Must use camelCase field names from the request model
+CreateResultRequest(programName="My Test", fileIds=[file_id])
+
+# Methods stay snake_case:
+client.create_results(request)  # This is correct
+client.create_steps(...)         # This is correct
+```
+
+Always check the request model constructor signature, not what "feels" Pythonic.
+
+### Partial-success responses
+
+Operations like `create_results()` and `create_steps()` return partial-success wrapper types
+(e.g., `CreateStepsPartialSuccess`) even when successful. These contain both success and failure data:
+
+```python
+from nisystemlink.clients.testmonitor import TestMonitorClient
+from nisystemlink.clients.testmonitor.models import CreateStepRequest
+
+client = TestMonitorClient()
+response = client.create_steps([CreateStepRequest(...)])
+
+# Success and failures are both in the response
+if response.failed:
+    print(f"Failed to create {len(response.failed)} steps")
+if response.created:
+    print(f"Successfully created {len(response.created)} steps")
+```
+
+### Limited service coverage
+
+The Python client does **not cover all SystemLink services**. The most important gaps for notebooks (see the [client repo](https://github.com/ni/nisystemlink-clients-python) for the current full list):
+
+- ❌ **Notebook Execution** — no Python client for execution lifecycle management
+- ❌ **Routines v1/v2** — no Python client for scheduling/triggering
+- ❌ **Systems State** — no Python client for system health queries
+- ❌ **Comments** — no Python client for resource annotations
+- ❌ **User Data** — no Python client for key-value stores
+- ❌ **Tag Historian** — no Python client for time-series history
+
+For these services, use REST calls directly via the `requests` library or SystemLink's OpenAPI SDKs.
+
+### Public import paths
+
+This skill uses two distinct Python SDK namespaces — be careful not to mix them:
+
+- **`nisystemlink.clients.*`** — the typed Python client (`nisystemlink-clients` package). Use public top-level imports.
+- **`systemlink.clients.nisysmgmt.*`** — a separate OpenAPI-generated SDK used only for Systems queries.
+
+For `nisystemlink.clients`, always import from the public top-level modules, not private `_module` paths:
+
+```python
+# ✅ CORRECT: Public paths (nisystemlink-clients)
+from nisystemlink.clients.file import FileClient
+from nisystemlink.clients.testmonitor import TestMonitorClient
+from nisystemlink.clients.testmonitor.models import CreateResultRequest, CreateStepRequest
+
+# ❌ WRONG: Private module paths (may change or be removed)
+from nisystemlink.clients.testmonitor._test_monitor_client import TestMonitorClient
+from nisystemlink.clients.testmonitor.models._create_result_request import CreateResultRequest
+
+# Separate SDK — used only for Systems queries:
+from systemlink.clients.nisysmgmt.api.systems_api import SystemsApi
+from systemlink.clients.nisysmgmt.models.query_systems_request import QuerySystemsRequest
+```
+
 ## Notebook Structure
 
 Every SystemLink notebook follows this cell pattern:
@@ -76,7 +154,13 @@ in the cell's `.metadata` field for SystemLink to recognize the parameters and o
 - `tags: ["parameters"]` is **required** — this is how papermill identifies the cell
 - `systemlink.version` must be `2` for most notebooks, or `1` for **Work Item Automations**
 - Supported parameter types: `string`, `integer`, `float`, `boolean`, `string[]`
-- Supported output types: `data_frame`, `scalar`, `string`, `string[]`
+- Supported scrapbook output types: `data_frame`, `scalar`, `string`, `string[]`
+- Some interfaces define additional descriptor values outside the standard scrapbook output
+  types. For example, Data Space Analysis returns analysis option descriptors whose
+  `type` can be `scalar` or `vector`.
+- **Grafana restriction:** Notebooks intended for use in Grafana dashboards can only
+  output `data_frame` and `scalar` types. The `string` and `string[]` output types
+  are not supported by the Grafana plugin.
 
 ### Work Item Automations pattern
 
@@ -199,33 +283,59 @@ import scrapbook as sb
 from systemlink.clients.nisysmgmt.api.systems_api import SystemsApi
 from systemlink.clients.nisysmgmt.models.query_systems_request import QuerySystemsRequest
 
-# Test results
+# Test results (remember: camelCase field names in request models)
 from nisystemlink.clients.testmonitor import TestMonitorClient
+from nisystemlink.clients.testmonitor.models import CreateResultRequest, CreateStepRequest
 from nisystemlink.clients.core import HttpConfigurationManager
 
 # Assets
 from nisystemlink.clients.assetmanagement import AssetManagementClient
 
-# Direct HTTP (when no typed client exists)
+# Direct HTTP (when no typed client exists or for missing services)
 import requests
 config = HttpConfigurationManager.get_configuration()
 base_url = config.server_uri.rstrip("/")
-headers = {"x-ni-api-key": config.api_keys[0]}
+api_keys = getattr(config, "api_keys", {})
+api_key = api_keys.get("x-ni-api-key") if isinstance(api_keys, dict) else None
+if not api_key:
+  raise RuntimeError("Configure an x-ni-api-key before using REST fallbacks.")
+headers = {"x-ni-api-key": api_key}
 ```
 
+### Available Python client services
+
+The Python client covers these **15 main services**:
+- `alarm`, `artifact`, `assetmanagement`, `dataframe`, `feeds`, `file`, `notebook`,
+  `notification`, `product`, `spec`, `systems`, `tag`, `test_plan`, `testmonitor`, `work_item`
+
+### Missing services (use REST directly)
+
+If you need these services, call the REST API directly using `requests` and the OpenAPI docs:
+- **Notebook Execution** — execution lifecycle (use OpenAPI directly)
+- **Routines v1/v2** — scheduling/triggering (use OpenAPI directly)
+- **Systems State** — system health/connection status (use OpenAPI directly)
+- **Comments** — resource annotations (use OpenAPI directly)
+- **User Data** — key-value stores (use OpenAPI directly)
+- **Tag Historian** — time-series history (use OpenAPI directly)
+- **Auth**, **User**, and others — see full list in service-gaps documentation
+
 ## Client and API References
 
-- Prefer the official Python client libraries when they cover the target service:
+- **Python client repository** — full source and examples:
   https://github.com/ni/nisystemlink-clients-python
-- If a SystemLink service does not have a Python client yet, call the REST API
-  directly and use the hosted OpenAPI docs to discover endpoints and schemas:
+- **SystemLink OpenAPI docs** — for all services, including those without Python clients:
   https://demo-api.lifecyclesolutions.ni.com/niapis/
-- For notebook patterns and end-to-end examples, check the SystemLink Enterprise
-  examples repository:
+- **SystemLink Enterprise examples** — end-to-end patterns:
   https://github.com/ni/systemlink-enterprise-examples/
 
-When using direct HTTP, prefer the OpenAPI docs first to confirm the service base
-path, request body shape, and response schema before writing notebook code.
+When using the Python client:
+- Always check the request model constructor signature for camelCase field names (they won't match Python snake_case)
+- Expect `create_*` operations to return partial-success wrapper types; inspect `.created` and `.failed` attributes
+- Use public import paths from top-level modules, not private `_module` paths
+
+When a service lacks a Python client, use OpenAPI docs to discover the endpoint path,
+request body shape, and response schema before writing HTTP calls.
+
 ## Systems Query Pattern
 
 The `SystemsApi` uses a projection/filter pattern for querying:

systemlink_cli-1.13.7/slcli/skills/systemlink-notebook/references/interfaces.md

@@ -0,0 +1,185 @@
+# Notebook Interfaces
+
+When deploying a notebook to SystemLink, you can assign an **interface** that tells
+SystemLink how the notebook will be used. This affects how parameters are presented
+and how the notebook is triggered.
+
+Set the interface during creation or update:
+
+```bash
+slcli notebook manage update --id <ID> --interface "Systems Grid"
+```
+
+Prefer `create --interface ...` when you are creating a new notebook. Use
+`update --interface ...` for in-place interface changes on an existing notebook.
+Delete and re-create only if the server rejects the update.
+
+## Service Availability Note
+
+The Python client does not cover every SystemLink service. Key gaps that affect
+automation interfaces (see the `nisystemlink-clients` repository for the current
+service list):
+
+- ❌ **Notebook Execution** — No Python client for checking execution status or logs
+- ❌ **Routines v1/v2** — No Python client for scheduling; use REST directly or `slcli routine` in scheduled shells
+- ❌ **Comments** — No Python client for adding resource annotations
+- ❌ **User** — No Python client for querying users/workspaces (use REST directly)
+
+For these services in notebooks, call the REST API directly via the `requests`
+library and the service-specific SystemLink OpenAPI docs.
+
+## Available Interfaces
+
+Reference: [Publishing a Jupyter Notebook (NI Docs)](https://www.ni.com/docs/en-US/bundle/systemlink-enterprise/page/publishing-a-jupyter-notebook.html)
+
+> **Note:** SystemLink Enterprise does not strictly enforce the selected interface name.
+> The service can still execute a notebook even if the interface-specific metadata is
+> incomplete. However, parameter injection, UI rendering, and output handling still depend
+> on the appropriate papermill and `systemlink` metadata being present.
+
+| Interface                    | Use Case                                                                                                                                                                    | Required Inputs                                                                                                                                                      | Required Outputs                                                                                                                                                                                                                                                        |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Assets Grid**              | Not currently in use                                                                                                                                                        | —                                                                                                                                                                    | —                                                                                                                                                                                                                                                                       |
+| **Data Table Analysis**      | Analyze data table contents. Detailed input and output requirements are not yet documented in this reference.                                                               | See NI docs                                                                                                                                                          | See NI docs                                                                                                                                                                                                                                                             |
+| **Data Space Analysis**      | Analyze parametric data in a data space and calculate statistics                                                                                                            | `trace_data`: `dict[str, str]` (artifact reference, for example `{"artifact_id": "..."}`)<br>`analysis_options`: `string[]`<br>`workspace_id`: `string`              | List of analysis options: `[{display_name, id, type: scalar/vector}]`                                                                                                                                                                                                   |
+| **File Analysis**            | Analyze a file or create a routine with a file change trigger                                                                                                               | `file_ids`: string[]                                                                                                                                                 | No output required                                                                                                                                                                                                                                                      |
+| **Periodic Execution**       | Scheduled recurring notebook (e.g. daily/hourly reports)                                                                                                                    | No input required                                                                                                                                                    | No output required                                                                                                                                                                                                                                                      |
+| **Resource Changed Routine** | Triggered when a resource changes (via v1 routines)                                                                                                                         | `context`: `dict` containing `routine_id`, `correlation_id`, `triggered_at`, `resource_type`, `before` (snapshot before change), and `after` (snapshot after change) | No output required                                                                                                                                                                                                                                                      |
+| **Specification Analysis**   | Analyze chosen specifications                                                                                                                                               | `spec_ids`: `string[]`<br>`product_id`: `string`                                                                                                                     | No output required                                                                                                                                                                                                                                                      |
+| **Systems Grid**             | Report that adds a column to the Systems management grid                                                                                                                    | No input required                                                                                                                                                    | `data_frame` with `minion id` as the first column. Example: `[{"display_name": "Package Version", "id": "package_version", "type": "data_frame", "data": {"columns": ["minion id", "package version"], "values": [["minion-id-1", "23.5"], ["minion-id-2", "24.0"]]}}]` |
+| **Test Data Analysis**       | Analyze chosen test results                                                                                                                                                 | `result_ids`: string[]                                                                                                                                               | No output required                                                                                                                                                                                                                                                      |
+| **Test Data Extraction**     | Extract parametric data from files (BDC, STDF) and transform into test results, steps, and measurements                                                                     | `file_id`: `string`<br>`part_number`: `string`<br>`notebook_id`: `string`                                                                                            | No output required                                                                                                                                                                                                                                                      |
+| **Work Item Automations**    | Perform automated actions on one or more work items for customer-specific use cases. Notebooks appear in the work items UI and can be manually triggered on selected items. | `work_item_ids`: string[]                                                                                                                                            | No output required                                                                                                                                                                                                                                                      |
+| **Work Item Operations**     | Invoked by the system through the action of a work item execution                                                                                                           | `workItemId`: `string`<br>`systemId`: `string`<br>May also receive user-defined parameters                                                                           | No output required                                                                                                                                                                                                                                                      |
+| **Work Item Scheduler**      | Schedule work items using a custom algorithm                                                                                                                                | `work_item_ids`: string[]                                                                                                                                            | No output required                                                                                                                                                                                                                                                      |
+
+### Grafana Compatibility
+
+Notebooks whose outputs are consumed by the SystemLink Grafana plugin can only use
+`data_frame` and `scalar` output types. The `string` and `string[]` types are not
+supported by Grafana.
+
+## Common Interface Patterns
+
+### Systems Grid
+
+Parameters typically include:
+
+- `group_by` (string) — always support "System"
+- `systems_filter` (string) — filter expression for which systems
+- Domain-specific params (e.g. `package` for package version)
+
+Output must be `data_frame` with `minion id` as the first column.
+
+### Test Data Analysis
+
+Parameters typically include:
+
+- `group_by` (string)
+- `program_name` (string)
+- `status_filter` (string)
+- `systems_filter` (string)
+
+### Periodic Execution
+
+No special parameter requirements. Typically uses fixed configuration
+or reads from tags/files. Can be scheduled via routines (no Python client available).
+
+**Note:** The Python client does not have a Routines service. Use `slcli routine` to
+schedule notebooks, or call the Routines REST API directly.
+
+Create a scheduled routine via CLI:
+
+```bash
+slcli routine create --api-version v1 \
+  --name "Daily Report" \
+  --type SCHEDULED \
+  --notebook-id <NOTEBOOK_ID> \
+  --schedule '{"startTime":"2026-01-01T00:00:00Z","repeat":"DAY"}'
+```
+
+Or create a scheduled routine via REST using `HttpConfigurationManager` and `requests`:
+
+```python
+import requests
+from nisystemlink.clients.core import HttpConfigurationManager
+
+config = HttpConfigurationManager.get_configuration()
+base_url = config.server_uri.rstrip("/")
+api_keys = getattr(config, "api_keys", {})
+api_key = api_keys.get("x-ni-api-key") if isinstance(api_keys, dict) else None
+if not api_key:
+    raise RuntimeError("Configure an x-ni-api-key before using REST fallbacks.")
+headers = {"x-ni-api-key": api_key}
+
+payload = {
+    "name": "Daily Report",
+    "type": "SCHEDULED",
+    "notebookId": "<NOTEBOOK_ID>",
+    "schedule": {"startTime": "<START_TIME_ISO8601>", "repeat": "DAY"}
+}
+
+resp = requests.post(f"{base_url}/niroutine/v1/routines", json=payload, headers=headers)
+resp.raise_for_status()
+```
+
+### Work Item Automations
+
+Use this interface for notebooks that act on selected work items (close, update,
+assign, etc.). The notebook appears in the work items UI and can be manually
+triggered on one or more selected work items.
+
+Parameters are injected by the work item system:
+
+- `work_item_ids` (string[]) — list of selected work item IDs. Default: `[]`
+- `workspace` (string) — workspace context (optional)
+
+**Critical:** `work_item_ids` must be typed as `"string[]"` (not `"string"`),
+default to `[]` in both papermill and the code cell, and `systemlink.version`
+must be `1`. See the systemlink-notebook skill for the full metadata example.
+
+**Service note:** The Python client has `work_item` service for querying and updating
+work items, but does not have a `comments` service. If your automation needs to add
+comments or notes, call the Comments REST API directly via `requests` library.
+
+## Using REST When Python Clients Are Missing
+
+If a notebook needs a service without a Python client, use `requests` and the OpenAPI docs:
+
+```python
+import requests
+from nisystemlink.clients.core import HttpConfigurationManager
+
+config = HttpConfigurationManager.get_configuration()
+base_url = config.server_uri.rstrip("/")
+api_keys = getattr(config, "api_keys", {})
+api_key = api_keys.get("x-ni-api-key") if isinstance(api_keys, dict) else None
+if not api_key:
+    raise RuntimeError("Configure an x-ni-api-key before using REST fallbacks.")
+headers = {"x-ni-api-key": api_key}
+
+# Example: Add a comment to a work item (Comments service not available in Python)
+comment_payload = {
+    "resourceId": work_item_id,
+    "resourceType": "WorkItem",
+    "content": "Automated note from notebook"
+}
+
+resp = requests.post(
+    f"{base_url}/nicomments/v1/comments",
+    json=comment_payload,
+    headers=headers
+)
+resp.raise_for_status()
+comment = resp.json()
+```
+
+Common missing services you might need:
+
+- **Comments** — `/nicomments/v1/comments`
+- **Routines v1/v2** — `/niroutine/v1/routines` or `/niroutine/v2/routines`
+- **User** — `/niuser/v1/users` or `/niuser/v1/users/query`
+- **Systems State** — `/nisystemsstate/v1/states`
+- **Tag Historian** — check the service-specific OpenAPI docs instead of assuming `/niapis/...`
+
+Always check the OpenAPI docs to confirm the correct endpoint path and request schema before implementing REST calls.