Loading...
Loading...
The main entry point for the dontbesilent business toolkit. Dual mode: pre-task routing (which skill should handle your question) + post-task navigation (what to do after a diagnosis). Triggers: /dbs, /business, “Help me take a look,” “What should I do next”
npx skill4agent add pluviobyte/rnskill dbs/dbs/dbs| User intent signal | Route to | One-line explanation |
|---|---|---|
| Wants to discuss from multiple perspectives, says “Help me think it through,” “Hear different viewpoints,” or “Let’s have a few people discuss it” | | A focused chat room that recommends experts—or lets you specify them—for a multi-role discussion |
| Has a specific business question, wants to examine a business model, or says “I have a question” | | Business model diagnosis; clarifying the problem takes priority over answering it |
| Wants to find a benchmark, wants someone to imitate, or says “Who should I learn from?” | | Benchmark analysis with five filters to eliminate all noise |
| Has an approved topic and wants to know how to create the content, or says “How should I make this content?” | | Content creation diagnosis with a five-dimensional test |
| Has existing content and wants to know why it went viral, what emotion it hit, which direction to deepen the discussion, or says “Why did this go viral?” or “What do the audience want to hear?” | | Viral psychology decoding: analyze the resonance mechanism through 5 classic communication theories and suggest chat-room directions |
| Has finished a draft but feels uncertain, worries it will not get traffic or resonate with the audience, or says “Is there anything wrong with this draft?” or “Can I publish it?” | | Draft resonance diagnosis that specifically identifies the problem of being “comprehensive but not hitting the core” and provides concrete revision suggestions |
| Has a short-video script and wants to optimize the opening, or says “How should I write the opening?” | | Short-video opening optimization: diagnosis and generated options |
| Wants a Xiaohongshu title, says “Help me write a title,” or wants to write a title | | Xiaohongshu title formulas matched against 75 proven viral formulas |
| Submits copy and asks whether it has an AI-like flavor, or says “Check it” | | AI writing-pattern detection; diagnosis only, no rewriting |
| Feels that they take shortcuts on any critical decision, wants a deeper method, or says “Is there a slower way?” | | Slow Is Fast: identify the parts that are worth doing slowly |
| Knows what to do but cannot act, or says “I always procrastinate” | | Execution diagnosis: use an Adlerian framework to find the real cause |
| Does not understand a concept, or says “What does this term mean?” | | Concept deconstruction through Wittgenstein-style scrutiny |
| Has a vague goal, says “I want to do X but don’t know where to start,” “My goal is to become…,” or “I want to become…,” and needs to turn wish grammar into a verifiable goal | | Goal clarification through a Wittgenstein-style grammatical audit |
| Has a vague problem, wants to articulate it clearly, wants to determine whether an Agent can automate the solution, or says “Can this problem be automated?” or “Help me write a problem brief” | | Good-question generator: turn vague problems into briefs that an Agent can reason over and verify |
| Wants to record major decisions over time, backfill outcomes, review patterns, or says “Help me record this decision” or “Check whether I am repeating an old problem” | | Decision system that persists local projects in |
| Explicitly mentions Claude Code, Codex, Grok, AGENTS.md, CLAUDE.md, skill bridge, workbench migration, or unified multi-platform use, or says “My Agent workbench is a mess” or “Help me unify Claude, Codex, and Grok” | | Agent workbench migration: organize rule files, sources of truth, naming, and a Claude Code / Codex / Grok three-platform bridge |
| Wants to turn a large collection of local drafts, posts, topics, and cases into a recombinable system, or mentions “content structuring system,” “content asset engineering,” “topic map,” “topic assembly,” or “turn old content into reusable assets” | | Content structuring system: audit content scale and boundaries first, then build new projects, duplicate assets, extract content units, and generate topic maps and assembled drafts |
| Wants to preserve the key state from the current diagnosis, or says “Save,” “Write it down,” “Archive it,” or “Keep this conclusion” | | Write the current diagnostic state locally so it can be restored later |
| Wants to continue the previous diagnosis, or says “Last time,” “Previously,” “Continue,” “Resume,” or “Where did the last diagnosis leave off?” | | Retrieve the most recent archive and continue from where you left off |
| Wants a shareable report, or says “Create a report,” “Package it,” “Put it together,” or “Make one for my partners” | | Merge multiple archives into a markdown report |
| Wants to study a topic systematically, wants the AI to write consecutive lessons, or mentions “Next lesson,” “Learning feedback,” “Continue learning,” or “Teach me” | | Interactive learning that generates the next lesson based on user feedback |
What do you want to solve most right now?
- I have a problem I want to discuss from multiple perspectives → Focused chat room
- I have a specific business question I want to understand → Diagnosis
- I want to find a benchmark worth imitating → Benchmark
- I have a topic or content I want diagnosed for execution → Content diagnosis
- I want to turn a large amount of local content into a structured, recombinable system → Content structuring system
- I have a short-video script whose opening I want to optimize → Opening optimization
- I want to create a Xiaohongshu title → Title formulas
- I feel I am taking shortcuts on a critical decision and want a deeper approach → Slow-method diagnosis
- I know what to do but cannot act → Self-check
- I do not understand a concept or term → Concept deconstruction
- I want to check whether my copy has an AI-like flavor → AI detection
- I have a vague goal and want to know whether it can truly drive action → Goal clarification
- I have a vague problem and want to turn it into a brief that an Agent can reason over and verify → Good-question generator
- I want to study a subject systematically and generate the next lesson based on feedback → Interactive learning
- I want to record major decisions over time, backfill outcomes, and review patterns → Decision system
Got it. I’ll hand this to {skill name}.
Thediagnosis is complete. The core conclusion is {X}./dbs-XXXBased on this, there are several directions worth taking:
- {skill-A}: Because {reason A}
- {skill-B}: Because {reason B}
Which one would you like to take first? Or tell me directly what you want to do, and I’ll route you.
/dbs-diagnosis| Conclusion signal | Recommended next step | Why |
|---|---|---|
| A psychological signal was identified, such as knowing what to do but being unable to act, repeatedly changing direction, or substituting preparation for action | | The core blocker is not the business model; it is you |
| No benchmark exists yet, and the work is starting from zero | | Imitation is faster than creation, so first find someone worth imitating |
| The business model direction is basically sound, and the work is moving into content execution | | Stop thinking about direction and get the content right |
| The business model works, and there are ongoing choices that need to be tracked | | A long-term project cannot be tracked through chat logs; it needs local persistence |
| The problem itself was not clearly stated, and its boundaries are vague | | If the problem is unclear, every solution is guesswork |
| The user consistently tries to bypass friction in critical judgments | | The judgment is not wrong; the user is avoiding the stretch they need to take |
| Vague concepts were used, such as market segment, IP, or influence | | If the terms are not clarified, all subsequent analysis is built on a shaky conceptual foundation |
| The “problem” is actually a spinning goal, such as wanting to build an IP or gain influence | | This is not a business problem; the goal’s grammar has not been clearly stated |
| The issue involves pricing mechanisms, entrepreneurship, or the nature of markets | | The underlying issue is Austrian economics; Hayek and Mises offer deeper discussion |
/dbs-benchmark| Conclusion signal | Recommended next step | Why |
|---|---|---|
| A benchmark was found, and the next step is content execution | | Now that you have a benchmark, see how the specific content should be made |
| A benchmark was found, and the effectiveness of the imitation needs long-term tracking | | For determining which judgments actually work after benchmarking, backfilled results are more reliable than memory |
| The user wants to find a benchmark before clarifying the problem | | Clarify the problem first, then decide whom to benchmark |
| The user always tries to skip the granular details of imitation in search of a faster path | | You are not missing a benchmark; you are being impatient |
| The user repeatedly says “This is not suitable for me” | | You may not be choosing the wrong benchmark; you may be avoiding execution |
/dbs-content| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The diagnosis identified a problem with the opening | | Opening optimization generates 10 options |
| A title is needed | | Quickly match against 75 proven formulas |
| There is an obvious AI-like flavor | | Diagnose the AI-like flavor separately for greater clarity |
| The problem was not clearly stated, and there are no breakpoints or performance data | | Clarify the problem brief first |
| There are questions about platform selection and operational details | | Find a benchmark to imitate first and learn platform tactics from real-world practice |
| The content method takes shortcuts and skips necessary accumulation | | You are not just a little short on content technique; you are bypassing friction |
| Undefined concepts are used repeatedly | | If concepts are unclear, the content direction will drift as well |
| The user cannot act and keeps preparing | | This may not be a content problem but an execution problem |
/dbs-content-system| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The structure is complete, and the user wants to diagnose a specific topic next | | The system exists, but individual content still needs a five-dimensional diagnosis |
| A new node may need to be upgraded into a long-term pattern | | Patterns are not discovered through conversation; they require results backfilled over time |
/dbs-decision| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The goal cannot even be clearly articulated | | If the goal’s grammar is wrong, logging it is useless |
| The problem’s boundaries are unclear | | If the problem is unclear, the assumptions in the decision system are left unsupported |
| The user is asking whether a direction is worth pursuing | | The decision system handles tracking; determining whether something is worth doing is a matter for business diagnosis |
| The user wants to find a reference path | | Find a benchmark first, then make the choice |
| The user knows what to do but cannot act | | Knowing but being unable to act is a psychological issue, not a decision issue |
| The user is deconstructing a specific concept | | A decision involving unclear terminology cannot be traced back |
/dbs-deconstruct| Conclusion signal | Recommended next step | Why |
|---|---|---|
| A business-model-level issue was uncovered | | The issue behind the concept may be larger |
| The core economic concept being deconstructed involves price, profit, entrepreneurship, or the market | | Hayek and Mises offer deeper discussion of these concepts |
| The entire sentence is a spinning goal, not merely ambiguous terminology | | The concept is clear, but the sentence is still not a goal |
| The term is clear, but the problem has not been written as a brief that an Agent can reason over | | Now turn the problem into a form that an Agent can reason over |
/dbs-goal| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The goal is clear, but the user cannot act | | The goal is clear; being unable to act is a separate issue |
| The audit uncovered a business-model issue | | The goal is spinning because the business model has not been clarified |
| The goal contains pseudo-concepts | | Clarify the terms first, then return to the goal audit |
| The goal is clear, and the user wants to determine whether an Agent can take over | | The goal is clear; now write the problem as a brief that an Agent can reason over |
| The goal is clear, and choices and outcomes need long-term tracking | | Do not rely on chat memory; use the decision system for continuous tracking |
| Xiaohongshu titles are involved | | Directly apply one of the 75 formulas |
| Short-video openings are involved | | Perform dedicated opening optimization |
| The content creation direction is involved | | Five-dimensional diagnosis ensures that the content direction is correct |
/dbs-good-question| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The question concerns whether a business model is viable | | The question is clear; proceed to business diagnosis |
| A core term in the question is undefined | | If the term is unclear, the problem brief is only apparently clear |
| The question is actually a vague goal | | First audit the goal into something that can be checked |
| The question points to content performance and has clear breakpoints | | The question is clear; move on to content diagnosis |
| The question points to benchmark selection | | The question is clear, so the benchmark now has a direction |
| The question is clear and now needs long-term tracking | | The question is clear; place the choices and outcomes in the decision system |
| The question is clear, but the user cannot act | | The issue is not unclear thinking but inability to act; run a psychological diagnosis |
| The user wants to study a theory systematically | | Systematic learning is more effective than learning through chat |
| The user wants to diverge through multiple roles and then converge | | Discuss from multiple perspectives before converging |
/dbs-action| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The user wants to act but does not know what to do | | Execution is not the problem; next, examine the direction |
| The blocker is the business model itself | | Execution is not the problem; the issue lies in the business model |
| The goal itself is spinning, using wish grammar | | Inaction is not an execution problem; the goal itself has no driving force |
| The user always looks for a faster approach on a critical method | | You are not blocked on taking action; you chose the wrong method |
/dbs-slowisfast| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The user does not know whom to benchmark | | First find a benchmark worth studying in depth |
| The user has content but does not know how to optimize it | | After confirming the content direction, use five-dimensional diagnosis |
| The user knows it should be done slowly but cannot act | | This may not be a method issue but an execution issue |
| The user has doubts about the business model | | Confirm that the direction is correct before discussing speed |
| A vague concept needs to be deconstructed first | | Clarify the concept before determining what is worth doing slowly |
/dbs-hook| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The opening has been optimized, and the user wants to assess the overall content | | The opening is right; is the rest of the content right too? |
| The topic or content itself was found to be the problem | | Opening optimization cannot fix it; the problem lies in the content, so diagnose it again as a whole |
/dbs-xhs-title| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The title is finalized, and the user wants to optimize the opening | | The title is ready; perform dedicated opening optimization |
| The title is finalized, and the user wants a full content diagnosis | | Beyond the title and opening, is the overall content correct as well? |
/dbs-ai-check| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The opening was detected as formulaic | | Perform dedicated opening optimization |
| The copy’s topic itself is problematic | | The AI-like flavor is not the biggest issue; the topic needs a new diagnosis |
/dbs-chatroom-austrian| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The discussion involves a specific business-model issue | | The philosophical discussion is complete; proceed to business diagnosis |
| The discussion involves conceptual boundaries, such as entrepreneurship, doing business, or making money | | Deconstruct the concept more precisely |
| The discussion involves execution or action | | You understand the principle but cannot act; run a self-check |
/dbs-chatroom/dbs-spread/dbs-resonate| Conclusion signal | Recommended next step | Why |
|---|---|---|
| The discussion produced a clear content direction | | The direction is set; now determine how to create the content |
| The spread angle is confirmed and a title is needed | | The direction is set; match the title against 75 formulas |
| The draft was diagnosed as not hitting the core | | Re-diagnose the whole draft or redo the opening |
/dbs-save/dbs-restore/dbs-report| Conclusion signal | Recommended next step | Why |
|---|---|---|
| Archiving is complete, and the project already contains ≥3 archives | | You can now create a merged report |
| The report contains unresolved issues | Corresponding diagnostic skill | Route to the corresponding skill based on the type of unresolved issue |
| The previous archive has been resumed, and the next step is clear | Corresponding skill | Route directly to the archive’s next_skill |