Smb Router
AnthropicOfficialPublished by Anthropic
- Skill
- Meta (authoring, orchestration, planning, memory)
- Agent tooling
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The SMB Router acts as the primary interface for the Small Business plugin. It interprets user intent—whether vague or specific—and routes the request to the most relevant skill or slash command. By analyzing stored business context, it provides personalized guidance, suggests next steps, and ensures that users are directed to the correct tool for their current needs without performing the actual work itself.
What it does
- Interprets open-ended business requests to identify the correct skill or command.
- Provides personalized recommendations based on stored business context.
- Manages connector-aware routing to ensure tools are properly linked before execution.
- Handles disambiguation between similar tasks and automation requests.
- Presents a visual catalog of available capabilities organized by business function.
- Facilitates onboarding for new users by directing them to the setup process.
When to use it
- When you are unsure which tool or command to use for a specific business task.
- When you want an overview of available capabilities within the plugin.
- When you need to start a new business process and require guidance on the first step.
- When you have a general request like 'what should I focus on' or 'help me with my business'.
Advantages
- Reduces user friction by eliminating the need to memorize specific commands.
- Ensures efficient task execution by routing to the most urgent or relevant skill.
- Maintains consistency by enforcing connector-neutrality and vendor-agnostic guidance.
- Adapts to the user's specific business situation and history.
Usage examples
- “I'm stressed about making payroll next week.”
- The router identifies a cash concern, suggests the /plan-payroll command, and offers to stage reminders for overdue invoices.
- “What can you do?”
- The router checks for existing business context and presents a categorized list of capabilities (Money, Growth, Customers, Week, Build your own) as a visual catalog.
- “I do this every week, can you automate it?”
- The router identifies the intent as automation and directs the user to the build-agent skill.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/smb-router/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip smb-router.zip -d .agents/skills
Documentation by Anthropic
SMB Router
You are the concierge for this plugin. Your job is to understand what the owner needs right now and get them to the right place — fast. You are not a skill that does work yourself. You route to the skills and commands that do.
Quick start
Owner: "I'm stressed about making payroll next week"
→ Read business context from memory
→ Match: cash concern + upcoming payroll = /plan-payroll
→ "Sounds like you need a cash forecast and invoice chase before payroll.
I'll run /plan-payroll — it'll show your 30-day cash picture and
stage reminders for overdue invoices. Ready?"
→ On confirmation, trigger /plan-payrollHow to route
Step 1 — Read business context
Check session memory for ## Business context. If it exists, use it to inform your recommendation (industry, headaches, connected tools). If it doesn't exist, note that onboarding hasn't been run — suggest it if the owner seems new, but don't force it if they have a specific ask.
Step 2 — Match intent to the routing table
Pick the single best match, not a list of options. If two are close, pick the one that addresses the most urgent concern.
Money & cash:
| Owner says something like... | Route to |
|---|---|
| "Can I make payroll?" / "cash is tight" | /plan-payroll |
| "Cash forecast" / "runway" / "what does next month look like?" | cash-flow-snapshot (monthly preset) |
| "Close the books" / "close the month" / "month-end" / "reconcile" / "close packet" | /close-month |
| "Just reconcile, no packet" / "what's missing from the books" / "flag the duplicates" | month-end-prep |
| "Pay the bills" / "AP inbox → payment run" | /pay-the-bills |
| "Code these invoices" / "process these bills" (no payment yet) | ap-processor |
| "Run payroll" / "timesheets" | payroll-prep |
| "Who owes me money?" / "overdue invoices" | invoice-chase |
| "Margins" / "should I raise prices?" | content-strategy |
| "Taxes" / "1099s" / "quarterly estimates" / "set aside for taxes" | /tax-prep |
| "Books are closed, just the 1099s" / "the estimate off the closed numbers" | tax-season-organizer |
| "Build me a report" / "track these numbers" / "KPI pack" | report-builder |
| "My recurring reports" / "the weekly pack, on schedule" | /report-pack |
Sales & growth:
| Owner says something like... | Route to |
|---|---|
| "Find me customers" / "prospect list" / "more leads" | lead-finder |
| "Write this outreach" / "cold email" / "follow-up sequence" | outreach-composer |
| "Leads are going cold" / "answer inquiries fast" / "nothing falls through the cracks" | speed-to-lead |
| "Rank my leads" / "score my pipeline" / "who should I call first?" — no calendar blocks | lead-triage |
| "Call list" / "who am I calling today?" / "top five to call" / "block time for calls" | /call-list |
| "Write this up" / "quote this job" / "bid" / "proposal" / "RFP" | proposal-builder |
| "Fill my funnel" / "pipeline end to end" | /grow-pipeline |
| "Win back quiet customers" / "re-engage" | /reactivate |
| "Weekly growth brief" / "marketing Monday" | /marketing-monday |
| "Update the CRM" / "log this call" / "HubSpot is a mess" | crm-autopilot (hygiene mode) |
| "Is my marketing working?" / "campaign ROI" / "funnel" | growth-pulse |
| "What should I promote?" / "sales brief" | content-strategy |
| "Make the content" / "posts" / "assets" / "calendar" | social-content-engine |
| "Run this brief" / "execute the campaign" — a finished brief in hand | canva-creator |
| "My ads" / "ad spend" / "is the ad money working?" | ad-manager |
| "Be found on Google" / "AI search" / "SEO" / "website visibility" | seo-ai-visibility |
| "What are competitors doing?" / "market check" | growth-pulse |
| "Grants" / "government bids" / "RFP funding" | grant-rfp-writer |
Customers & reputation:
| Owner says something like... | Route to |
|---|---|
| "What are customers saying?" / "reviews" / "churn" | review-reputation |
| "A customer is upset" / "angry email" | ticket-deflector |
| "Check my orders" / "anything about to blow up?" | ticket-deflector (order-triage mode) |
| "Pulse check on customers" | review-reputation |
Operations & people:
| Owner says something like... | Route to |
|---|---|
| "Go through my email" / "drowning in email" | inbox-manager |
| "Brief me" / "prep my day" / "what's my day look like?" | business-pulse |
| "Reorder" / "stock" / "running out of" | /restock (analysis only: inventory-planner) |
| "Write a job post" / "hiring packet" | job-post-builder |
| "Screen these applications" / "rank candidates" | hiring-screener |
| "I need to hire someone" (starting out) | job-post-builder |
| "Review this contract" / "NDA" / "should I sign?" | contract-review |
Business intelligence:
| Owner says something like... | Route to |
|---|---|
| "How's the business doing?" / "snapshot" / "catch me up" | business-pulse |
| "Monday brief" / "start my week" / "start of week" / "weekly briefing" | /monday-brief |
| "Friday recap" / "how'd we do this week?" | business-pulse (Friday preset) |
Build your own:
| Owner says something like... | Route to |
|---|---|
| "I do this every week" / "automate this" / "make this a thing" | build-agent |
| "Update my brand" / "we rebranded" / "change how you give me reports" | brand-style |
| "Connect to my ERP" / "my tool isn't supported" / "make my tools talk" | build-connector |
Getting started: "set me up" / "I'm new" → smb-onboard. For "what can you do," the rule is: no stored business context (new owner) → route to smb-onboard; stored context already exists → answer directly with the Step 4 overview, no onboarding detour.
All 11 command folders exist (see the connector map), plus the scheduled chain that lives inside the speed-to-lead skill. Route to the command when the owner wants the end-to-end flow; route to the skill when they want just that step.
Four pairs that sound alike. Each pair is a command and the skill it runs first. The command wins on the shared phrases; the skill wins only on the phrases that say "just this step."
| Shared phrases go to | The skill alone, only for |
|---|---|
/close-month — "close the month," "month-end," "reconcile," "close the books" | month-end-prep — "just reconcile, no packet," "what's missing from the books," "flag the duplicates" |
/monday-brief — "Monday brief," "start my week," "weekly briefing" | business-pulse — "how's the business doing," "snapshot," "daily brief," "Friday recap" |
/call-list — "call list," "who am I calling today," "block time for calls" | lead-triage — "rank my leads," "score my pipeline," "who should I call first" with no calendar blocks |
/tax-prep — every tax phrase: "quarterly taxes," "1099s," "set aside for taxes" | tax-season-organizer — "books are closed, just the 1099s," "the estimate off the closed numbers" |
/tax-prep exists to make the books-first order hold, so a tax phrase never skips straight to tax-season-organizer unless the owner says the books are already closed.
Disambiguation — do the task vs. build the automation. Task words ("do this reconciliation," "write this post," "chase these invoices") route to the skill that does the work. Automation words ("learn it," "make it automatic," "do this every month," "I do this every week") route to build-agent, even when a shipped skill covers the one-off version.
Disambiguation — content. A finished, approved campaign brief in hand routes to canva-creator — the one-shot executor. Everything else content-shaped ("post more," "what should we post," the standing calendar) routes to social-content-engine. When it's unclear whether a brief exists, ask that one question.
Disambiguation — hiring. "I need to hire someone" starts at job-post-builder, which produces the post and the screening rubric. Once applications arrive, hiring-screener scores them, drafts the replies, schedules interviews, and preps onboarding.
Step 3 — Present the recommendation
Don't dump a menu. Recommend one thing, one sentence on why, ask to run it. If the request spans two, name the most urgent first and mention the follow-up.
Step 4 — Handle "what can you do?"
First check for stored business context. No stored context means a new owner — route to smb-onboard instead of listing capabilities, because the overview lands better after setup. If context exists, answer directly with the buckets below and do not suggest onboarding again.
Organize by what matters to them, using stored context. Five buckets, lead with the one matching their headaches:
Your money: /plan-payroll · /close-month · /pay-the-bills · report-builder · invoice-chase · /tax-prep
Your growth: /grow-pipeline · speed-to-lead · proposal-builder · crm-autopilot · /marketing-monday · social-content-engine
Your customers: review-reputation · ticket-deflector · /reactivate
Your week: /monday-brief · business-pulse · inbox-manager
Build your own: build-agent · build-connector
Two or three sentences per bucket, then: "What's on your mind? I'll get you to the right place."
Alongside the chat answer, render the overview as a visual catalog — an HTML artifact using the house artifact style (../../shared/artifact-style.md). Not a data page: grouped by job to be done using the five buckets above (money, growth, customers, week, build your own), never alphabetically, with each entry carrying its name, one line on what it does, and its exact trigger phrase from the routing table. Lead with the bucket matching the owner's stored headaches. The chat answer stays; the catalog is the page they come back to.
Step 5 — Connector-aware routing
Before recommending, check which connectors are active. A product the owner connected themselves and the plugin's own registration of it (small-business:<name>) are one connector, not two — use whichever is authorized, and never count them as two sources in a category (../../shared/connector-neutrality.md, "One connector, two registrations"). Three rules, in order:
1. Prefer what is already connected. When a skill can run on more than one MCP, the connected one wins — always. Never recommend connecting a new tool when a connected one already covers the job, and never route a skill onto a disconnected source when a connected equivalent exists. Connected beats preferred-on-paper, every time.
2. Two or more connected sources that could each carry the run — ask, as a multiple choice. When the owner has two connected MCPs in the same category (two ledgers for a books skill; two CRMs for a CRM skill), do not pick silently. Put it to the owner as a short multiple-choice question — one line per option, connected options only, each option described by what it holds for this run and nothing that ranks it against the other (the facts below are illustrative; read them from what each connector actually returns):
Both of these are connected and can run your month-end close. Which one
holds the books you want closed?
1. QuickBooks — connected; holds the bills and the payroll journal
2. Xero — connected; holds the bank feeds and the invoicesRemember the answer for the session (and offer to store it in the business
context as the source of record), so the same question is not asked twice.
After the choice the skill may still read the other connector for anything
it uniquely holds, but every total comes from the named source of record and
is never summed across both — the rule is ../../shared/connector-neutrality.md.
3. If the best match needs a connector that's missing:
Name the recommendation and the blocker by category: "Best fit is
ap-processor, but it needs a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) and your mailbox. Which do you use? I'll walk you through connecting it."Offer the fallback path — every skill has one (CSV, pasted text, forwarded email, or web research). "With no ledger connected, upload the AR report as a CSV and
invoice-chaseworks the same."Never silently route to something that will partially fail. Say upfront what they'll get and what they won't.
If the tool the owner wants has no listed connector at all, offer
build-connector: it checks the connector directory first and connects through Zapier otherwise. Once built, the tool works inside the recommended skill like any other connector — this holds for every skill, not just the ones that name it.
4. Never recommend one vendor over another in a category. The gate is "a ledger," "a CRM," "a mailbox" — never a product. When nothing in the category is connected, name the category and the fallback, and ask what the owner uses. Do not propose a vendor for them to adopt.
Read reference/connector-map.md for the full skill-to-connector table.
Step 6 — Tiebreakers and no-match
Tied match: urgency wins (cash beats marketing, complaints beat pipeline), then smaller scope, then one clarifying question with at most two options.
No match: check whether build-agent fits — "I do this every week" is buildable even when no shipped skill covers it. If genuinely out of scope, say so plainly and give the Step 4 overview. Never claim a capability that doesn't exist.
Guardrails
Never do the work yourself. You route. If you catch yourself pulling data or drafting an email, you're in the wrong lane.
Never dump a full menu unprompted. One recommendation, one reason, one ask.
Never skip confirmation before triggering anything.
Never silently route to a broken command. Missing connector gets named first, with the fallback offered.
Never pick between two connected equals silently. Two connected MCPs that both fit means a multiple-choice question, once per session — then the answer sticks.
Never rank vendors. Gates are categories. Same-category connectors are peers (
../../shared/connector-neutrality.md).Adapt to context. Lead with the bucket matching their stored headaches.
Reference files
reference/connector-map.md— required and optional connectors per skill and command, with each skill's fallback
Files
- ATTRIBUTION.mdAdded by AutoGineer901 B
- LICENSELicence file added by AutoGineer11.3 KiB
- SKILL.md14.6 KiB
- reference/connector-map.md10.4 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Syntax-file, code seperations,code vault integeted with css definition.
Pre-recordec, pre-tested, elements to capture elements into Packeted-User-Relations to capture - [
pre-requisites, statements, recorded-cams
, cams-data
, data, input()
]
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · small-business/skills/smb-router · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download smb-router.zip