node-ops

Included with Lifetime

$97 forever

Node pairing: approve/reject, nodes run/invoke, screen_record, camera_snap, location, System76 mgmt

Backend & APIsnodespairingsystem76screencamera

What this skill does


# node-ops

## Purpose
This skill handles node operations in a distributed communications setup, focusing on pairing nodes (approve/reject), executing commands, and managing hardware like screen recording, camera snapshots, location tracking, and System76 device management. It's designed for secure, cluster-based interactions in environments like distributed-comms.

## When to Use
Use this skill when setting up or managing node pairs in a cluster, such as approving new nodes for communication, invoking remote commands, or accessing device features. Apply it in scenarios involving IoT devices, remote monitoring, or System76 hardware integration, like fleet management or real-time data capture.

## Key Capabilities
- Approve or reject node pairings via authenticated requests.
- Invoke or run commands on paired nodes, supporting asynchronous execution.
- Record screen sessions or take camera snapshots on target nodes.
- Retrieve location data from nodes, using GPS or network-based methods.
- Manage System76 devices, including firmware updates and hardware diagnostics.
- Handle secure communications within the distributed-comms cluster, with encryption for all operations.

## Usage Patterns
Always authenticate using the `$NODE_OPS_API_KEY` environment variable before operations. Start with pairing nodes, then proceed to commands or hardware access. Use CLI for quick tasks or API for programmatic integration. For example, check node status first, then execute actions. In code, import the skill as a module and call methods with required parameters; in scripts, pipe outputs for chaining commands.

## Common Commands/API
Use the CLI tool `node-ops` or the REST API at `https://api.distributed-comms.com/v1/node-ops`. Authentication requires setting `$NODE_OPS_API_KEY` in your environment.

- CLI for pairing: `node-ops pair approve --node-id 123 --reason "Verified"`. Reject with: `node-ops pair reject --node-id 123 --reason "Unauthorized"`.
- CLI for running commands: `node-ops run --node-id 123 --command "ls -la" --async`. Example output: JSON with command status.
- API endpoint for screen recording: POST /api/screen_record with body: `{"node_id": "123", "duration": 30}`. Response: 200 OK with recording URL.
- API for camera snapshot: GET /api/camera_snap?node_id=123. Requires headers: `Authorization: Bearer $NODE_OPS_API_KEY`.
- Code snippet for invoking a command:
  ```javascript
  const nodeOps = require('node-ops-sdk');
  nodeOps.invoke({ nodeId: '123', command: 'echo Hello' })
    .then(result => console.log(result));
  ```
- Code snippet for location retrieval:
  ```python
  import node_ops
  location = node_ops.get_location(node_id='123')
  print(location)  # Returns dict: {'lat': 37.7749, 'lon': -122.4194}
  ```
- Config format: Use JSON files for node profiles, e.g., `{"node_id": "123", "pair_status": "approved", "api_key": "$NODE_OPS_API_KEY"}`.

## Integration Notes
Integrate by setting `$NODE_OPS_API_KEY` as an environment variable in your application. For cluster interactions, ensure your code references the distributed-comms endpoint. Use SDKs like `node-ops-sdk` for Node.js or Python wrappers. When combining with other skills, handle cross-cluster calls by prefixing with the cluster ID, e.g., `distributed-comms:node-ops run ...`. Avoid hardcoding keys; use secure vaults or env files.

## Error Handling
Common errors include authentication failures (HTTP 401), node not found (404), or command timeouts. Check response codes and handle with try-catch blocks. For CLI, parse errors with `--verbose` flag. Example: If pairing fails, retry after checking `$NODE_OPS_API_KEY`. In code:
  ```javascript
  try {
    await nodeOps.pairApprove({ nodeId: '123' });
  } catch (error) {
    if (error.code === 'AUTH_ERROR') console.error('Invalid API key');
  }
  ```
Log detailed errors using the skill's built-in logging, enabled via `--debug` flag.

## Graph Relationships
This skill relates to: distributed-comms cluster (parent), skills with tags: nodes (peers), pairing (related), system76 (dependent), screen and camera (integrated hardware features). Connections: Uses distributed-comms for node discovery; shares data with system76 management skills.

Files: 1

Size: 4.5 KB

Complexity: 12/100

Category: Backend & APIs

Source: https://github.com/alphaonedev/openclaw-graph/tree/main/skills/distributed-comms/node-ops

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts