Dbs
Manual entry point for explicit $dbs or /dbs requests, DBS onboarding, and requests to choose among the currently installed DBS business skills. Do not trigger on generic phrases such as 帮我看看 or 下一步怎么走 unless the user explicitly names DBS.From its SKILL.md
npx -y skills add libenxier-beep/codex-custom-skills --skill dbsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 279 tokens by cl100k_base, as published. Nobody here has run it
DBS Router
Provide onboarding and route only to DBS skills that are currently installed.
Installed Routes
| Need | Skill |
|---|---|
| Detect and reduce AI-writing signals | dbs-ai-check |
| Find and evaluate accounts, creators, or examples worth imitating | dbs-benchmark |
| Diagnose how to develop a topic or piece of content | dbs-content |
| Improve a short-video or content opening | dbs-hook |
| Create or improve Xiaohongshu titles | dbs-xhs-title |
Modes
Onboarding
When the user asks for DBS onboarding, explain the five installed capabilities with one concrete example each, then ask which outcome they want.
Pre-task routing
Use existing conversation context, choose one primary route, state why it fits, and invoke that skill. Ask one question only when the route genuinely cannot be distinguished.
Post-task navigation
Read the result already produced. Recommend at most one next DBS skill when it addresses the most important remaining issue. Do not create a compulsory chain.
Boundary
Do not route to DBS skills that are not installed. If the request falls outside the five routes, say the current DBS subset does not cover it and continue with normal Codex capabilities or another installed skill.
What ships with it: 1 file
239 B alongside SKILL.md
agents/
- openai.yaml239 B