← Back to Skills Marketplace
🔌

FTTR Operator Copilot

by FTTR-AI · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ Security Clean
46
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install fttr-operator-copilot
Description
Connect OpenClaw to the FTTR Copilot operator cloud-control APIs through ConnectRPC for managed-device lookup, alert operations, regional stats, network diag...
README (SKILL.md)

FTTR Operator Copilot

Use this skill when a user asks OpenClaw to query or operate FTTR Copilot data with an Operator identity.

Runtime

Run the bundled CLI from this skill directory:

node src/cli.js \x3Ctool> [json-arguments]

The CLI always prints JSON. Successful calls use:

{
  "ok": true,
  "title": "...",
  "summary": "...",
  "data": {},
  "suggestions": [],
  "trace": []
}

Available Tools

  • list_devices: List Operator-managed devices with filters such as region, MAC, SN, online status, kind, activation state, and fault code.
  • get_device_detail: Get Operator device detail by device ID, MAC address, or SN.
  • get_device_online_status: Get online status by device ID, MAC address, or SN.
  • list_device_alerts: List Operator-visible alerts, optionally filtered by device, region, event type, event code, cursor, and limit.
  • get_alert_detail: Get one alert detail by alert ID.
  • calculate_alert_number: Count total and unread alerts for one or more devices.
  • mark_alerts_as_read: Mark alert IDs as read. This writes to FTTRAI state.
  • get_network_topology: Get gateway and station topology for a master gateway.
  • get_station_stats: Get station metrics for all stations or one station.
  • get_station_metrics: Alias of get_station_stats for detailed station metrics.
  • get_network_experience: Get network score and experience trends.
  • get_station_experience: Get RSSI history for one station.
  • get_device_stats: Get Operator regional device summary stats.
  • get_device_load: Get device load trends through admin charts. Supported load_type: basic, optic, wireless_rssi, wireless_loads, station_rssi, station_counter.
  • get_fault_counter: Get Operator regional fault stats.
  • get_master_gateway_info: Send an Operator-authorized real-time query command for FMU information.
  • get_slave_gateway_info: Send an Operator-authorized real-time query command for FSU information.
  • get_agent_version: Send an Operator-authorized real-time query command for Agent version.
  • diagnose_device_offline: Combine detail, online status, and Operator-visible alerts for offline diagnosis.
  • diagnose_network_slow: Combine detail, topology, network experience, and station metrics for network-slow diagnosis.
  • explain_fttrai_copilot_usage: Explain available Operator capabilities, required inputs, and example prompts.

Usage Guidance

  • Prefer device ID, MAC address, SN, or region code when asking follow-up questions.
  • Operator tools are scoped by the token user's region and permissions.
  • mark_alerts_as_read writes state; confirm intent before using it.
  • Real-time command tools send device query commands and may return a sequence_id when the device has not returned a result yet.
  • Do not invent FTTR operating procedures. If live FTTRAI data is insufficient, say what is missing and ask for the next identifier or symptom.
  • Keep answers in Chinese unless the user asks otherwise.

Examples

node src/cli.js list_devices '{"region_code":"440000","online_status":"OFFLINE","limit":20}'
node src/cli.js get_device_detail '{"device_identifier":"AA:BB:CC:DD:EE:FF"}'
node src/cli.js list_device_alerts '{"region_code":"440000","event_type":"ALARM","limit":20}'
node src/cli.js get_alert_detail '{"alert_id":"00000000-0000-4000-8000-000000000000"}'
node src/cli.js calculate_alert_number '{"device_identifiers":["AA:BB:CC:DD:EE:FF"]}'
node src/cli.js mark_alerts_as_read '{"alert_ids":["00000000-0000-4000-8000-000000000000"]}'
node src/cli.js get_device_stats '{"region_code":"440000"}'
node src/cli.js get_fault_counter '{"region_code":"440000"}'
node src/cli.js get_device_load '{"device_identifier":"AA:BB:CC:DD:EE:FF","load_type":"basic"}'
node src/cli.js get_network_topology '{"device_identifier":"AA:BB:CC:DD:EE:FF"}'
node src/cli.js get_master_gateway_info '{"device_identifier":"AA:BB:CC:DD:EE:FF"}'
node src/cli.js diagnose_network_slow '{"device_identifier":"AA:BB:CC:DD:EE:FF","symptom":"卧室网慢"}'
Usage Guidance
Before installing, confirm that this agent is allowed to use an FTTRAI operator token and view managed-device/network data. Use a least-privileged token, keep FTTRAI_RPC_URL on a trusted HTTPS endpoint, and require confirmation before marking alerts as read or running real-time device query commands.
Capability Analysis
Type: OpenClaw Skill Name: fttr-operator-copilot Version: 0.1.0 The fttr-operator-copilot skill is a legitimate toolset for managing FTTR (Fiber to the Room) devices via the FTTR Copilot operator cloud APIs. It facilitates device lookups, alert management, network diagnostics, and real-time status queries through a ConnectRPC interface at fms-main.fttrai.com. The implementation is well-structured, includes comprehensive unit tests, and shows no signs of malicious intent, data exfiltration, or unauthorized command execution.
Capability Tags
requires-oauth-tokenrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
The tools match the stated FTTR Operator Copilot purpose: device lookup, alert review, stats, diagnostics, and read-oriented real-time query commands. The capability is sensitive because it exposes operator-visible device and network data.
Instruction Scope
The skill documents its tools and specifically tells the agent to confirm before using the state-changing mark_alerts_as_read tool. The CLI itself is a direct tool runner, so safe use depends on the agent/user honoring that confirmation guidance.
Install Mechanism
There is no install script or dependency install step in the provided artifacts; the skill runs bundled Node.js files directly and package.json declares no external dependencies.
Credentials
Requiring FTTRAI_OPERATOR_AUTH_TOKEN is proportionate for an operator API integration. The optional FTTRAI_RPC_URL should only be set to a trusted HTTPS endpoint because the code allows both http and https.
Persistence & Privilege
No local persistence, background worker, or self-starting behavior is shown. Provider-side state can change when alerts are marked read, and all API access runs under the supplied operator token.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install fttr-operator-copilot
  3. After installation, invoke the skill by name or use /fttr-operator-copilot
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial Operator skill with managed-device, alert, stats, diagnostics, and command tools
Metadata
Slug fttr-operator-copilot
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is FTTR Operator Copilot?

Connect OpenClaw to the FTTR Copilot operator cloud-control APIs through ConnectRPC for managed-device lookup, alert operations, regional stats, network diag... It is an AI Agent Skill for Claude Code / OpenClaw, with 46 downloads so far.

How do I install FTTR Operator Copilot?

Run "/install fttr-operator-copilot" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is FTTR Operator Copilot free?

Yes, FTTR Operator Copilot is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does FTTR Operator Copilot support?

FTTR Operator Copilot is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created FTTR Operator Copilot?

It is built and maintained by FTTR-AI (@fttrai); the current version is v0.1.0.

💬 Comments