os-operations

Inspect, manage, and remediate Bloom OS services, containers, and bootc updates.

10|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/alexradunet/piBloom --skill os-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-operations
Source: https://github.com/alexradunet/piBloom/tree/main/skills/os-operations
Command: npx skills add https://github.com/alexradunet/piBloom --skill os-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a streamlined way to inspect, manage, and remediate issues within the Bloom OS system, ensuring its stability and optimal performance.

Core Features & Use Cases

  • System Health Monitoring: Get a comprehensive snapshot of the OS, services, and containers.
  • OS Image Management: Check, download, apply, and roll back OS image updates using bootc.
  • Service and Container Control: Manage Bloom-specific services and containers, including viewing logs.
  • Declarative State Management: Use manifest tools to ensure services are in the desired state.
  • Use Case: If Bloom services are reported as inactive, use this skill to check system health, inspect container logs, and restart the affected services.

Quick Start

Use the os-operations skill to check the status of all bloom services.

Frequently Asked Questions about os-operations

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

FAQPage Schema
How do I check the health of my Bloom OS system and services?

You can check Bloom OS system health by generating a comprehensive snapshot that inspects the operating system, active services, and running containers. This snapshot identifies inactive services so you can take corrective remediation actions.

How do I manage OS image updates with bootc in Bloom OS?

You can manage bootc image updates by checking for new versions, downloading them, applying the updates to the system, and rolling back if necessary. This process ensures the Bloom OS maintains its desired version and operational stability.

Why are my Bloom OS containers inactive and how do I restart them?

Inactive containers often stem from service failures or misconfigurations. You can inspect container logs to diagnose the root cause and then restart the affected Bloom services to restore the desired operational state.

Can I manage user-scoped Quadlet units for containers in Bloom OS?

Yes, you can control user-scoped Quadlet units within Bloom OS. This allows you to manage container services declaratively, ensuring they remain in their desired state without requiring root-level system permissions.

What is the best way to ensure systemd timers are in their desired state?

The best way to ensure systemd timers are in their desired state is by using manifest tools for declarative state management. This approach verifies the operational status and automatically remediates any deviations from the declared configuration.