star-office-helper

Automate Star Office UI installation, startup, and connection diagnostics for local visualization.

33|6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill star-office-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: star-office-helper
Source: https://github.com/gaogg521/1ONE-ClaudeCode/tree/main/src/process/resources/skills/star-office-helper
Command: npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill star-office-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides an end-to-end workflow to install, start, connect, and troubleshoot Star Office UI for OpenClaw/Aion visualization integrations.

Core Features & Use Cases

  • Install and configure backend/frontend services for Star Office UI
  • Diagnose and repair common issues such as Unauthorized pages, port conflicts, and Python venv/pip problems
  • Reconnect and verify health endpoints to ensure reliable local visualization

Quick Start

Run the built-in doctor and setup scripts to install, start, and verify Star Office UI locally, then confirm the frontend health at http://127.0.0.1:19000.

Frequently Asked Questions about star-office-helper

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

FAQPage Schema
How do I install and start Star Office UI for local OpenClaw visualization?

To install and start Star Office UI, run the built-in doctor and setup scripts to configure backend and frontend services, then verify the local frontend health endpoint at http://127.0.0.1:19000.

Why does the Star Office UI show an Unauthorized page after startup?

An Unauthorized page in Star Office UI indicates a connection or authentication issue during local setup; running the diagnostic doctor script identifies and repairs the underlying health endpoint or configuration problem.

How do I fix Python virtual environment or pip issues when setting up Star Office?

Python virtual environment or pip issues during Star Office setup are resolved by executing the automated diagnostic workflow, which detects environment errors and applies the necessary repair steps to restore functionality.

What is the best way to troubleshoot port conflicts for Star Office UI on localhost?

The best way to troubleshoot Star Office UI port conflicts is using the built-in diagnostics workflow, which verifies local health endpoints, detects port conflicts on 127.0.0.1, and applies automated repairs.

Does Star Office UI require any external dependencies for local visualization?

Star Office UI requires no external dependencies to run locally; it uses built-in scripts to automate the setup, enforce the defined workflow, and enable visualization integrations with OpenClaw or Aion.

Can I run connection diagnostics to verify OpenClaw visualization is working properly?

Yes, you can run connection diagnostics to verify OpenClaw visualization by executing the built-in doctor scripts, which check health endpoints and confirm the frontend is running at http://127.0.0.1:19000.