Skip to content
SkillModel-led2,199 tokens in use

dbs-save

Saves the conclusions, rejected directions and confirmed next step of a diagnosis chat to a local markdown file, and lets you choose where archives live.

11,518 stars on the repository Custom / Unknowndontbesilent2025/dbskill · skills/dbs-save
npx -y skills add dontbesilent2025/dbskill -g --all
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing dbs-save costs

51tokens idle
2,199tokens in use
4,070tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure22/25
  • Examples12/15
  • Output0/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community64
  • Maturity28
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers