[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718D6913KSNV0HXK79JM3P5":3,"skill-same:01M718D6913KSNV0HXK79JM3P5":71},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M718D6913KSNV0HXK79JM3P5","brief",null,"Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35660,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Flegal\u002Fskills\u002Fbrief\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"question","RAPID","briefings","research","work","across","query","incident response","when","use","daily","litigation","breach","incident","scan","for","email","relevant","sources","2026-11-10 10:12:30",false,"---\nname: brief\ndescription: Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.\nargument-hint: \"[daily | topic \u003Cquery> | incident]\"\n---\n\n# \u002Fbrief -- Legal Team Briefing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.\n\n## Invocation\n\n```\n\u002Fbrief daily              # Morning brief of legal-relevant items\n\u002Fbrief topic [query]      # Research brief on a specific legal question\n\u002Fbrief incident [topic]   # Rapid brief on a developing situation\n```\n\nIf no mode is specified, ask the user which type of brief they need.\n\n## Modes\n\n---\n\n### Daily Brief\n\nA morning summary of everything a legal team member needs to know to start their day.\n\n#### Sources to Scan\n\nCheck each connected source for legal-relevant items:\n\n**Email (if connected):**\n- New contract requests or review requests\n- Compliance questions or reports\n- Responses from counterparties on active negotiations\n- Flagged or urgent items from the legal team inbox\n- External counsel communications\n- Regulatory or legal update newsletters\n\n**Calendar (if connected):**\n- Today's meetings that need legal prep (board meetings, deal reviews, vendor calls)\n- Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines)\n- Recurring legal team syncs\n\n**Chat (if connected):**\n- Overnight messages in legal team channels\n- Direct messages requesting legal input\n- Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms)\n- Escalations or urgent requests\n\n**CLM (if connected):**\n- Contracts awaiting review or signature\n- Approaching expiration dates (next 30 days)\n- Newly executed agreements\n\n**CRM (if connected):**\n- Deals moving to stages that require legal involvement\n- New opportunities flagged for legal review\n\n#### Output Format\n\n```\n## Daily Legal Brief -- [Date]\n\n### Urgent \u002F Action Required\n[Items needing immediate attention, sorted by urgency]\n\n### Contract Pipeline\n- **Awaiting Your Review**: [count and list]\n- **Pending Counterparty Response**: [count and list]\n- **Approaching Deadlines**: [items due this week]\n\n### New Requests\n[Contract review requests, NDA requests, compliance questions received since last brief]\n\n### Calendar Today\n[Meetings with legal relevance and what prep is needed]\n\n### Team Activity\n[Key messages or updates from legal team channels]\n\n### This Week's Deadlines\n[Upcoming deadlines and filing dates]\n\n### Sources Not Available\n[Any sources that were not connected or returned errors]\n```\n\n---\n\n### Topic Brief\n\nResearch and brief on a specific legal question or topic across available sources.\n\n#### Workflow\n\n1. Accept the topic query from the user\n2. Search across connected sources:\n   - **Documents**: Internal memos, prior analyses, playbooks, precedent\n   - **Email**: Prior communications on the topic\n   - **Chat**: Team discussions about the topic\n   - **CLM**: Related contracts or clauses\n3. Synthesize findings into a structured brief\n\n#### Output Format\n\n```\n## Topic Brief: [Topic]\n\n### Summary\n[2-3 sentence executive summary of findings]\n\n### Background\n[Context and history from internal sources]\n\n### Current State\n[What the organization's current position or approach is, based on available documents]\n\n### Key Considerations\n[Important factors, risks, or open questions]\n\n### Internal Precedent\n[Prior decisions, memos, or positions found in internal sources]\n\n### Gaps\n[What information is missing or what sources were not available]\n\n### Recommended Next Steps\n[What the user should do with this information]\n```\n\n#### Important Notes\n- Topic briefs synthesize what is available in connected sources; they do not substitute for formal legal research\n- If the topic requires current legal authority or case law, recommend the user consult a legal research platform (Westlaw, Lexis, etc.) or outside counsel\n- Always note the limitations of the sources searched\n\n---\n\n### Incident Brief\n\nRapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).\n\n#### Workflow\n\n1. Accept the incident topic or description\n2. Rapidly scan all connected sources for relevant context:\n   - **Email**: Communications about the incident\n   - **Chat**: Real-time discussions and escalations\n   - **Documents**: Relevant policies, response plans, insurance coverage\n   - **Calendar**: Scheduled response meetings\n   - **CLM**: Affected contracts, indemnification provisions, insurance requirements\n3. Compile into an actionable incident brief\n\n#### Output Format\n\n```\n## Incident Brief: [Topic]\n**Prepared**: [timestamp]\n**Classification**: [severity assessment if determinable]\n\n### Situation Summary\n[What is known about the incident]\n\n### Timeline\n[Chronological summary of events based on available sources]\n\n### Immediate Legal Considerations\n[Regulatory notification requirements, preservation obligations, privilege concerns]\n\n### Relevant Agreements\n[Contracts, insurance policies, or other agreements that may be implicated]\n\n### Internal Response\n[What response activity has already occurred based on email\u002Fchat]\n\n### Key Contacts\n[Relevant internal and external contacts identified from sources]\n\n### Recommended Immediate Actions\n1. [Most urgent action]\n2. [Second priority]\n3. [etc.]\n\n### Information Gaps\n[What is not yet known and needs to be determined]\n\n### Sources Checked\n[What was searched and what was not available]\n```\n\n#### Important Notes for Incident Briefs\n- Speed matters. Produce the brief quickly with available information rather than waiting for complete information\n- Flag any litigation hold or preservation obligations immediately\n- Note privilege considerations (mark the brief as attorney-client privileged \u002F work product if appropriate)\n- If the incident may involve a data breach, flag applicable notification deadlines (e.g., 72 hours for GDPR)\n- Recommend outside counsel engagement if the matter is significant\n\n## General Notes\n\n- If sources are unavailable, note the gaps prominently so the user knows what was not checked\n- For daily briefs, learn the user's preferences over time (what they find useful, what they want filtered out)\n- Briefs should be actionable: every item should have a clear next step or reason for inclusion\n- Keep briefs concise. Link to source materials rather than reproducing them in full\n","# \u002Fbrief -- Legal Team Briefing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.\n\n## Invocation\n\n```\n\u002Fbrief daily              # Morning brief of legal-relevant items\n\u002Fbrief topic [query]      # Research brief on a specific legal question\n\u002Fbrief incident [topic]   # Rapid brief on a developing situation\n```\n\nIf no mode is specified, ask the user which type of brief they need.\n\n## Modes\n\n---\n\n### Daily Brief\n\nA morning summary of everything a legal team member needs to know to start their day.\n\n#### Sources to Scan\n\nCheck each connected source for legal-relevant items:\n\n**Email (if connected):**\n- New contract requests or review requests\n- Compliance questions or reports\n- Responses from counterparties on active negotiations\n- Flagged or urgent items from the legal team inbox\n- External counsel communications\n- Regulatory or legal update newsletters\n\n**Calendar (if connected):**\n- Today's meetings that need legal prep (board meetings, deal reviews, vendor calls)\n- Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines)\n- Recurring legal team syncs\n\n**Chat (if connected):**\n- Overnight messages in legal team channels\n- Direct messages requesting legal input\n- Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms)\n- Escalations or urgent requests\n\n**CLM (if connected):**\n- Contracts awaiting review or signature\n- Approaching expiration dates (next 30 days)\n- Newly executed agreements\n\n**CRM (if connected):**\n- Deals moving to stages that require legal involvement\n- New opportunities flagged for legal review\n\n#### Output Format\n\n```\n## Daily Legal Brief -- [Date]\n\n### Urgent \u002F Action Required\n[Items needing immediate attention, sorted by urgency]\n\n### Contract Pipeline\n- **Awaiting Your Review**: [count and list]\n- **Pending Counterparty Response**: [count and list]\n- **Approaching Deadlines**: [items due this week]\n\n### New Requests\n[Contract review requests, NDA requests, compliance questions received since last brief]\n\n### Calendar Today\n[Meetings with legal relevance and what prep is needed]\n\n### Team Activity\n[Key messages or updates from legal team channels]\n\n### This Week's Deadlines\n[Upcoming deadlines and filing dates]\n\n### Sources Not Available\n[Any sources that were not connected or returned errors]\n```\n\n---\n\n### Topic Brief\n\nResearch and brief on a specific legal question or topic across available sources.\n\n#### Workflow\n\n1. Accept the topic query from the user\n2. Search across connected sources:\n   - **Documents**: Internal memos, prior analyses, playbooks, precedent\n   - **Email**: Prior communications on the topic\n   - **Chat**: Team discussions about the topic\n   - **CLM**: Related contracts or clauses\n3. Synthesize findings into a structured brief\n\n#### Output Format\n\n```\n## Topic Brief: [Topic]\n\n### Summary\n[2-3 sentence executive summary of findings]\n\n### Background\n[Context and history from internal sources]\n\n### Current State\n[What the organization's current position or approach is, based on available documents]\n\n### Key Considerations\n[Important factors, risks, or open questions]\n\n### Internal Precedent\n[Prior decisions, memos, or positions found in internal sources]\n\n### Gaps\n[What information is missing or what sources were not available]\n\n### Recommended Next Steps\n[What the user should do with this information]\n```\n\n#### Important Notes\n- Topic briefs synthesize what is available in connected sources; they do not substitute for formal legal research\n- If the topic requires current legal authority or case law, recommend the user consult a legal research platform (Westlaw, Lexis, etc.) or outside counsel\n- Always note the limitations of the sources searched\n\n---\n\n### Incident Brief\n\nRapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).\n\n#### Workflow\n\n1. Accept the incident topic or description\n2. Rapidly scan all connected sources for relevant context:\n   - **Email**: Communications about the incident\n   - **Chat**: Real-time discussions and escalations\n   - **Documents**: Relevant policies, response plans, insurance coverage\n   - **Calendar**: Scheduled response meetings\n   - **CLM**: Affected contracts, indemnification provisions, insurance requirements\n3. Compile into an actionable incident brief\n\n#### Output Format\n\n```\n## Incident Brief: [Topic]\n**Prepared**: [timestamp]\n**Classification**: [severity assessment if determinable]\n\n### Situation Summary\n[What is known about the incident]\n\n### Timeline\n[Chronological summary of events based on available sources]\n\n### Immediate Legal Considerations\n[Regulatory notification requirements, preservation obligations, privilege concerns]\n\n### Relevant Agreements\n[Contracts, insurance policies, or other agreements that may be implicated]\n\n### Internal Response\n[What response activity has already occurred based on email\u002Fchat]\n\n### Key Contacts\n[Relevant internal and external contacts identified from sources]\n\n### Recommended Immediate Actions\n1. [Most urgent action]\n2. [Second priority]\n3. [etc.]\n\n### Information Gaps\n[What is not yet known and needs to be determined]\n\n### Sources Checked\n[What was searched and what was not available]\n```\n\n#### Important Notes for Incident Briefs\n- Speed matters. Produce the brief quickly with available information rather than waiting for complete information\n- Flag any litigation hold or preservation obligations immediately\n- Note privilege considerations (mark the brief as attorney-client privileged \u002F work product if appropriate)\n- If the incident may involve a data breach, flag applicable notification deadlines (e.g., 72 hours for GDPR)\n- Recommend outside counsel engagement if the matter is significant\n\n## General Notes\n\n- If sources are unavailable, note the gaps prominently so the user knows what was not checked\n- For daily briefs, learn the user's preferences over time (what they find useful, what they want filtered out)\n- Briefs should be actionable: every item should have a clear next step or reason for inclusion\n- Keep briefs concise. Link to source materials rather than reproducing them in full\n",{"name":5,"description":7,"argument-hint":48},"[daily | topic \u003Cquery> | incident]","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","legal\u002Fskills\u002Fbrief",3944,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 06:21:52",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill brief",{"tool":63,"command":64},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill brief",{"tool":66,"command":67},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Flegal\u002Fskills\u002Fbrief\u002FSKILL.md",true,[],[72,98,123,144,171,196],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":43},"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",[],[79,80,81,82,83,84,85,32,86,87,88,89,90,91,92,93,94,95,96,97],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":43},"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",[],[105,106,107,108,109,110,111,112,113,114,32,115,116,117,118,119,97,120,121,122],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":43},"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",[],[130,106,131,132,107,133,134,109,135,136,137,138,139,39,140,111,141,24,142,143],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","paypal","business",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"publishedAt":43},"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",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员",[154,155,156,157,158,159,135,160,161,162,163,164,165,166,32,167,168,88,169,170],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":43},"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",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[181,182,183,184,185,186,132,5,187,188,189,82,190,32,191,192,193,97,194,195],"social","social content engine","engine","content engine","social content","content","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":43},"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",[],[203,204,205,133,206,39,140,207,84,208,114,143,209,210,211,212,213,191,214,92],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]