把当前诊断的关键状态存到本地，下次回来可以接着用。 触发方式：/dbs-save、/存档、「保存这次诊断」「记下来」「这个结论留着」 Save the current diagnosis state to disk for cross-session recall. Trigger: /dbs-save, "save this diagnosis", "remember this"
The `dbs-save` skill is a state-saving tool designed to record the key outcomes of diagnostic sessions for later retrieval. It solves the problem of losing progress across multiple interactions by saving conclusions, rejected directions, and recommended next steps into a structured, persistent format. Unlike diagnostic skills that generate insights, `dbs-save` focuses solely on capturing and storing this information locally, ensuring continuity in ongoing projects without repeating prior work.
The skill's main features include automatic extraction of titles from user dialogue, organization of files by project (slug) directories, timestamped file naming, and structured storage using YAML frontmatter combined with markdown body. It allows users to explicitly specify titles and projects, list existing saved sessions, and automatically generates readable paths for cross-session recall. The stored files document user questions, derived conclusions, negated directions, hypotheses to verify, recommended next steps, and additional notes, making it a comprehensive state snapshot. The system also includes safeguards against saving empty sessions and handles filename conflicts with timestamp and random suffixes.
`dbs-save` is intended for users engaging in multiple diagnostic interactions who need continuity between sessions, such as consultants, analysts, or business strategists tracking iterative problem-solving. Its use cases include capturing partial or complete diagnostic results for ongoing projects, creating a historical log of user decisions, and enabling future skills like `dbs-restore` to resume work seamlessly. The skill targets professionals who require reliable session persistence and structured documentation of evolving insights without manual effort.
You can save the session using `/dbs-save` to automatically extract a title or `/dbs-save <title>` to specify one. Alternative trigger phrases like '保存这次诊断' or '记下来' also work.
Yes. Each session belongs to a project, internally called a slug. You can specify a project with the `--slug` parameter, e.g., `/dbs-save --slug my-project <title>`. If unspecified, it defaults to the current directory name or 'default'.
It captures the user’s initial question, conclusions reached, rejected directions, hypotheses to validate, recommended next steps, and optional notes. It does not perform diagnosis itself.
Use `/dbs-save list` to see sessions in the current project or `/dbs-save list <project>` to view sessions for a specific project. The output shows timestamp, title, status, and source skill.
It requires the dbskill environment to be installed. Sessions cannot be empty; attempting to save without prior diagnostic content will prompt the user to run a diagnostic skill first. All files are stored locally in plain text, so sensitive information should be handled accordingly.
Quick Setup:
.claude/skills/Repository
dontbesilent2025/dbskill