operational-resilience

Enforce idempotent operational practices with absolute paths and JSON outputs.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/KAFKA2306/yt3 --skill operational-resilience
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: operational-resilience
Source: https://github.com/KAFKA2306/yt3/tree/main/.agent/skills/operational-resilience
Command: npx skills add https://github.com/KAFKA2306/yt3 --skill operational-resilience

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operational Resilience provides clear, enforceable infrastructure standards to prevent silent failures and make incidents immediately diagnosable, reducing time-to-resolution during production issues.

Core Features & Use Cases

  • LLM orchestration guidance: recommend Gemini Flash for multi-source processing, enforce JSON structured outputs, and delegate quota/key rotation to a dedicated orchestration service.
  • Workflow and checkpoint control: compress context between stages, extract summaries instead of passing full chat history, and require idempotent checkpoints so side-effecting steps can be safely retried.
  • Failure and service unit practices: prefer crash-fast behavior with system-level restarts, require absolute paths, and mandate service unit fields (User, Group, WorkingDirectory) and pre-flight permission checks.
  • Use Case: Evaluate a YT3 publish pipeline to ensure it produces Final Deliverable Metadata, uses idempotent checkpoints, and yields structured JSON outputs for publish validation.

Quick Start

Audit a deployment or LLM orchestration design for YT3 and produce a checklist verifying absolute paths, idempotent checkpoints, compressed context handoffs, JSON structured outputs, and final deliverable metadata.

Frequently Asked Questions about operational-resilience

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

FAQPage Schema
How do I make infrastructure failures diagnosable during incident response?

Making failures diagnosable requires enforcing observable operational practices like absolute paths, JSON response outputs, and explicit publish metadata. This visibility prevents silent failures and significantly reduces time-to-resolution during production incidents.

What is the best way to handle idempotent checkpoints in LLM orchestration workflows?

Handling idempotent checkpoints in LLM orchestration requires extracting summaries between stages instead of passing full chat history. This compressed context handoff ensures side-effecting steps can be safely retried without duplicating operations or exceeding token limits.

How do I configure systemd service units for crash-fast behavior and automatic restarts?

Configuring systemd service units for crash-fast behavior involves system-level restarts and mandating service unit fields like User, Group, and WorkingDirectory. You must also perform pre-flight permission checks to validate configurations before deployment.

Can I use Gemini Flash for multi-source LLM ingestion and structured outputs?

Yes, you can use Gemini Flash for multi-source LLM ingestion by delegating quota and key rotation to a dedicated orchestration service. This architecture enforces JSON structured outputs to standardize data processing and ensure reliable publish validation.

How do I audit a deployment pipeline for operational resilience?

Auditing a deployment pipeline for operational resilience involves producing a checklist that verifies absolute paths, idempotent checkpoints, compressed context handoffs, JSON structured outputs, and final deliverable metadata to guarantee transparent and recoverable service delivery.