[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718SC6BEPZJ743GHVY87G01":3,"skill-same:01M718SC6BEPZJ743GHVY87G01":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M718SC6BEPZJ743GHVY87G01","build-agent",null,"Turns a task the owner keeps doing by hand into a named, reusable skill they can trigger by name or put on a schedule. Watches them do it once or listens to them describe it, works out what varies and what stays fixed, writes the skill with approval checkpoints in the right places, registers it with the router, and shares it with the team. This is how a business gets a workflow nobody shipped for them. Use this whenever the owner describes something repetitive they wish were automatic — including phrasings like \"I do this every week,\" \"can you remember how to do this,\" \"make this a thing I can just ask for,\" \"build me an agent,\" \"automate this for me,\" \"turn this into a workflow,\" or \"I want this to happen every Monday.\" Reach for it when they describe a routine, even without asking for automation.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35656,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fbuild-agent\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"build","build agent","automate","describe","automatic","routine","read","how","me","router","hand","team","schedule","ask","you","workflow","automate this","when","how to","monday","2026-11-10 10:12:30",false,"---\nname: build-agent\ndescription: >\n  Turns a task the owner keeps doing by hand into a named, reusable skill they\n  can trigger by name or put on a schedule. Watches them do it once or listens\n  to them describe it, works out what varies and what stays fixed, writes the\n  skill with approval checkpoints in the right places, registers it with the\n  router, and shares it with the team. This is how a business gets a workflow\n  nobody shipped for them. Use this whenever the owner describes something\n  repetitive they wish were automatic — including phrasings like \"I do this\n  every week,\" \"can you remember how to do this,\" \"make this a thing I can just\n  ask for,\" \"build me an agent,\" \"automate this for me,\" \"turn this into a\n  workflow,\" or \"I want this to happen every Monday.\" Reach for it when they\n  describe a routine, even without asking for automation.\nallowed-tools: Read, WebFetch\n---\n\n# Build Agent\n\nTurn something the owner does every week into something they ask for by name.\n\nThis is what keeps the plugin from having to ship every industry's workflow. No catalog can cover a septic contractor's permit routine or an insurance agency's carrier commission reconciliation. Those owners can build them.\n\n## Step 1 — Watch it happen, or hear it described\n\nTwo starting points, and the first is much better.\n\n**Best: they just did it in this conversation.** If the owner has walked through the task with you — pulled the files, made the decisions, corrected you twice — that transcript is the specification. Extract it rather than re-interviewing them. The corrections they made are the most valuable part, because they encode judgment the owner would never have thought to state.\n\n**Otherwise: they describe it.** Ask them to walk through the last time they did it, concretely. Real specifics beat an abstract description every time — \"last Tuesday I pulled the carrier file, matched it against what we'd booked, and chased six discrepancies\" tells you more than \"I reconcile commissions.\"\n\nRead `reference\u002Fcapture.md` for how to get a complete picture without an interrogation.\n\n## Step 2 — Separate what varies from what stays fixed\n\nThis is the whole craft of the step. A skill that hardcodes last Tuesday's specifics only works on last Tuesday.\n\nFor each part of the task, decide:\n\n- **Fixed** — the sequence, the sources, the output format, the rules\n- **Varies** — dates, names, amounts, which file, which customer\n- **Judgment** — the parts where the owner decides, which become approval gates\n\nThe corrections the owner made while walking through it usually mark the judgment points. When someone says \"no, not that one — we skip anything under USD 50,\" that is a rule. When they say \"hmm, depends,\" that is an approval gate.\n\n## Step 3 — Find the approval gates\n\nEvery step that sends, spends, publishes, or deletes needs a gate. So does every step where the owner hesitated.\n\nDo not gate everything — a skill that asks permission nine times is worse than doing it by hand. Gate the consequential and the ambiguous, and let the rest run.\n\nRead `reference\u002Fskill_authoring.md` for where gates belong and how to phrase them.\n\n## Step 4 — Write it\n\nProduce a real skill in the same shape as everything else in this plugin: a `SKILL.md` with frontmatter and numbered steps, plus a `reference\u002F` folder if the detail warrants it.\n\nRequirements it must meet, same as every shipped skill:\n\n- Name and folder match, lowercase with hyphens\n- Description says what it does **and** when to trigger, in third person\n- A real fallback for when a connector is missing\n- Approval gates on anything consequential\n- Never invents a number; missing data is reported as missing\n\n**Write it in the owner's terms, not in generic business language.** If they call it \"the carrier file,\" the skill says carrier file. A skill full of unfamiliar vocabulary is one they will not trust to run unattended.\n\n## Step 5 — Test it on a real case, before they rely on it\n\nRun the new skill against a case the owner already knows the answer to — ideally the exact one they walked through. Show the output next to what they got by hand.\n\nThis is the step that determines whether the skill gets used. An owner who has seen it reproduce a known-good result will schedule it. One who hasn't will run it manually and check it every time, which saves nothing.\n\nIf it doesn't match, fix the skill and run it again. Do not ask the owner to accept a near-miss.\n\n## Step 6 — Register and set the cadence\n\nAdd it to `smb-router` so plain-English requests reach it, and record the trigger phrases the owner actually uses.\n\nIf it is a recurring task, offer to schedule it. Scheduling is what converts \"a skill I could run\" into \"something that happens without me,\" which is the outcome they wanted.\n\n## Step 7 — Share it, with approval\n\nOffer to share with the team. Say what sharing means: who gets it, what data it can reach, and what it can do unattended.\n\n**Be specific about the risk when a skill sends, spends, or writes.** A skill that emails customers, running for someone who did not build it and does not know its assumptions, is a real hazard. Recommend draft-only for shared skills that send anything.\n\n## What not to do\n\n- **Do not re-interview about a task they just walked through.** The transcript is the spec.\n- **Do not hardcode the example.** Names, dates, and amounts vary; the sequence does not.\n- **Do not gate every step.** Nine approvals is worse than doing it by hand.\n- **Do not skip the test run.** An untested skill gets checked manually forever, which saves nothing.\n- **Do not write it in generic business language.** Their words, or they won't trust it.\n- **Do not build something that sends or spends without approval gates.** Ever, regardless of what the owner asks for.\n\n## After the build\n\nThe owner now has a named skill they can trigger or schedule. If the new skill hit a tool that isn't connected, \"connect to my ERP\" (`build-connector`) is the natural next step — it turns the missing system into a working source. Also nearby: \"brief me\" to fold the new output into the daily picture, and \"Monday brief\" if the skill should feed the weekly one. Offer at most three, and skip any offer the owner already declined this session.\n\n## Reference files\n\n- `reference\u002Fcapture.md` — getting a complete picture of the task without an interrogation\n- `reference\u002Fskill_authoring.md` — the structure, frontmatter, and where approval gates belong\n- `reference\u002Fgotchas.md` — the failure modes that produce a skill nobody uses\n","# Build Agent\n\nTurn something the owner does every week into something they ask for by name.\n\nThis is what keeps the plugin from having to ship every industry's workflow. No catalog can cover a septic contractor's permit routine or an insurance agency's carrier commission reconciliation. Those owners can build them.\n\n## Step 1 — Watch it happen, or hear it described\n\nTwo starting points, and the first is much better.\n\n**Best: they just did it in this conversation.** If the owner has walked through the task with you — pulled the files, made the decisions, corrected you twice — that transcript is the specification. Extract it rather than re-interviewing them. The corrections they made are the most valuable part, because they encode judgment the owner would never have thought to state.\n\n**Otherwise: they describe it.** Ask them to walk through the last time they did it, concretely. Real specifics beat an abstract description every time — \"last Tuesday I pulled the carrier file, matched it against what we'd booked, and chased six discrepancies\" tells you more than \"I reconcile commissions.\"\n\nRead `reference\u002Fcapture.md` for how to get a complete picture without an interrogation.\n\n## Step 2 — Separate what varies from what stays fixed\n\nThis is the whole craft of the step. A skill that hardcodes last Tuesday's specifics only works on last Tuesday.\n\nFor each part of the task, decide:\n\n- **Fixed** — the sequence, the sources, the output format, the rules\n- **Varies** — dates, names, amounts, which file, which customer\n- **Judgment** — the parts where the owner decides, which become approval gates\n\nThe corrections the owner made while walking through it usually mark the judgment points. When someone says \"no, not that one — we skip anything under USD 50,\" that is a rule. When they say \"hmm, depends,\" that is an approval gate.\n\n## Step 3 — Find the approval gates\n\nEvery step that sends, spends, publishes, or deletes needs a gate. So does every step where the owner hesitated.\n\nDo not gate everything — a skill that asks permission nine times is worse than doing it by hand. Gate the consequential and the ambiguous, and let the rest run.\n\nRead `reference\u002Fskill_authoring.md` for where gates belong and how to phrase them.\n\n## Step 4 — Write it\n\nProduce a real skill in the same shape as everything else in this plugin: a `SKILL.md` with frontmatter and numbered steps, plus a `reference\u002F` folder if the detail warrants it.\n\nRequirements it must meet, same as every shipped skill:\n\n- Name and folder match, lowercase with hyphens\n- Description says what it does **and** when to trigger, in third person\n- A real fallback for when a connector is missing\n- Approval gates on anything consequential\n- Never invents a number; missing data is reported as missing\n\n**Write it in the owner's terms, not in generic business language.** If they call it \"the carrier file,\" the skill says carrier file. A skill full of unfamiliar vocabulary is one they will not trust to run unattended.\n\n## Step 5 — Test it on a real case, before they rely on it\n\nRun the new skill against a case the owner already knows the answer to — ideally the exact one they walked through. Show the output next to what they got by hand.\n\nThis is the step that determines whether the skill gets used. An owner who has seen it reproduce a known-good result will schedule it. One who hasn't will run it manually and check it every time, which saves nothing.\n\nIf it doesn't match, fix the skill and run it again. Do not ask the owner to accept a near-miss.\n\n## Step 6 — Register and set the cadence\n\nAdd it to `smb-router` so plain-English requests reach it, and record the trigger phrases the owner actually uses.\n\nIf it is a recurring task, offer to schedule it. Scheduling is what converts \"a skill I could run\" into \"something that happens without me,\" which is the outcome they wanted.\n\n## Step 7 — Share it, with approval\n\nOffer to share with the team. Say what sharing means: who gets it, what data it can reach, and what it can do unattended.\n\n**Be specific about the risk when a skill sends, spends, or writes.** A skill that emails customers, running for someone who did not build it and does not know its assumptions, is a real hazard. Recommend draft-only for shared skills that send anything.\n\n## What not to do\n\n- **Do not re-interview about a task they just walked through.** The transcript is the spec.\n- **Do not hardcode the example.** Names, dates, and amounts vary; the sequence does not.\n- **Do not gate every step.** Nine approvals is worse than doing it by hand.\n- **Do not skip the test run.** An untested skill gets checked manually forever, which saves nothing.\n- **Do not write it in generic business language.** Their words, or they won't trust it.\n- **Do not build something that sends or spends without approval gates.** Ever, regardless of what the owner asks for.\n\n## After the build\n\nThe owner now has a named skill they can trigger or schedule. If the new skill hit a tool that isn't connected, \"connect to my ERP\" (`build-connector`) is the natural next step — it turns the missing system into a working source. Also nearby: \"brief me\" to fold the new output into the daily picture, and \"Monday brief\" if the skill should feed the weekly one. Offer at most three, and skip any offer the owner already declined this session.\n\n## Reference files\n\n- `reference\u002Fcapture.md` — getting a complete picture of the task without an interrogation\n- `reference\u002Fskill_authoring.md` — the structure, frontmatter, and where approval gates belong\n- `reference\u002Fgotchas.md` — the failure modes that produce a skill nobody uses\n",{"name":5,"description":49,"allowed-tools":50},"Turns a task the owner keeps doing by hand into a named, reusable skill they can trigger by name or put on a schedule. Watches them do it once or listens to them describe it, works out what varies and what stays fixed, writes the skill with approval checkpoints in the right places, registers it with the router, and shares it with the team. This is how a business gets a workflow nobody shipped for them. Use this whenever the owner describes something repetitive they wish were automatic — including phrasings like \"I do this every week,\" \"can you remember how to do this,\" \"make this a thing I can just ask for,\" \"build me an agent,\" \"automate this for me,\" \"turn this into a workflow,\" or \"I want this to happen every Monday.\" Reach for it when they describe a routine, even without asking for automation.\n","Read, WebFetch","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","small-business\u002Fskills\u002Fbuild-agent",3945,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-13 23:29:50",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill build-agent",{"tool":65,"command":66},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill build-agent",{"tool":68,"command":69},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill build-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fbuild-agent\u002FSKILL.md",true,[73,79,83],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"reference\u002Fcapture.md","REFERENCE","参考文档",4463,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fbuild-agent\u002Freference\u002Fcapture.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"reference\u002Fgotchas.md",5143,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fbuild-agent\u002Freference\u002Fgotchas.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"reference\u002Fskill_authoring.md",5834,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fbuild-agent\u002Freference\u002Fskill_authoring.md",[88,111,136,159,187,212],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":44},"01M718Y97HCGW12Q53PSJDY03W","ticket-deflector","Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says \"draft a response,\" \"answer this customer,\" \"where's my order,\" \"I want a refund,\" \"check my orders,\" or \"anything about to blow up.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fticket-deflector\u002FSKILL.md",[],[95,96,97,98,99,100,101,41,39,37,102,103,104,105,106,107,108,109,110,30],"ticket","ticket deflector","mode","up","payments","open","writing","Connector","text","mail","window","next","customer","support","crm","past",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":44},"01M718Y55HFAN5705ME5VEDZ9K","tax-season-organizer","Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags.\nAny tax request routes first to \u002Ftax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: \"books are closed, now do the 1099s,\" \"run the quarterly estimate off the closed numbers,\" or \"just the contractor W-9 list.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-season-organizer\u002FSKILL.md",[],[118,119,120,121,122,123,124,125,126,127,41,128,129,130,131,132,30,133,134,135],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":44},"01M718Y13VVPHDD9NTDBVFJ2AZ","tax-prep","Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on \"quarterly taxes,\" \"estimated tax payment,\" \"how much should I set aside,\" \"1099s,\" \"1099-NEC,\" \"W-9s,\" \"year-end tax prep,\" \"get my books ready for my accountant,\" any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-prep\u002FSKILL.md",[],[143,119,144,145,120,146,147,122,148,149,150,151,152,153,154,124,155,156,157,158],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","for","trigger","material","question","paypal","business",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":170,"publishedAt":44},"01M718XWTWQZ01GYSG9T8RW8TW","speed-to-lead","Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like \"leads are going cold,\" \"did anyone answer that inquiry,\" \"I keep missing form submissions,\" \"nothing falls through the cracks,\" \"handle my inbound,\" \"respond to this lead,\" or \"we lose people because nobody gets back fast enough.\" Reach for it for a single unanswered inquiry as readily as for a standing setup.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fspeed-to-lead\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[171,172,173,174,175,176,148,177,178,179,180,181,182,183,41,36,184,102,185,186],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","logs","sure","human",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":196,"publishedAt":44},"01M718XQYMN1KY3TPS33967FK0","social-content-engine","Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including \"I need to post more,\" \"we've gone quiet on Instagram,\" \"what should we post this month,\" \"make the content,\" \"give me a month of posts,\" \"write this in my voice,\" \"repurpose this,\" or \"set up our content calendar.\" Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsocial-content-engine\u002FSKILL.md",[193],{"categoryNo":194,"categoryName":195,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000036","内容创作者",[197,198,199,200,201,202,145,203,204,205,206,98,207,41,32,208,209,30,210,211],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","product","calendar","write","drafts",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":44},"01M718XMPJVH0EVRVP998BVZPC","smb-router","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.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsmb-router\u002FSKILL.md",[],[33,219,220,146,221,153,154,222,100,223,127,158,38,224,225,226,227,32,228,106],"smb","smb router","do","front","single","vague","can","with","plugin","focus"]