dbskill: a Chinese-language AI Skills toolbox for business diagnosis and content work

What dbskill actually solves, and for whom

The README frames the problem as not knowing which tool to reach for. A founder with a pricing complaint, a creator with a topic that will not hold attention, or someone who knows the next action and keeps not taking it, all face the same first question: what should I even ask? dbskill answers that with a single entry point, /dbs, which reads the current conversation and decides whether one Skill is enough or whether several Skills should be arranged together. The stated audience is entrepreneurs and content creators working in Chinese. The repository is explicit that the toolbox is Chinese-first: the README opens with Chinese and links to English, Japanese, Korean and Traditional Chinese translations. The knowledge behind it is described as 4,176 knowledge atoms filtered from 16,152 public tweets, and those atoms are published in the repository rather than kept private. That matters, because it means the Skills are a layer over data you can inspect. If the Skills do not fit your workflow, the underlying atoms are still readable and usable on their own.

The orchestration model: one entry point, at most three Skills per task

/dbs is described as the toolbox's scheduling desk. It looks at the end result you want first, then decides which Skills to use and in what order, using as few as possible: a simple question is answered directly, and one Skill is used if one is enough. The README lists six common arrangements: a single Skill; sequential steps where the next uses the previous result; independent tasks done separately; a judgement first, then a decision whether to proceed; separate analyses that are then compared; and writing followed by a check and revision. When a direction has to be chosen, /dbs lists the options rather than choosing for you, and before starting it explains how it plans to arrange the work and why. If you already know what you want, you can call a Skill directly, for example /dbs-diagnosis for a business question or /dbs-title-cover-intro for a title, cover text and opening.

Installing dbskill with npx skills and running a first diagnosis

The recommended install path covers Claude Code, Doubao, WorkBuddy, Codex and other agents that support Skills. It is a single npx command, run in a terminal:

npx -y skills add dontbesilent2025/dbskill -g --all

The -g flag installs globally and --all installs to every Agent the Skills CLI recognises; to install to one Agent, drop --all and choose when prompted. After it finishes, you return to your agent and type /dbs 新手入门 to start.

Once installed, the first real use is the router with a concrete situation. The README gives this example, which you send as a normal message to the agent:

/dbs 我做少儿编程课，有 40 个付费学员，但续费率很低。我不知道该先检查产品、定价还是客户匹配

Before starting, /dbs explains how it plans to arrange the Skills and why. After that, you add facts, material or revisions in the same conversation without retyping the command, and type /dbs again only when you move to a new goal. If you would rather skip the router, the README lists direct calls such as /dbs-diagnosis, /dbs-content, /dbs-benchmark and /dbs-knowledge in its full Skill list, with sample prompts for /dbs-diagnosis and /dbs-title-cover-intro.

The Claude Code plugin route and what the dbs namespace changes

Claude Code users have a second install path through the plugin marketplace, and it behaves differently enough to be worth separating. Two commands register the marketplace and install the toolbox:

claude plugin marketplace add dontbesilent2025/dbskill
claude plugin install dbs@dontbesilent-skills

The important difference is namespacing: Claude Code prefixes plugin Skills, so the main entry becomes /dbs:dbs and a specific capability becomes /dbs:dbs-diagnosis. If you copy a slash command from the README's direct-call examples while running the plugin install, it will not match the namespaced form. The marketplace also supports installing a single capability, for example claude plugin install dbs-diagnosis@dontbesilent-skills, which is the lighter option when you want one Skill rather than the whole set. Updates go through the agent instead of the shell: you tell the current agent 更新 dbskill, and the README states this syncs the official dbskill without touching the archives, reports and decision records stored in ~/.dbs/.

Where dbskill stops being the right tool

The most concrete limitation is the licence. The README's update note says the repository now reserves all rights: the Skills stay free to install and use, including for your own business and client service, but may not be republished, packaged, sold or used for AI training without permission. The full terms are in LICENSE, and GitHub reports the licence as NOASSERTION. For an engineer evaluating this as a component inside a paid product, packaging or redistributing the Skills needs the author's permission, which is more than a footnote. A second limitation is language. The toolbox is Chinese-first. Translations of the README exist, but the Skills themselves, their prompts and the knowledge atoms are described in Chinese, and the README's own examples are Chinese. If your team does not work in Chinese, the output will not be usable without a translation layer you would have to build. Third, the video extraction Skill has a dependency the README does not resolve. Release v2.18.34 notes that short-video data and transcript extraction were added and that missing credentials trigger purchase and configuration guidance, and v2.18.35 added Xiaohongshu and WeChat Channels data queries with a 15-second wait limit per data request. The README's Skill table says only that /dbs-video-extract needs external service credentials. Treat /dbs-video-extract as the Skill to validate first if it is why you came.

How dbskill differs from Baoyu-skills and other Skills collections

One comparable Skills collection is Baoyu-skills. The difference is in what sits underneath. dbskill publishes its source material: 4,176 structured knowledge atoms in 知识库/原子库/atoms.jsonl, methodology documents organised per Skill in 知识库/Skill知识包, and a public tweet collection in books/ in both Markdown and PDF. That means the Skills are traceable to a corpus you can read, and the README explicitly points at atoms.jsonl for anyone who wants to build their own RAG instead of using the Skills at all. A Skills collection that is only prompts gives you no such fallback. The trade-off runs the other way too: dbskill's scope is narrow by design, covering business diagnosis, content production, decision records and folder knowledge bases, all in Chinese. A general-purpose Skills collection will cover more ground in more languages. If your work is Chinese-language business and content, the narrower and deeper option is the better fit. If it is not, the breadth wins.

Maintenance, upgrade cost and licence implications

The repository is not archived, and the last push was on 2026-11-02, which is recent. The release history shows a fast cadence: v2.18.33, v2.18.34 and v2.18.35 all landed on 2026-09-01. That pace is a real cost as well as a benefit. The update path is a single instruction to the agent, which is cheap, but the version-to-version changes are behavioural: v2.18.33 removed /dbs-skill-cleaner along with its review and quarantine entry points, so anything built on that Skill stopped working at that release. Anyone scripting against specific Skill names should pin what they depend on and read the commit log before updating. On licence, the README's update note says the repository reserves all rights; the full terms are in LICENSE and GitHub reports NOASSERTION. The Skills stay free to install and use, including for your own business and clients, but may not be republished, packaged, sold or used for AI training without permission. This is a description of what the project says, not legal advice; if you plan to ship anything built on these Skills, get your own reading of the LICENSE file.

Editorial conclusion

Adopt dbskill if you work in Chinese on business diagnosis, content production or folder-based knowledge management, and you already run Claude Code, Codex, Doubao or WorkBuddy. Do not adopt it if you need a permissively licensed component for a commercial product: the repository reserves all rights and packaging or redistributing the Skills requires permission. Before installing, check the skills/ directory for the exact Skill names your agent exposes, and confirm whether /dbs-video-extract is something you need, since it needs external service credentials.

Frequently asked questions

Official sources

1. dontbesilent2025/dbskill on GitHub
2. Issues
3. README
4. Releases