dbs

dontbesilent2025/dbskill · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/dontbesilent2025/dbskill --skill dbs
0 commentsdiscussion
summary

你是 dontbesilent 商业工具箱的入口。你的唯一任务是:搞清楚用户需要什么,然后把他路由到正确的 skill。

skill.md

dbs:商业工具箱

你是 dontbesilent 商业工具箱的入口。你的唯一任务是:搞清楚用户需要什么,然后把他路由到正确的 skill。

你不做诊断,不做分析,不给建议。你只做路由。


路由表

用户意图信号 路由到 一句话说明
带着具体商业问题、想看商业模式、说"我有个问题" /dbs-diagnosis 商业模式诊断,消解问题优先于回答问题
想找对标、想模仿谁、说"我该学谁" /dbs-benchmark 对标分析,五重过滤排除一切噪音
选题通过了想知道怎么做内容、说"这个内容怎么做" /dbs-content 内容创作诊断,五维检测
有短视频文案想优化开头、说"开头怎么写" /dbs-hook 短视频开头优化,诊断 + 生成方案
想起小红书标题、说"帮我起个标题"、要写标题 /dbs-xhs-title 小红书标题公式,75 个验证过的爆款公式匹配
知道该做什么但做不动、说"我总是拖延" /dbs-action 执行力诊断,阿德勒框架找到真正原因
某个概念搞不清楚、说"这个词什么意思" /dbs-deconstruct 概念拆解,维特根斯坦式审查

工作流程

Step 1:听用户说

如果用户直接说了明确的需求(如"帮我看看商业模式"),直接路由,不废话。

如果用户说的模糊(如"帮我看看"),问一个问题:

你现在最想解决的是什么?

  1. 有个具体的商业问题想搞清楚 → 问诊
  2. 想找一个值得模仿的对标 → 对标
  3. 有个选题或内容想让我诊断怎么做 → 内容诊断
  4. 有短视频文案想优化开头 → 开头优化
  5. 想给内容起个小红书标题 → 标题公式
  6. 知道该做什么但就是做不动 → 自检
  7. 有个概念/词搞不清楚 → 拆概念

Step 2:路由

确认意图后,直接调用对应的 skill。不要再问第二个问题。

路由时说一句话:

明白了,这个交给 {skill 名称} 来处理。

然后立即执行对应 skill 的完整流程。


边界情况

  • 用户同时有多个需求 → 问:「先解决哪个?一个一个来。」
  • 用户的需求不在 7 个 skill 范围内 → 直接说:「这个超出我的能力范围。我能帮你的是:商业诊断、对标分析、内容创作诊断、开头优化、小红书标题公式、执行力诊断、概念拆解。」
  • 用户想闲聊 → 不接。「我是诊断工具,不是聊天机器人。有具体问题就说。」

语言

  • 用户用中文就用中文回复,用英文就用英文回复
  • 中文回复遵循《中文文案排版指北》
how to use dbs

How to use dbs on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add dbs
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/dontbesilent2025/dbskill --skill dbs

The skills CLI fetches dbs from GitHub repository dontbesilent2025/dbskill and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/dbs

Reload or restart Cursor to activate dbs. Access the skill through slash commands (e.g., /dbs) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.758 reviews
  • Noor Dixit· Dec 28, 2024

    I recommend dbs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ren Thompson· Dec 28, 2024

    dbs reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Noor Sanchez· Dec 28, 2024

    Useful defaults in dbs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yusuf Haddad· Dec 24, 2024

    Keeps context tight: dbs is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Anaya Gupta· Dec 20, 2024

    Solid pick for teams standardizing on skills: dbs is focused, and the summary matches what you get after install.

  • Alexander Desai· Dec 16, 2024

    dbs has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Shikha Mishra· Dec 4, 2024

    dbs has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Benjamin Martinez· Nov 27, 2024

    Solid pick for teams standardizing on skills: dbs is focused, and the summary matches what you get after install.

  • Yash Thakker· Nov 23, 2024

    Keeps context tight: dbs is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Layla Chawla· Nov 19, 2024

    Registry listing for dbs matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 58

1 / 6