signalproof-restore

Executes bounded restoration from verified rollback targets with identity and behavior verification.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-restore-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-restore
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-restore
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-restore-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Restoring a system to a known-good state often risks overwriting user data, creating mixed-version states, or skipping verification. This Skill enforces a bounded, evidence-backed restoration process that protects persistent data and proves the restore actually worked. ## Core Features & Use Cases - Bounded Restore Execution: Declares exact replace/retain boundaries before actuation, covering application payload, configuration, runtime, services, or full install trees. - Data Protection by Default: Preserves persistent user data and failed-state evidence unless explicitly authorized otherwise. - Post-Restore Verification: Verifies target identity, representative behavior, and protected-data survival after the switch. - Use Case: After a failed deployment corrupts a service, use this Skill to stage the last verified build, restore configuration in dependency order, and confirm both identity and function before declaring recovery complete. ## Quick Start Restore the service to the last verified rollback target while protecting user data and verifying the result.

Frequently Asked Questions about signalproof-restore

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

FAQPage Schema
How do I restore a system to a known-good state safely?▼

Identify a verified recovery target, declare exact replace/retain boundaries, stage the candidate before switching, then verify identity and function after the restore. Persistent user data is protected by default throughout the process.

What is the difference between rollback and restore?▼

Restore executes the bounded act of returning to a selected known-good state. If the recovery target itself is unresolved, the Rollback skill handles target selection first, then Restore performs the verified actuation.

When should a restore operation stop instead of proceeding?▼

Stop when overwrite scope is ambiguous, persistent data would be erased outside authority, target verification fails, writes cannot be safely quiesced, required privilege is unauthorized, or the result would be a mixed-version state.

Does restore overwrite user data during recovery?▼

No. Persistent user data is protected by default, and data restoration is a separate explicit boundary requiring its own authorization in the recovery plan.

How is a restore verified as successful?▼

Verification checks target identity after copy or switch, representative required behavior, and protected-data survival. Completion requires explicit records of boundaries, actions, verifications, failures, and remaining fallback options.