librc

Control Copilot-LD service lifecycle via the svscan supervision daemon.

1|1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/copilot-ld/copilot-ld --skill librc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: librc
Source: https://github.com/copilot-ld/copilot-ld/tree/main/packages/librc
Command: npx skills add https://github.com/copilot-ld/copilot-ld --skill librc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

librc provides a reliable way to manage the Copilot-LD service lifecycle by coordinating with the svscan supervision daemon to start, stop, and monitor platform services.

Core Features & Use Cases

  • Unified lifecycle: Start, stop, and query status for multiple services in the correct boot/shutdown order.
  • Oneshot and long-running support: Runs immediate setup steps as oneshot tasks and supervises long-running services via svscan.
  • Orchestration with reliability: Ensures services are created in supervision, handles dependencies, and gracefully shuts down in reverse order.

Quick Start

Instantiate ServiceManager and start all configured services to bring up the Copilot-LD platform.

Frequently Asked Questions about librc

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

FAQPage Schema
How do I manage service lifecycle and orchestrate boot order with svscan?

Service lifecycle management with svscan coordinates starting, stopping, and monitoring multiple services in the correct boot and shutdown order. It ensures services are created in supervision, handles dependencies, and gracefully shuts down in reverse order.

What's the best way to run oneshot setup tasks alongside long-running supervised services?

Running oneshot setup tasks alongside long-running services requires a supervision daemon that supports both execution modes. The librc framework runs immediate setup steps as oneshot tasks and supervises long-running services via svscan.

How does Unix socket communication work for querying service status in a supervision stack?

Unix socket communication for querying service status enables automated control of supervised services. The libsupervision stack uses Unix sockets to allow ServiceManager instances to query status and orchestrate service order reliably.

Do I need Node.js modules to integrate with the libsupervision stack for service management?

Integrating with the libsupervision stack for service management specifies Node.js modules as a requirement. You need these modules to instantiate ServiceManager and start all configured services to bring up the platform.

Can I automate starting and stopping platform services in the correct dependency order?

Automating starting and stopping platform services in the correct dependency order ensures services are created in supervision and gracefully shut down in reverse order. This orchestration with reliability prevents dependency failures during boot and shutdown.

Why does librc coordinate with svscan instead of managing services directly?

Coordinating with svscan instead of managing services directly provides a reliable way to manage the service lifecycle by leveraging the svscan supervision daemon to monitor and orchestrate platform services continuously.