[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718VKPNJCKK7NPDNX7XKKQV":3,"skill-same:01M718VKPNJCKK7NPDNX7XKKQV":83},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M718VKPNJCKK7NPDNX7XKKQV","lead-triage",null,"Scores inbound HubSpot leads by engagement signals, company fit, and urgency markers, ranks the ones worth a call today with talking points, drafts the follow-ups, and proposes calendar times for the owner to book. Use when the owner asks to prioritize, score, or rank leads, asks \"who should I call first,\" or asks about their pipeline. An ask that wants the ranked leads turned into a call list with time blocked on the calendar routes to \u002Fcall-list, which runs this skill first and then books the time.","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\u002Fsmall-business\u002Fskills\u002Flead-triage\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"triage","lead","lead triage","engagement","with","books","ask","when","use","call","company","time","fit","pipeline","for","call list","markers","which","leads","follow-ups","2026-11-10 10:12:30",false,"---\nname: lead-triage\nversion: 0.1.1\ndescription: >\n  Scores inbound HubSpot leads by engagement signals, company fit, and urgency\n  markers, ranks the ones worth a call today with talking points, drafts the\n  follow-ups, and proposes calendar times for the owner to book. Use when the\n  owner asks to prioritize, score, or rank leads, asks \"who should I call\n  first,\" or asks about their pipeline. An ask that wants the ranked leads\n  turned into a call list with time blocked on the calendar routes to\n  \u002Fcall-list, which runs this skill first and then books the time.\nallowed-tools: Read, WebFetch\n---\n\n# Lead Triage\n\n## Quick start\n\nPull inbound leads from HubSpot, score them, and surface a ranked call list with talking points. Drafts follow-ups and proposes calendar slots — never sends or books without owner approval.\n\n```\nUser: \"prioritize my leads\"\n→ Pull contacts: lifecycle stage Lead or MQL, status ≠ Unqualified\n→ Score each across engagement, company fit, urgency, recency\n→ Return ranked list (size adapts to volume) with talking points\n→ Offer to draft follow-ups and propose calendar slots\n```\n\n## Workflow\n\n1. **Pull leads from HubSpot.** Fetch contacts with `lifecyclestage` = `Lead` or `MQL` and `hs_lead_status` ≠ `Unqualified`. Use the field list in [reference\u002Fhubspot-scoring.md](reference\u002Fhubspot-scoring.md). If HubSpot is unavailable — not installed, not connected, or erroring — do not stop. Say so plainly and run the \"No HubSpot?\" path at the bottom of this file: ask for a CSV export or a rough pasted list, and score that instead.\n   - **Empty portal check.** If the pull returns zero contacts of any lifecycle stage, the portal is empty, not filtered wrong. Say so in one line, offer HubSpot's own setup (`manage_onboarding`, action `SET_GOAL`) or the \"No HubSpot?\" path, and do not diagnose lifecycle stages on a portal with nothing in it. The count is the test: `get_user_details` returns an `onboarded` flag, but a portal can report `onboarded: false` while holding hundreds of contacts, so the flag alone never decides this.\n\n2. **Clarify if trigger is ambiguous.** If the user said only \"pipeline\" without a qualifier, ask: *\"Quick pipeline overview (deal stages + total value) or prioritized call list?\"* — then route accordingly. Do not score leads on a bare \"pipeline.\"\n\n3. **Score each lead.** Apply the four-dimension model in [reference\u002Fhubspot-scoring.md](reference\u002Fhubspot-scoring.md):\n   - **Engagement** — email replies, opens, site visits in HubSpot (last 30 days only)\n   - **Company fit** — industry and employee count vs. owner's ICP (default: any industry, 1–50 employees). Read these from the company associated with the lead, not from the contact record — see the scoring reference. When leads have no associated company and a lead-data connector (Apollo or Clay) is connected, the enrichment leg in the scoring reference fills industry and size from the lead's email domain. It is metered — say how many rows it would enrich and what that costs in credits, and run it only on the owner's yes for this run. Nothing enriched is written back to the CRM from here.\n   - **Urgency** — lead age, stage duration, notes containing \"urgent \u002F ASAP \u002F deadline \u002F budget approved\". The keyword check requires actually fetching note bodies via the contact → notes association — follow the \"Fetch note bodies\" section of the scoring reference; the note count alone cannot fire it.\n   - **Recency penalty** — subtract points if last activity was \u003C24 hours ago (already touched today)\n\n   **Then check whether the scores actually separated.** If the highest and lowest composite differ by less than 10 points, the CRM has no signal to rank on. Do not present the order as a ranking — run the flat-score path in the scoring reference, say plainly that the signals are empty, and order by CRM facts instead. A false ranking sends the owner to call the wrong person.\n\n4. **Build the ranked list.** Sort descending by composite score. Adapt list size to volume:\n   - ≤10 leads → show all\n   - 11–30 leads → show top 5\n   - >30 leads → show top 8\n\n   For each lead: name, company, score, one-paragraph talking point, last activity summary. If engagement signals are all >30 days old, flag: *\"Engagement signals are stale — approach as cold outreach.\"*\n\n5. **Offer follow-up drafts.** Ask: *\"Draft follow-ups for any of these?\"* If yes, write one email per selected lead in the owner's voice per [the shared voice profile](..\u002F..\u002Fshared\u002Fvoice-profile.md). If that file has no profile yet, follow its \"When there is no sample\" instruction — ask for three emails the owner was happy with; if they decline, draft plain and neutral and say the drafts are un-voiced. Never invent a personality. Show drafts; do not send. If Mail is unavailable, hand the drafts over in chat as subject plus body for the owner to paste — that is a complete outcome.\n\n6. **Render the triage board as an artifact.** After the short chat answer — never instead of it — build an HTML page using the house artifact style (`..\u002F..\u002Fshared\u002Fartifact-style.md`): a ranked table with each lead's composite score in mono, an urgency status pill per row (good \u002F warn \u002F critical), and a talking-points line under each lead. If the flat-score path fired, say so on the page and drop the pill colors to neutral.\n\n7. **Offer calendar slots.** Ask: *\"Propose call slots for any of these?\"* If yes, check Calendar for open 30-minute windows in the next two business days (avoid slots with existing events ±15 min). Propose two options per lead. Never create calendar events without explicit owner approval. If Calendar is unavailable, ask the owner for two or three windows they can offer and use those instead of inventing times.\n\n## Approval gates\n\n- **Never send an email.** Draft only; owner sends from their inbox.\n- **Never create calendar events until approved by the user.**\n- **Never change lifecycle stage or mark a lead Unqualified** unless the owner explicitly asks.\n- **Never include `Customer` or `Evangelist` lifecycle contacts** in the lead list.\n- **If zero leads match the filter**, explain why and offer to check what lifecycle stages are in use — do not fabricate a list.\n\n## Reference\n\n- [reference\u002Fhubspot-scoring.md](reference\u002Fhubspot-scoring.md) — HubSpot field names, scoring weights, ICP defaults\n- [reference\u002Fgotchas.md](reference\u002Fgotchas.md) — edge cases: stale data, zero leads, pipeline disambiguation, customer contamination\n- [reference\u002Fexamples\u002Fhappy-path-triage.md](reference\u002Fexamples\u002Fhappy-path-triage.md) — worked output for a 7-lead list with draft and slot proposal\n\n## Closing offer\n\nEnd with one line on what the triage produced, then the most relevant next step with its trigger phrase — usually \"call list\" (`\u002Fcall-list`) to add calendar blocks around the ranking. Up to two others when they fit: \"write this outreach\" (`outreach-composer`) or \"update the CRM\" (`crm-autopilot`). Never more than three, and never re-offer something the owner already declined this session.\n\n## No HubSpot?\n\nPaste or upload the lead list — a CSV export or even a rough list works. Scoring and talking points run the same; the ranked call list comes back as chat plus a file instead of writing to the CRM.\n\n## Using a tool that isn't listed\n\nThe connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.\n","# Lead Triage\n\n## Quick start\n\nPull inbound leads from HubSpot, score them, and surface a ranked call list with talking points. Drafts follow-ups and proposes calendar slots — never sends or books without owner approval.\n\n```\nUser: \"prioritize my leads\"\n→ Pull contacts: lifecycle stage Lead or MQL, status ≠ Unqualified\n→ Score each across engagement, company fit, urgency, recency\n→ Return ranked list (size adapts to volume) with talking points\n→ Offer to draft follow-ups and propose calendar slots\n```\n\n## Workflow\n\n1. **Pull leads from HubSpot.** Fetch contacts with `lifecyclestage` = `Lead` or `MQL` and `hs_lead_status` ≠ `Unqualified`. Use the field list in [reference\u002Fhubspot-scoring.md](reference\u002Fhubspot-scoring.md). If HubSpot is unavailable — not installed, not connected, or erroring — do not stop. Say so plainly and run the \"No HubSpot?\" path at the bottom of this file: ask for a CSV export or a rough pasted list, and score that instead.\n   - **Empty portal check.** If the pull returns zero contacts of any lifecycle stage, the portal is empty, not filtered wrong. Say so in one line, offer HubSpot's own setup (`manage_onboarding`, action `SET_GOAL`) or the \"No HubSpot?\" path, and do not diagnose lifecycle stages on a portal with nothing in it. The count is the test: `get_user_details` returns an `onboarded` flag, but a portal can report `onboarded: false` while holding hundreds of contacts, so the flag alone never decides this.\n\n2. **Clarify if trigger is ambiguous.** If the user said only \"pipeline\" without a qualifier, ask: *\"Quick pipeline overview (deal stages + total value) or prioritized call list?\"* — then route accordingly. Do not score leads on a bare \"pipeline.\"\n\n3. **Score each lead.** Apply the four-dimension model in [reference\u002Fhubspot-scoring.md](reference\u002Fhubspot-scoring.md):\n   - **Engagement** — email replies, opens, site visits in HubSpot (last 30 days only)\n   - **Company fit** — industry and employee count vs. owner's ICP (default: any industry, 1–50 employees). Read these from the company associated with the lead, not from the contact record — see the scoring reference. When leads have no associated company and a lead-data connector (Apollo or Clay) is connected, the enrichment leg in the scoring reference fills industry and size from the lead's email domain. It is metered — say how many rows it would enrich and what that costs in credits, and run it only on the owner's yes for this run. Nothing enriched is written back to the CRM from here.\n   - **Urgency** — lead age, stage duration, notes containing \"urgent \u002F ASAP \u002F deadline \u002F budget approved\". The keyword check requires actually fetching note bodies via the contact → notes association — follow the \"Fetch note bodies\" section of the scoring reference; the note count alone cannot fire it.\n   - **Recency penalty** — subtract points if last activity was \u003C24 hours ago (already touched today)\n\n   **Then check whether the scores actually separated.** If the highest and lowest composite differ by less than 10 points, the CRM has no signal to rank on. Do not present the order as a ranking — run the flat-score path in the scoring reference, say plainly that the signals are empty, and order by CRM facts instead. A false ranking sends the owner to call the wrong person.\n\n4. **Build the ranked list.** Sort descending by composite score. Adapt list size to volume:\n   - ≤10 leads → show all\n   - 11–30 leads → show top 5\n   - >30 leads → show top 8\n\n   For each lead: name, company, score, one-paragraph talking point, last activity summary. If engagement signals are all >30 days old, flag: *\"Engagement signals are stale — approach as cold outreach.\"*\n\n5. **Offer follow-up drafts.** Ask: *\"Draft follow-ups for any of these?\"* If yes, write one email per selected lead in the owner's voice per [the shared voice profile](..\u002F..\u002Fshared\u002Fvoice-profile.md). If that file has no profile yet, follow its \"When there is no sample\" instruction — ask for three emails the owner was happy with; if they decline, draft plain and neutral and say the drafts are un-voiced. Never invent a personality. Show drafts; do not send. If Mail is unavailable, hand the drafts over in chat as subject plus body for the owner to paste — that is a complete outcome.\n\n6. **Render the triage board as an artifact.** After the short chat answer — never instead of it — build an HTML page using the house artifact style (`..\u002F..\u002Fshared\u002Fartifact-style.md`): a ranked table with each lead's composite score in mono, an urgency status pill per row (good \u002F warn \u002F critical), and a talking-points line under each lead. If the flat-score path fired, say so on the page and drop the pill colors to neutral.\n\n7. **Offer calendar slots.** Ask: *\"Propose call slots for any of these?\"* If yes, check Calendar for open 30-minute windows in the next two business days (avoid slots with existing events ±15 min). Propose two options per lead. Never create calendar events without explicit owner approval. If Calendar is unavailable, ask the owner for two or three windows they can offer and use those instead of inventing times.\n\n## Approval gates\n\n- **Never send an email.** Draft only; owner sends from their inbox.\n- **Never create calendar events until approved by the user.**\n- **Never change lifecycle stage or mark a lead Unqualified** unless the owner explicitly asks.\n- **Never include `Customer` or `Evangelist` lifecycle contacts** in the lead list.\n- **If zero leads match the filter**, explain why and offer to check what lifecycle stages are in use — do not fabricate a list.\n\n## Reference\n\n- [reference\u002Fhubspot-scoring.md](reference\u002Fhubspot-scoring.md) — HubSpot field names, scoring weights, ICP defaults\n- [reference\u002Fgotchas.md](reference\u002Fgotchas.md) — edge cases: stale data, zero leads, pipeline disambiguation, customer contamination\n- [reference\u002Fexamples\u002Fhappy-path-triage.md](reference\u002Fexamples\u002Fhappy-path-triage.md) — worked output for a 7-lead list with draft and slot proposal\n\n## Closing offer\n\nEnd with one line on what the triage produced, then the most relevant next step with its trigger phrase — usually \"call list\" (`\u002Fcall-list`) to add calendar blocks around the ranking. Up to two others when they fit: \"write this outreach\" (`outreach-composer`) or \"update the CRM\" (`crm-autopilot`). Never more than three, and never re-offer something the owner already declined this session.\n\n## No HubSpot?\n\nPaste or upload the lead list — a CSV export or even a rough list works. Scoring and talking points run the same; the ranked call list comes back as chat plus a file instead of writing to the CRM.\n\n## Using a tool that isn't listed\n\nThe connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.\n",{"name":5,"version":44,"description":45,"allowed-tools":46},"0.1.1","Scores inbound HubSpot leads by engagement signals, company fit, and urgency markers, ranks the ones worth a call today with talking points, drafts the follow-ups, and proposes calendar times for the owner to book. Use when the owner asks to prioritize, score, or rank leads, asks \"who should I call first,\" or asks about their pipeline. An ask that wants the ranked leads turned into a call list with time blocked on the calendar routes to \u002Fcall-list, which runs this skill first and then books the time.\n","Read, WebFetch","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","small-business\u002Fskills\u002Flead-triage",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill lead-triage",{"tool":61,"command":62},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill lead-triage",{"tool":64,"command":65},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill lead-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Flead-triage\u002FSKILL.md",true,[69,75,79],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"reference\u002Fexamples\u002Fhappy-path-triage.md","REFERENCE","参考文档",1897,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Flead-triage\u002Freference\u002Fexamples\u002Fhappy-path-triage.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"reference\u002Fgotchas.md",2019,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Flead-triage\u002Freference\u002Fgotchas.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"reference\u002Fhubspot-scoring.md",7092,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Flead-triage\u002Freference\u002Fhubspot-scoring.md",[84,109,132,154,181,207],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":39},"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",[],[91,92,93,94,95,96,97,26,98,25,99,100,101,102,103,104,105,106,107,108],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":39},"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",[],[116,117,118,36,119,120,121,122,123,124,26,24,125,126,127,128,108,129,130,131],"tax season organizer","tax","us federal","netsuite","paid","end","usd","only","now","xero","scanning","run","request","flags","list","stripe",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":39},"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",[],[139,117,140,141,118,142,143,119,144,145,146,147,148,33,149,121,150,151,152,153],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":165,"publishedAt":39},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[166,20,167,168,169,170,144,30,171,172,173,174,175,176,26,177,178,99,179,180],"speed to lead","speed","shared","back","cold","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":190,"publishedAt":39},"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",[187],{"categoryNo":188,"categoryName":189,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000036","内容创作者",[191,192,193,194,195,196,141,197,198,199,200,94,201,26,202,203,204,108,205,206],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":39},"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",[],[214,215,216,142,217,33,149,218,96,219,124,153,220,221,222,23,223,202,224,103],"router","smb","smb router","do","front","single","you","vague","can","plugin","focus"]