One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill backend-agent-leonardo-corte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-agent
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.maestro/skills/backend-agent
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill backend-agent-leonardo-corte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend-heavy Mission Control workflows can fail mid-run, leaving runtime state inconsistent and recovery incomplete, which forces users to restart or lose progress.

Core Features & Use Cases

  • Runtime-state persistence & validation: Defines and enforces runtime-state types, validators, and storage adapters so retries resume safely.
  • Recovery orchestration & checkpoint semantics: Implements retry/recovery logic with checkpoint safety and stale/session detection to prevent reactivating expired ownership.
  • Cross-CLI domain adapters & resilient persistence: Wires the domain/invariants into src/services.ts, ensuring filesystem-backed audit/event/history persistence degrades safely when runtime data is missing.
  • Use Case: A long-running mission fails during a backend step; this Skill ensures the next CLI invocation can detect stale ownership, restore checkpoint metadata, and requeue the right features while preserving retry history and audit trails.

Quick Start

Use the backend-agent Skill when implementing a Mission Control change that affects recovery, checkpoint restore, or runtime ownership invariants across retries and CLI resumes.

Frequently Asked Questions about backend-agent

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

FAQPage Schema
How do I reliably persist runtime state and orchestrate recovery for a backend CLI?

Recovery orchestration detects stale ownership and restores checkpoint metadata so the next CLI invocation can requeue features while preserving retry history. It applies backward-compatible degradation when runtime data is missing.

What is the best way to handle long-running mission failures without losing progress?

Handling long-running mission failures requires implementing checkpoint safety and stale session detection to prevent data loss. This approach restores runtime state and requeues the right features while preserving audit trails and retry history.

How do I validate runtime state types when implementing retries in Mission Control?

Validating runtime state types requires using the project's existing Zod-based validation patterns. This ensures that storage adapters and retry logic can safely enforce invariants and confirm that runtime data is consistent before resuming.

Can I use filesystem-backed persistence if my runtime data is missing?

Filesystem-backed persistence can be used when runtime data is missing by applying backward-compatible degradation. This approach ensures that audit, event, and history persistence degrade safely without crashing the CLI.

Why does my CLI resume fail when domain logic changes affect runtime ownership?

CLI resumes fail when domain and adapter changes break runtime ownership invariants across retries. Wiring the domain invariants into service files ensures that cross-CLI domain adapters and resilient persistence maintain consistent state.