skillbox-operator

Coordinate box runtime governance to manage the Skillbox graph and onboard projects.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/build000r/skillbox --skill skillbox-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillbox-operator
Source: https://github.com/build000r/skillbox/tree/main/skills/skillbox-operator
Command: npx skills add https://github.com/build000r/skillbox --skill skillbox-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the skillbox runtime graph from inside the box. Onboard projects via blueprints, orchestrate services, diagnose and heal runtime issues, and maintain box health through manage.py. Activate when the user asks about box state, wants to set up a project, needs service management, or when something in the environment is broken.

Core Features & Use Cases

  • Onboard projects via blueprints and scaffold client environments.
  • Orchestrate services across the runtime graph and ensure healthy state.
  • Diagnose, heal, and maintain box health with manage.py for recovery and consistency.
  • Activate when user asks about box state, wants to set up a project, needs service management, or when environment is broken.

Quick Start

Begin by assessing the box state with status and doctor, then scope changes, run a dry-run, and apply verified actions with up, ensuring health and configuration accuracy.

Frequently Asked Questions about skillbox-operator

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

FAQPage Schema
How do I onboard a new project into a runtime graph using blueprints?

To onboard a project into a runtime graph, you apply idempotent bootstrap workflows using blueprints to scaffold client environments. This ensures configuration accuracy and initializes the project safely within the existing service orchestration structure.

What is the best way to diagnose runtime drift and heal misconfigurations across services?

Diagnosing runtime drift and healing misconfigurations is handled by running status and doctor checks. These commands identify environment inconsistencies, allowing you to apply scoped mutations with client and service filters to repair box health.

Can I dry-run service orchestration changes before applying them to the runtime?

Yes, you can dry-run service orchestration changes before applying them. The execution pattern requires assessing box state, scoping desired changes, executing a dry-run, and finally applying verified actions to ensure safe runtime management.

How do I initialize a client environment and manage services safely?

You initialize client environments and manage services by applying safe execution patterns. This involves using scoped mutations with client and service filters, alongside idempotent bootstrap workflows, to guarantee consistent and verified runtime state.

Why do I need an operator to maintain box health and orchestrate services?

You need an operator to maintain box health because it coordinates runtime governance, diagnoses drift, and heals misconfigurations. It applies verified actions across the service graph, ensuring consistent environment recovery and project consistency.

What are the limitations when applying scoped mutations to a runtime graph?

When applying scoped mutations to a runtime graph, you are limited to using client and service filters to target changes. You must follow safe execution patterns like dry-runs and verification to prevent breaking the box environment during recovery.