signal-state

Store and update SIGNAL protocol state in a .signal_state.md file.

10|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mattbaconz/signal --skill signal-state
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signal-state
Source: https://github.com/mattbaconz/signal/tree/main/gemini-signal/skills/signal-state
Command: npx skills add https://github.com/mattbaconz/signal --skill signal-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The signal-state skill provides a simple, disk-backed mechanism to store and recover the current SIGNAL protocol context, enabling continuity across sessions by persisting state in a single .signal_state.md file at project root.

Core Features & Use Cases

  • Persistent context: reads existing state at startup and writes changes atomically as tasks progress.
  • Lightweight format: uses a compact YAML-frontmatter structure followed by three content blocks (Context, Progress, Next).
  • Use Case: maintain continuation across long-running tasks or after restarts, keeping track of focus and completed milestones.

Quick Start

Create or update the .signal_state.md file at the project root to initialize and persist session state across tasks.

Frequently Asked Questions about signal-state

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

FAQPage Schema
How do I persist development context across sessions?▼

To persist development context across sessions, use a disk-backed .signal_state.md file to save and recover the current SIGNAL protocol state atomically at project root.

What is the best way to checkpoint project state to disk?▼

The best way to checkpoint project state to disk is writing a compact YAML-frontmatter file with Context, Progress, and Next blocks, overwriting progress on change and pruning completed items.

How does the SIGNAL protocol state file handle completed milestones?▼

The SIGNAL protocol state file handles completed milestones by overwriting progress on change and automatically pruning completed items when the tracked history exceeds ten entries.

Can I store executable code inside the persistent state file?▼

No, you cannot store executable code inside the persistent state file. The mechanism strictly enforces atomic updates of context data and never stores executable code.

When should I trigger a context refresh for persistent state?▼

You should trigger a context refresh for persistent state at session start, during sub-task completion, after a PR merge, or when focus shifts by using the /signal-state command.

Does the persistent state format require external dependencies?▼

No, the persistent state format requires no external dependencies. It uses a lightweight YAML-frontmatter structure to manage disk-backed context directly at the project root.