dbs-save

Saves the current diagnosis state as a per-project markdown file with YAML frontmatter and body.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Mengbooo/BemoSkills --skill dbs-save
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbs-save
Source: https://github.com/Mengbooo/BemoSkills/tree/main/skills/productivity/dbs-save
Command: npx skills add https://github.com/Mengbooo/BemoSkills --skill dbs-save

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool saves the key conclusions, rejected directions, and recommended next steps from a diagnostic dialogue to a local markdown file, enabling cross-session recall. 它把诊断对话中的关键信息(结论、已否定方向、下一步建议)本地化存档,便于下次继续。

Core Features & Use Cases

  • Structured persistence: per-project archives that capture the core findings and decisions.
  • Cross-session continuity: preserves context so you don't restart from scratch in a new session.
  • Extensible format: stores data as YAML frontmatter plus body in a single markdown file, with optional references and assets for richer context.
  • Use Case: Over multiple sessions, you save and restore diagnosis state to refine recommendations without losing earlier work.

Quick Start

Trigger the /dbs-save command to store the current diagnosis state locally.

Frequently Asked Questions about dbs-save

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

FAQPage Schema
How do I save diagnosis state locally for cross-session recall?

To save diagnosis state for cross-session recall, trigger the command to store key conclusions, denied directions, and next steps as a markdown file with YAML frontmatter in a local archive. This ensures context persists across sessions without restarting from scratch.

What is the file path format for archived diagnosis markdown files?

Archived diagnosis markdown files are saved under a deterministic path at ~/.dbs/sessions/{slug}/{timestamp}-{title-slug}.md. Each file uses YAML frontmatter plus a body section, optionally including references or assets for richer context.

Can I use per-project markdown archives across multiple diagnostic sessions?

Yes, per-project markdown archives are designed for multiple diagnostic sessions. They capture core findings and decisions, preserving context so you can restore diagnosis state and refine recommendations without losing earlier work.

What's the best way to persist rejected diagnosis directions and recommended next steps?

The best way to persist rejected directions and next steps is saving them as structured markdown with YAML frontmatter. This format captures key conclusions and decisions deterministically, enabling seamless continuity when resuming diagnostic work later.

Do I need any dependencies to archive diagnosis state as local markdown?

No dependencies are required to archive diagnosis state as local markdown. The tool independently stores the current diagnosis state per-project, writing YAML frontmatter and body content to a deterministic local file path.