dbs-report is a Chinese-language agent skill that works on the saved states left by the dbs-save skill. It reads every save file for a project, sorts them by time, and writes one new Markdown report in a fixed six-part layout.
The report lists how the user’s main complaint changed over time, the conclusions reached, the directions rejected, the open questions, the confirmed next step, and an index of the source files. Each line traces back to a field in a save file; nothing is summarized from memory.
What You Get
- A Markdown report named with a timestamp and the project name, never overwriting an earlier one
- A timeline of the user’s main complaint with the skill that produced each save
- Conclusions merged and de-duplicated, newest first, with corrected ones marked
- Rejected directions with the reasons, open questions, and the confirmed next step
- An index table of every source file with date, title, status and path
- A short receipt giving the file path, the number of saves merged and the date span
Common Use Cases
- Sending a business partner a single document that sums up weeks of diagnosis sessions
- Reviewing three weeks later how the problem framing changed
- Reconciling the saved results with an outside advisor’s notes
What Makes It Unique
Every statement in the report comes from a field in a save file, and the only section where it may summarize is the evolution of the complaint, where it describes the path only. Conflicting conclusions are both kept, with the newer first and the older marked as corrected. Sensitive details the user saved are carried over unchanged, since masking belongs to the save step. It produces Markdown only.
Under The Hood
It is a prose-only skill with no scripts of its own. The agent reads the SKILL.md and a shared archive-contract reference. It reads the project’s save files from the archive folder (by default under the home directory, or the folder set in a small config file in the working directory), runs a shell command to create the reports folder if missing, and writes a new report file each run. The shared contract also names a short Python command for timestamps. It does not call web services, and it only reads the config, never changes it.