aradotso/trending-skills/dontbesilent-dbskill

---
name: dontbesilent-dbskill
description: Claude Code skill for dontbesilent's business diagnosis toolkit — routes to diagnosis, benchmark, content, unblock, and deconstruct skills built from 12,307 tweets
triggers:
  -diagnose my business model
  -help me find a benchmark competitor
  -diagnose my content strategy
  -I'm stuck and can't execute
  -deconstruct this concept for me
  -run business diagnosis
  -use dbs skill
  -commercial diagnosis
---
 
# dontbesilent-dbskill
 
> Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection.
 
Business diagnosis toolkit for Claude Code. Distilled from 12,307 tweets into 4,176 structured knowledge atoms across 6 diagnostic skills.
 
---
 
## Installation
 

 
Or manually:
 

 
After installation, use `/dbs` inside Claude Code.
 
---
 
## Skills Overview
 
| Command | Purpose |
|---|---|
| `/dbs` | Main entry point — auto-routes to the right tool |
| `/dbs-diagnosis` | Business model diagnosis. Dissolves problems rather than answering them |
| `/dbs-benchmark` | Benchmark analysis. Five filters to eliminate noise |
| `/dbs-content` | Content creation diagnosis. Five-dimension detection |
| `/dbs-unblock` | Execution diagnosis. Adlerian framework |
| `/dbs-deconstruct` | Concept deconstruction. Wittgensteinian audit |
 
### Workflow
 

 
Skills auto-recommend next steps. For example, if `diagnosis` detects psychological blockers, it suggests `unblock`.
 
---
 
## Usage
 
### Main Router
 

 
The `/dbs` router reads the input and dispatches to the correct skill automatically.
 
---
 
### `/dbs-diagnosis` — Business Model Diagnosis
 
**What it does:** Applies 6 axioms + a dissolution funnel to identify whether you have a real business problem or a false framing problem.
 

 
**Typical output structure:**
1. Axiom scan — which of the 6 axioms are violated
2. Problem dissolution — is this a real problem or a framing error
3. Signal classification — structural vs. psychological vs. execution
4. Recommended next skill
 
**When to use:**
- Revenue is flat but you can't identify why
- You're about to pivot and want a second opinion
- The business "feels wrong" but you can't articulate it
 
---
 
### `/dbs-benchmark` — Benchmark Analysis
 
**What it does:** Finds who to model after using five filters to exclude misleading comparisons.
 

 
**Five filters applied:**
1. Same customer type (not same product)
2. Same distribution channel
3. Same pricing tier
4. Similar company age/stage
5. Accessible operational data
 
**When to use:**
- Deciding on pricing
- Choosing a growth channel
- Evaluating whether your metrics are good or bad
 
---
 
### `/dbs-content` — Content Diagnosis
 
**What it does:** Five-dimension detection for content that isn't working.
 

 
**Five dimensions checked:**
1. Audience-message fit
2. Format vs. platform norms
3. Value signal clarity
4. Call-to-action coherence
5. Consistency and cadence
 
**When to use:**
- Content gets views but no conversions
- You don't know what to post
- Engagement dropped suddenly
 
---
 
### `/dbs-unblock` — Execution Unblock
 
**What it does:** Diagnoses why you're not executing using the Adlerian framework (goal conflict, not willpower failure).
 

 
**Framework applied:**
- Adlerian teleology: behavior serves a hidden goal
- Signal detection: what does avoiding this action protect?
- Reframe: surface the competing commitment
- Micro-action prescription
 
**When to use:**
- You know what to do but aren't doing it
- Procrastination on specific high-value tasks
- Execution works in some areas but breaks down in others
 
---
 
### `/dbs-deconstruct` — Concept Deconstruction
 
**What it does:** Wittgensteinian audit of vague business concepts to find where language is causing confusion.
 

 
**Process:**
1. List all uses of the term in circulation
2. Find family resemblances and contradictions
3. Identify which definition the user is actually operating with
4. Replace with concrete observables
 
**When to use:**
- A concept feels important but you can't act on it
- Team alignment is failing around a shared term
- You're using a term from one domain in another domain
 
---
 
## Knowledge Base (Standalone Use)
 
The knowledge base is fully open. You don't need the Skills installed to use it.
 
### Directory Structure
 

 
### Knowledge Atom Format
 

 
### Field Reference
 
| Field | Values | Notes |
|---|---|---|
| `type` | `principle` / `method` / `case` / `anti-pattern` / `insight` / `tool` | Filter for cases: ~700+ entries |
| `confidence` | `high` / `medium` / `low` | Use `high` for system prompts |
| `topics` | 10 categories (multi-select) | e.g. `"心理与执行力"` has 296 atoms |
| `skills` | One or more skill IDs | Cross-reference to skill docs |
 
---
 
## Using the Knowledge Base Without Installing Skills
 
### Scenario 1: Add business diagnosis to your own AI system prompt
 
Copy the content of `知识库/Skill知识包/diagnosis_公理与诊断框架.md` into your system prompt. Your AI gets the 6-axiom framework + dissolution funnel immediately.
 
### Scenario 2: RAG pipeline
 

 
### Scenario 3: Topic-based filtering
 

 
### Scenario 4: Build a standalone chatbot
 

 
---
 
## Common Patterns
 
### Pattern: Full workflow for a new venture
 

 
### Pattern: Stuck on a single concept
 

 
Use this before any strategy discussion where the key term feels fuzzy.
 
### Pattern: Content not converting
 

 
The more specific the input, the more targeted the five-dimension output.
 
### Pattern: Cross-skill signal handoff
 
Skills auto-detect when a different skill would be more useful:
 
- `diagnosis` → detects avoidance language → recommends `unblock`
- `benchmark` → finds no valid comparables → recommends `diagnosis` (may be category creation)
- `content` → detects unclear positioning → recommends `diagnosis`
- `unblock` → detects concept confusion → recommends `deconstruct`
 
---
 
## Troubleshooting
 
**`/dbs` not found after installation**
 
Check that files were copied to the correct location:

 
Expected output:

 
If missing, re-run the manual install:

 
**Knowledge base files not loading**
 
Skills read knowledge packages from relative paths. If you moved skill files, ensure the `知识库/Skill知识包/` directory is co-located or update path references in the SKILL.md files.
 
**Getting generic responses instead of framework-driven ones**
 
Provide more context. The skills route based on signal words. Instead of:

 
Use:

 
**Atoms.jsonl is large — only need a subset**
 

 
---
 
## License
 
CC BY-NC 4.0. Free for personal use, learning, research, non-commercial projects. Commercial use requires separate authorization. Contact the author at [@dontbesilent](https://x.com/dontbesilent).