The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks "what can you do," "help me with my business," "what should I focus on," "I don't know where to start," or any open-ended business request that doesn't clearly match a single skill.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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-payroll
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.
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.
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.
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.
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 invoices
Remember 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:
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."invoice-chase works the same."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.
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.
../../shared/connector-neutrality.md).reference/connector-map.md — required and optional connectors per skill and command, with each skill's fallbackまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
日本語の概要は準備中です。原文の説明を表示しています。
360-degree view of an account - CRM data, recent email threads, docs, transcripts, and internal chat chatter, synthesized into one brief. Use when the user asks "tell me about [account]" (an existing customer; for a prospect, account-research), "account context for [name]", "what's going on with [account]", or "catch me up on [account]".
日本語の概要は準備中です。原文の説明を表示しています。
Build or refresh a strategic account plan - current state, goals, stakeholder coverage, opportunity map, risks, and the action plan - written to a doc and key fields synced to the CRM. Use when the user says "build an account plan for [account]", "update the [account] plan", "account planning for [account]", or before a planning cycle / QBR.
日本語の概要は準備中です。原文の説明を表示しています。
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
日本語の概要は準備中です。原文の説明を表示しています。
Research a target company and optionally a specific contact - company overview, recent news, likely priorities, and fit against your ICP. Cross-references existing CRM records. Use when the user asks to "research [company]", "look into [company]", "prospect research on [company]", "look up [person]", "intel on [prospect]", "who is [person] at [company]", or "tell me about [company]" when the company is a prospect rather than an existing account.
日本語の概要は準備中です。原文の説明を表示しています。
Score and tier a list of accounts (or your full book) against ICP fit and engagement signals to prioritize where to spend time. Use when the user asks to "tier my accounts", "prioritize my book", "which accounts should I focus on", or "score these accounts".
日本語の概要は準備中です。原文の説明を表示しています。