DontBeSilent Business Diagnosis Toolkit

Problem: Diagnosis work is fragmented across steps

Business operations questions often span model, content, spread, and decision-making. When rewriting titles, benchmarking competitors, or drafting reports, the earlier diagnosis can be lost. dbskill Business Diagnosis Toolkit combines dontbesilent modules into one entry: a single package includes linked commands such as /dbs, /dbs-diagnosis, /dbs-benchmark, /dbs-content, and /dbs-report. For vague requests like “show me where I’m stuck” or “what should I do next”, it routes through the main entry first, then reads the relevant modules/*.md file before executing, so the workflow does not depend on manual stitching.

How it works: route first, then follow module rules

Core rule: identify the command, read the module, and output according to its templates and constraints.
- Clear command: /dbs-xhs-title enters the Xiaohongshu title formula module; /dbs-benchmark enters benchmark analysis.
- Vague request: “how should I handle this content?” routes to /dbs first.
- State continuity: /dbs-save stores diagnosis state, /dbs-restore recovers context, and /dbs-report summarizes the result.

The modules cover business model diagnosis, content creation, short-video hooks, WeChat public account HTML, spread psychology, resonance diagnosis, goal clarity, and decision systems. Execution requires reading the module source first, then following its identity, process, constraints, and output format; templates, scaffolds, and tools are resolved from the module resource directory.

Scope and cautions

It fits diagnosis chains from business questions to content, decisions, and reporting, especially when earlier judgments need to remain visible in one session. The provided materials describe this SkillHub version as a lightweight retained version; a fuller resource pack is available through the GitHub / Claude Code plugin marketplace. When templates, scripts, or deeper resources are involved, verify that the module assets are included in the package. It is not free-form generation: without a clear command it routes to /dbs; with a clear command it enters the corresponding module and follows the defined workflow.