dbs-save turns what a diagnosis chat produced into a structured markdown archive on your machine: the original complaint, conclusions, directions you rejected, hypotheses to verify, the next step you confirmed and notes. It refuses to write an empty file when nothing has been concluded yet.
It also lists existing archives for a project and shows or changes the archive location: the default home folder, a folder inside the current project, or a custom path such as a synced folder. Changing the location always shows the final path first and waits for your confirmation.
What You Get
- A new markdown archive per save, never overwriting an earlier one
- A list view of all archives in a project with time, title, state and source skill
- A location command that shows or sets the archive root (default, project or custom folder)
- A reminder that archives are unencrypted text files and may need a gitignore entry
Common Use Cases
- Keeping the outcome of a long business diagnosis before closing the chat
- Recording which options you ruled out so they are not suggested again next week
- Moving archives into a synced folder so several machines can read them
What Makes It Unique
The archive format, naming and location rules live in one contract file shared with dbs-restore and dbs-report, so the three skills always agree. It writes only after something was concluded, it never edits .gitignore or moves old archives without asking, and it is the only skill in the set allowed to write the location configuration.
Under The Hood
The skill is prose instructions plus one shared reference file. It creates folders and writes markdown archives to the local disk, and when you change the location it writes a small configuration file in the current project after you confirm. It reads the clock to build file names and may run a short command to get a time stamp. It makes no network calls and has no scripts of its own. Archives are unencrypted text files, so sensitive figures stay readable by anyone with access to the folder.