companion

Manage companion fleet lifecycle via SSH or locally with orchestrator.py.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill companion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: companion
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/companion
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill companion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the lifecycle management of a background companion fleet to ensure continuous monitoring and health checks without manual intervention.

Core Features & Use Cases

  • Start/stop/status/now across the workhorse via SSH or locally.
  • Daemon orchestration with a registry-driven workflow for consistent deployments.
  • Health findings are aggregated and surfaced for quick debugging.

Quick Start

Start the companion daemon and issue lifecycle commands against the workhorse or local instance.

Frequently Asked Questions about companion

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

FAQPage Schema
How do I automate lifecycle management for a background daemon fleet?

Automate background daemon fleet lifecycle management by running a registry-driven orchestrator script to start, stop, and query status. The companion fleet operates continuously, executing health checks and one-shot runs over SSH or locally without manual intervention.

How do I start and stop background daemons on a workhorse via SSH?

Start and stop background daemons on a workhorse via SSH by executing lifecycle commands through an orchestrator script. The script uses a YAML registry to ensure consistent deployments and control daemon operations across local or remote instances.

What is a registry-driven workflow for daemon orchestration?

A registry-driven workflow for daemon orchestration uses a YAML configuration file to define and manage deployments. It provides consistent execution of start, stop, and status commands across a companion fleet, ensuring reliable health monitoring without manual configuration.

Can I trigger one-shot runs locally for development using a fleet orchestrator?

Yes, you can trigger one-shot runs locally for development using the fleet orchestrator. The orchestrator supports both local execution and remote SSH control, allowing you to test daemon processes and health checks during development.

How are health monitoring findings aggregated for quick debugging?

Health monitoring findings are aggregated by the orchestrator and output to Supabase. This surfaces fleet health data continuously, providing quick debugging insights and ensuring continuous monitoring without manual log inspection.

Do I need SSH access to query the status of an always-on companion fleet?

No, you do not need SSH access to query the status of an always-on companion fleet. The orchestrator executes status queries locally for development or remotely over SSH for workhorse instances, providing flexible health monitoring.