dbs: A Dual-Mode Business Toolkit Entry for Agents

Where this fits

A user opens your agent and types “help me with my business,” or asks “what’s next” right after a diagnostic report. Your agent has several business skills but no reliable way to pick one. dbs solves that: it is a single entry point that checks conversation context, routes the task to the correct dbs-* skill before work begins, and reads the previous skill output to suggest next steps after work finishes.

Why agents benefit

• Context-aware mode selection: dbs checks whether any dbs-* skill output already exists in the conversation. If yes, it enters post-task navigation; if no, it routes upfront. No extra user configuration needed.
• Intent-to-skill routing table: The README maps phrases such as “compare with competitors” to /dbs-benchmark and “why did this go viral” to /dbs-spread, so the agent can choose skills from signals instead of guessing.
• Post-task reasoning with bounds: After a diagnosis, dbs returns 2–3 recommended next actions with reasons, not a new analysis. This keeps follow-up grounded in the previous output.
• Discipline by design: dbs explicitly says “you do not diagnose, you only route.” That constraint prevents the agent from drifting into unrequested business advice.
• Low memory load for users: Users only need to remember one trigger (/dbs or “what's next”) to reorient the agent.

Practical scenarios

A vague business request

User says “I have a problem with my business model.” The agent runs /dbs, finds no dbs-* output, enters mode A, and routes to /dbs-diagnosis instead of jumping to generic advice.

A viral content question

User shares a post and asks “why did this get so much engagement?” dbs routes to /dbs-spread, which decodes resonance mechanisms using communication theory and points to a chatroom for further discussion.

A post-diagnosis follow-up

The agent just completed a business model diagnosis. User asks “what should I do now?” dbs detects the report in the conversation, enters mode B, and gives two or three concrete next actions with reasoning based on the report conclusions.

Add it to your agent workflow

Install with:

npx skills add Pluviobyte/rnskill --skill dbs

Then use the trigger in a conversation:

User: /dbs
Agent: No previous dbs-* output detected. Entering pre-task routing. Are you looking for diagnosis, benchmarking, content help, or something else?

After any dbs-* skill finishes, the same /dbs trigger switches to navigation mode automatically.

Compare before adopting

Look at routing quality: does dbs distinguish between similar intents (e.g., content creation vs. content resonance) better than a simple keyword router? Check maintenance freshness: the routing table needs updates when new dbs-* skills are added. Compare against alternatives like a custom system prompt with function calling or a generic router skill. Also consider workflow fit: dbs is most valuable if you use several dbs-* skills; for a single business skill, it may be redundant.

Why it is worth tracking

With 1,421 stars and an active author, dbs is a practical example of a small, opinionated orchestration skill. It is worth tracking because routing and post-task navigation are common agent weaknesses, and this skill solves both in one package. If your agent accumulates more business tools, evaluate dbs when orchestration becomes the bottleneck. You can inspect its listing on OpenAgentSkill for additional details: https://www.openagentskill.com/skills/pluviobyte-dbs