skill-reloader

Restore critical workspace files and tools after resets.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/soma-neuron/soma-public --skill skill-reloader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-reloader
Source: https://github.com/soma-neuron/soma-public/tree/main/skills/skill-reloader
Command: npx skills add https://github.com/soma-neuron/soma-public --skill skill-reloader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clawdbot agents lose workspace state after restarts; this skill automatically restores critical files and tools to preserve continuity.

Core Features & Use Cases

  • Detects fresh workspace states and quickly restores from cache or remote
  • Automatically caches essential files to speed up recovery
  • Provides simple workflows to verify and maintain workspace integrity

Quick Start

Activate the Skill Reloader at startup to automatically preserve and restore your workspace state.

Frequently Asked Questions about skill-reloader

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

FAQPage Schema
How do I restore workspace files and configuration after an agent restart?

To restore workspace files after an agent restart, the Skill Reloader detects fresh states and automatically recovers critical tools, memory, and configuration from a local cache or remote GitHub repository.

What is the best way to preserve workspace state across environment resets?

The best way to preserve workspace state across environment resets is by configuring a criticalFiles array that automatically caches essential files locally, ensuring your tools and memory survive unexpected crashes or restarts.

Can I recover workspace continuity from a remote Git repository after a crash?

Yes, you can recover workspace continuity from a remote Git repository after a crash. The Skill Reloader implements optional remote restoration from GitHub to fetch and restore your preserved critical files.

How does hot-reloading workspace memory and tools work after a fresh start?

Hot-reloading workspace memory and tools works by detecting a fresh workspace state at startup, then quickly restoring your preserved critical files and configurations from local cache or remote sources to maintain continuity.

Do I need to manually configure which files to back up for workspace recovery?

Yes, you need to manually configure which files to back up for workspace recovery by defining a criticalFiles array. This configurable preservation rule specifies exactly which tools, memory, and configuration files to cache and restore.