save-status

Persist task status files and reconcile session metadata across machines.

28|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/ma08/botfiles --skill save-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-status
Source: https://github.com/ma08/botfiles/tree/main/hermes/skills/save-status
Command: npx skills add https://github.com/ma08/botfiles --skill save-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of lost task context and misaligned metadata when switching between coding agent sessions, remote machines, or task tracking tools, ensuring you can always resume work exactly where you left off.

Core Features & Use Cases

  • Persist Task Progress: Save current task status, plans, and investigation notes to the project's dedicated task-tracking folder.
  • Sync Cross-Tool Metadata: Reconcile machine, zellij session, and task tracker metadata to keep all systems aligned.
  • Use Case: If you're working on a long-running coding task across multiple remote SSH sessions, use this Skill to save your progress and sync it with your task tracker so you can pick up right where you stopped on any machine.

Quick Start

Invoke the save-status skill with your active task slug to persist your current progress and sync it across all your sessions, trackers, and machines.

Frequently Asked Questions about save-status

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

FAQPage Schema
How do I persist task progress when switching between coding agent sessions?

You can persist task progress by invoking the save-status skill with your active task slug to save current status, plans, and investigation notes to a dedicated task-tracking folder, ensuring context survives across coding agent sessions.

What is the best way to sync zellij session metadata with GitHub issues?

The best way to sync zellij session metadata with GitHub issues is using the save-status skill, which reconciles machine, zellij session, and task tracker metadata to keep all external systems aligned without manual intervention.

How does status persistence work for long-running coding workflows across remote machines?

Status persistence works by writing task status files and updating current-task pointers on your project's tracking folder, allowing you to resume long-running coding workflows exactly where you stopped on any remote machine.

Can I use this task-tracking approach without losing context between SSH sessions?

Yes, you can use this approach without losing context between SSH sessions because the save-status skill persists task status files and reconciles machine and session metadata, allowing you to pick up work seamlessly across different remote SSH connections.

Do I need zellij to sync metadata across multiple coding agents?

You do not necessarily need zellij to sync metadata across multiple coding agents, but the save-status skill is specifically designed to integrate zellij for session management and reconcile its metadata with external task trackers.