dbs-save

Archive diagnostic session states into structured Markdown files.

3|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/XinAloha/skills --skill dbs-save-xinaloha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbs-save
Source: https://github.com/XinAloha/skills/tree/main/business/state-save
Command: npx skills add https://github.com/XinAloha/skills --skill dbs-save-xinaloha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the cold-start problem in diagnostic workflows by allowing you to save the current state of an AI-assisted diagnosis, ensuring that insights, rejected paths, and conclusions persist across different sessions.

Core Features & Use Cases

  • State Persistence: Captures key diagnostic conclusions, rejected directions, and next steps into a structured local Markdown file.
  • Project Isolation: Automatically organizes archives by project slug to prevent data contamination between different business contexts.
  • Use Case: If you are halfway through a complex business diagnosis and need to switch tasks, use this skill to save your progress so you can resume exactly where you left off later without repeating the initial analysis.

Quick Start

Trigger the save process by typing /dbs-save to archive your current diagnostic progress to the local storage directory.

Frequently Asked Questions about dbs-save

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

FAQPage Schema
How do I save AI diagnostic state for cross-session continuity?

To save AI diagnostic state for cross-session continuity, trigger the save command to archive current conclusions, rejected paths, and next steps into a structured local Markdown file for later retrieval.

What is the best way to persist complex diagnostic workflows across different sessions?

Persisting complex diagnostic workflows across sessions requires archiving key hypotheses and analytical conclusions into structured local files, automatically organized by project slug to prevent data contamination between business contexts.

Can I resume a multi-step business diagnosis after switching tasks?

Yes, you can resume a multi-step business diagnosis after switching tasks by loading previously archived session states, ensuring you continue exactly where you left off without repeating initial analysis.

How do I organize archived diagnostic states by project?

Organizing archived diagnostic states by project happens automatically when saving, as the system isolates stored Markdown files using unique project slugs to prevent data contamination between different business contexts.

Does state persistence for diagnostic workflows require external dependencies?

State persistence for diagnostic workflows requires no external dependencies, as it implements local file system operations to ensure data persistence and retrieval for subsequent diagnostic iterations.

What limitations exist when archiving diagnostic session states locally?

Archiving diagnostic session states locally is limited to single-machine file system operations, meaning stored Markdown archives are not automatically synced or shared across different distributed environments or team members.