qol-plugin-pointz

Manages PointZ desktop daemon lifecycle, UDP discovery, TCP transport, status API, and cross-platform input injection for qol-tray plugin development and debugging.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/qol-tools/qol-skills --skill qol-plugin-pointz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qol-plugin-pointz
Source: https://github.com/qol-tools/qol-skills/tree/main/plugins/qol-plugin-pointz/skills/qol-plugin-pointz
Command: npx skills add https://github.com/qol-tools/qol-skills --skill qol-plugin-pointz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual management of the PointZ desktop daemon and the mobile remote-control protocol across platforms is error-prone and tedious; this skill documents and standardizes the contract, lifecycle, and integration points for qol-tray.

Core Features & Use Cases

  • Daemon lifecycle management for the PointZ server: startup, socket handling via /tmp/qol-pointz.sock, and cross-platform input injection scaffolding.
  • UDP discovery, TCP command transport, and a local status API to coordinate mobile remote-control with the desktop app.
  • Clear architecture and dev/build guidance including platform-specific input handling, ports, and shared data models for commands.

Quick Start

Start the pointzerver daemon and verify the UDP discovery and status endpoints on your machine.

Frequently Asked Questions about qol-plugin-pointz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a cross-platform desktop daemon lifecycle for mobile remote control?

Cross-platform desktop daemon lifecycle management is handled by starting the PointZ server, configuring the socket path, and using status HTTP API endpoints to verify mobile remote-control connectivity.

How does UDP discovery work for mobile remote control applications?

UDP discovery broadcasts network availability to mobile clients, allowing them to automatically locate the desktop daemon and establish TCP command transport for remote-control input injection.

Does the desktop daemon support cross-platform input injection on Linux, macOS, and Windows?

Cross-platform input injection is supported across Linux, macOS, and Windows, with platform-specific handling scaffolded to ensure remote-control commands execute correctly on each operating system.

What is the best way to debug TCP command transport for a desktop daemon?

Debugging TCP command transport involves checking the daemon lifecycle status via the local HTTP API, verifying the socket connection at the specified path, and validating command data models.

Why does the mobile remote control daemon fail to connect on different operating systems?

Connection failures often stem from disabled daemon flags, incorrect socket path configuration, or platform-specific input injection issues, which the enforced plugin contract helps identify and prevent.

Can I use the status HTTP API to monitor the PointZ daemon lifecycle?

Yes, the local status HTTP API monitors the PointZ daemon lifecycle, providing endpoint verification for startup, UDP discovery, and active TCP command transport sessions during plugin development.