skills.rest
MGPowerlytics
MGPowerlyticsCOMMUNITY
Explore all skills by this author →
GitHub

extreme-persistence

Execute high-stakes tasks autonomously with multi-path failure recovery and post-mission documentation.

Updated Jan 16, 2026
Search Tags:#persistence#autonomy#error-recovery#distributed-systems#fault-tolerance#post-mission-logging#retry-loop
One-click install
npx skills add https://github.com/MGPowerlytics/nhlstats --skill extreme-persistence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extreme-persistence
Source: https://github.com/MGPowerlytics/nhlstats/tree/main/.github/skills/extreme-persistence
Command: npx skills add https://github.com/MGPowerlytics/nhlstats --skill extreme-persistence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a framework of persistence and autonomous execution to ensure high-stakes tasks complete without user intervention, reducing downtime due to failures and interruptions.

Core Features & Use Cases

  • Zero-Interaction Execution: Operates under the assumption that the user is unavailable and executes tasks to completion.
  • Recursive Troubleshooting: Offers structured multi-path recovery and retry loops to overcome failures without human input.
  • Audit & Handover: Generates post-mission logs, assumptions, and an audit trail for accountability and reproducibility.

Quick Start

To begin, prompt the agent with a high-stakes task and explicitly state that no user input will be available. The agent will absorb context, attempt multiple recovery strategies, persist state across failures, and report completion with a concise handover.

Frequently Asked Questions about extreme-persistence

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

FAQPage Schema
How does recursive troubleshooting handle error recovery in distributed systems without human input?▼

Autonomous error recovery in distributed systems works by applying structured multi-path recovery strategies and recursive retry loops to overcome failures without human input. It persists state across failures and continues execution until the task is complete.

Can I use autonomous execution for maintenance tasks in distributed systems where no user input is available?▼

The best way to autonomously complete maintenance tasks when user input is unavailable is to enforce zero-interaction execution, which attempts multiple recovery strategies and reports completion with a concise handover. This reduces downtime caused by interruptions or failures.

What are the limitations of using zero-interaction execution for fault-tolerance tasks?▼

Post-mission logging for autonomous fault-tolerance tasks works by automatically generating detailed logs, assumptions, and an audit trail upon task completion. This provides thorough documentation for accountability, reproducibility, and handover.

Do I need to provide context before starting an autonomous retry loop for fault-tolerance?▼

You should not use autonomous persistence for distributed systems maintenance when tasks require real-time human judgment or when unstructured, unpredictable failures exceed the predefined multi-path recovery strategies. It is designed for high-stakes tasks where user input is entirely unavailable.

Related Skills

Explore More Software Engineering Skills→
ruifrvazruifrvaz
3

smaqit.task-start

Initiate work on a specified task and set the workflow mode.

Community
Intermediate
serac-labsserac-labs
77

debugging-mutations

Inspect post-action mutations and logs in ServiceNow to verify changes.

Official
Advanced
proofoftomproofoftom

a2a-bridge

Coordinate autonomous agents via A2A protocol with Agent Card discovery and task lifecycles.

Community
Intermediate
lenadlmlenadlm

hermes-cron-recovery

Manually trigger stuck cron jobs and reset Hermes Agent scheduler state.

Community
Intermediate