[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718X4X2P9747C260QPP8ZRR":3,"skill-same:01M718X4X2P9747C260QPP8ZRR":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},"01M718X4X2P9747C260QPP8ZRR","restock",null,"Turns what is actually selling into a reorder decision and gets it all the way into the books — computes sales velocity and conservative stockout dates per item, sizes the reorder, drafts the purchase order and the vendor email, and then stages the matching entry so the bill matches against the PO when it arrives. Flags the money sitting still too, so dead stock gets cleared instead of reordered. Runs on Shopify, Square, or an uploaded sales and stock CSV, and deepens with QuickBooks, Gmail or M365, Calendar, and NetSuite. No PO is sent and no vendor is emailed without approval. Use it when the owner says \"what do I need to reorder,\" \"am I going to run out,\" \"restock,\" \"we keep running out of filters,\" \"draft a PO for my supplier,\" or \"how much cash is sitting in the warehouse.\"","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\u002Frestock\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"how","quickbooks","my","flags","gmail","square","drafts","read","calendar","run","velocity","m365","books","when","filters","decision","purchase","stock","netsuite","2026-11-10 10:12:30",false,"---\nname: restock\ndescription: Turns what is actually selling into a reorder decision and gets it all the way into the books — computes sales velocity and conservative stockout dates per item, sizes the reorder, drafts the purchase order and the vendor email, and then stages the matching entry so the bill matches against the PO when it arrives. Flags the money sitting still too, so dead stock gets cleared instead of reordered. Runs on Shopify, Square, or an uploaded sales and stock CSV, and deepens with QuickBooks, Gmail or M365, Calendar, and NetSuite. No PO is sent and no vendor is emailed without approval. Use it when the owner says \"what do I need to reorder,\" \"am I going to run out,\" \"restock,\" \"we keep running out of filters,\" \"draft a PO for my supplier,\" or \"how much cash is sitting in the warehouse.\"\nallowed-tools: Read, WebFetch\n---\n\n# Restock\n\nChain two skills so reordering ends in the books rather than in a forgotten email: `inventory-planner` decides what to buy, `ap-processor` stages what it will cost.\n\nThe gap this closes is small and expensive. The reorder gets figured out, the PO gets drafted, the email gets sent — and then nothing is recorded anywhere, so when the bill lands six weeks later nobody can tell whether the price or the quantity was right.\n\n## Step 1 — Work out what to buy (inventory-planner)\n\nInvoke `inventory-planner`.\n\n- **Goes in:** sales history and stock on hand from Shopify, Square, or NetSuite, or an uploaded CSV of both.\n- **Comes out:** 7-day and 28-day velocity per item, conservative stockout dates, a sized 60-day reorder with dollar costs, and a separate slow-mover list.\n\n`inventory-planner` owns all of the math — the two velocity windows, the distortion handling, the lead-time comparison, the seasonality rule. Do not redo any of it here.\n\nTwo of its rules matter enough to name in the chain:\n\n- **Zero-velocity items are never reorder candidates.** They come through as slow movers with the cash tied up in them. No sales means stop buying, not buy more.\n- **An out-of-stock period is not zero demand.** It is suppressed demand, and treating it as zero under-orders the item forever.\n\n**Gate — the buy list.** Show the total dollars and the count of items about to stock out before anything is drafted. The owner approves the list, trims it, or changes quantities. Every line carries its velocity, days of cover, lead time, quantity, and cost, so the decision takes a minute instead of a rebuild.\n\n## Step 2 — Draft the PO and the vendor email (inventory-planner)\n\nFor the approved lines, `inventory-planner` drafts a purchase order per vendor and the email to go with it, written in the owner's voice.\n\n**Gate — both wait for an explicit yes, separately from Step 1.** Approving the buy list is agreeing on what to order. Sending the PO is committing the money and spending the vendor relationship. State the vendor, the line items, and the total before asking.\n\nWithout a mail connector (Gmail or Microsoft 365) connected, the PO and the email are files the owner sends by hand. That is a complete outcome.\n\n## Step 3 — Leave a record the future bill can match against\n\nTwo different things happen here, and it matters which skill owns which.\n\n**`inventory-planner` keeps the purchase order itself.** The approved PO is its document — vendor, line items, quantities, prices, expected date. It is saved and handed to the owner in Step 2, and that is the record of what was ordered.\n\n**`ap-processor` takes the coded memo, not the PO.** Hand it the vendor, the PO number, the total, the expected date, and the account, class, and job the spend belongs to. `ap-processor` does not create purchase orders in the ledger — it reads them when a bill arrives, to run the three-way match of bill against PO against receiving ticket. What it needs from this step is a coded record sitting where that match will look for it.\n\n- **Goes in:** vendor, PO number, total, expected date, and the coding.\n- **Comes out:** a coded memo filed against the vendor, so when the bill lands in six weeks the price and the quantity can be checked against what was actually approved.\n\n**Gate — the coding approval.** This is `ap-processor`'s own gate and it holds here. Nothing is written to the ledger until the owner says yes, and nothing lands as a bill and never as a payment. **No money moves in this command at all** — paying for what arrives is `\u002Fpay-the-bills`.\n\nIf a code is uncertain on a new vendor, `ap-processor` asks rather than guessing. One question now beats a miscoded year.\n\nWithout a ledger connector, the coded memo comes out as an import file and a summary alongside the PO. The three-way match still happens later, by hand, against a record that exists.\n\n## Step 4 — Make it a rhythm\n\nRay Okonkwo runs Okonkwo Mechanical off a parts shelf he checks when something is missing, which is always too late. With Google Calendar connected, offer once — after a restock the owner found useful — to put a recurring block on the calendar for the reorder decision.\n\nThis works far better as a rhythm than as a fire drill. Offer it once. On a no or on silence, drop it.\n\n## Fallback path\n\nA sales CSV plus a stock count is a fully supported input. Many businesses count on a clipboard, and that is legitimate data. Velocity, stockout dates, reorder sizing, the PO, and the vendor email all come out the same. The books entry becomes an import file.\n\n## What not to do\n\n- **Do not send a PO or a vendor email without approval.** One spends money, the other spends goodwill.\n- **Do not treat the buy-list approval as approval to send.** Two gates, two decisions.\n- **Do not reorder a zero-velocity item.**\n- **Do not size a reorder without subtracting what is already inbound.** Double-ordering a slow item buries cash for years.\n- **Do not invent a velocity, a lead time, or a stockout date.** Too little history is reported by SKU.\n- **Do not pay anything here.** POs are staged, not paid. Payment is `\u002Fpay-the-bills`.\n- **Do not report units without dollars.** The owner is deciding about cash, not pieces.\n\n## Output\n\n**Deliver the reorder plan per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `..\u002F..\u002Fshared\u002Fartifact-style.md`):\n\n- **Visual artifact (the default):** render the plan as an HTML page in the house style — total committed as the lead stat tile in dollars, each SKU a row with velocity, stockout date, and reorder size in tabular-nums, and a pill on anything already inbound. The PO documents and any import file ride along as working files, not second deliverables.\n- **docx \u002F md \u002F notion \u002F canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.\n- **Best for skill:** use the visual artifact — this output is a buy decision, not prose.\n\n## After the run\n\nThe POs are out and a coded record is waiting for the bills to match against. When those bills land, the natural next step is \"pay the bills\" — `\u002Fpay-the-bills` runs the match, the cash check, and the payment gate. Also nearby: \"cash forecast\" (`cash-flow-snapshot`) to see what the committed orders do to the next 60 days, and \"close the month\" (`\u002Fclose-month`) when the period ends. Offer at most three, and skip any offer the owner already declined this session.\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","# Restock\n\nChain two skills so reordering ends in the books rather than in a forgotten email: `inventory-planner` decides what to buy, `ap-processor` stages what it will cost.\n\nThe gap this closes is small and expensive. The reorder gets figured out, the PO gets drafted, the email gets sent — and then nothing is recorded anywhere, so when the bill lands six weeks later nobody can tell whether the price or the quantity was right.\n\n## Step 1 — Work out what to buy (inventory-planner)\n\nInvoke `inventory-planner`.\n\n- **Goes in:** sales history and stock on hand from Shopify, Square, or NetSuite, or an uploaded CSV of both.\n- **Comes out:** 7-day and 28-day velocity per item, conservative stockout dates, a sized 60-day reorder with dollar costs, and a separate slow-mover list.\n\n`inventory-planner` owns all of the math — the two velocity windows, the distortion handling, the lead-time comparison, the seasonality rule. Do not redo any of it here.\n\nTwo of its rules matter enough to name in the chain:\n\n- **Zero-velocity items are never reorder candidates.** They come through as slow movers with the cash tied up in them. No sales means stop buying, not buy more.\n- **An out-of-stock period is not zero demand.** It is suppressed demand, and treating it as zero under-orders the item forever.\n\n**Gate — the buy list.** Show the total dollars and the count of items about to stock out before anything is drafted. The owner approves the list, trims it, or changes quantities. Every line carries its velocity, days of cover, lead time, quantity, and cost, so the decision takes a minute instead of a rebuild.\n\n## Step 2 — Draft the PO and the vendor email (inventory-planner)\n\nFor the approved lines, `inventory-planner` drafts a purchase order per vendor and the email to go with it, written in the owner's voice.\n\n**Gate — both wait for an explicit yes, separately from Step 1.** Approving the buy list is agreeing on what to order. Sending the PO is committing the money and spending the vendor relationship. State the vendor, the line items, and the total before asking.\n\nWithout a mail connector (Gmail or Microsoft 365) connected, the PO and the email are files the owner sends by hand. That is a complete outcome.\n\n## Step 3 — Leave a record the future bill can match against\n\nTwo different things happen here, and it matters which skill owns which.\n\n**`inventory-planner` keeps the purchase order itself.** The approved PO is its document — vendor, line items, quantities, prices, expected date. It is saved and handed to the owner in Step 2, and that is the record of what was ordered.\n\n**`ap-processor` takes the coded memo, not the PO.** Hand it the vendor, the PO number, the total, the expected date, and the account, class, and job the spend belongs to. `ap-processor` does not create purchase orders in the ledger — it reads them when a bill arrives, to run the three-way match of bill against PO against receiving ticket. What it needs from this step is a coded record sitting where that match will look for it.\n\n- **Goes in:** vendor, PO number, total, expected date, and the coding.\n- **Comes out:** a coded memo filed against the vendor, so when the bill lands in six weeks the price and the quantity can be checked against what was actually approved.\n\n**Gate — the coding approval.** This is `ap-processor`'s own gate and it holds here. Nothing is written to the ledger until the owner says yes, and nothing lands as a bill and never as a payment. **No money moves in this command at all** — paying for what arrives is `\u002Fpay-the-bills`.\n\nIf a code is uncertain on a new vendor, `ap-processor` asks rather than guessing. One question now beats a miscoded year.\n\nWithout a ledger connector, the coded memo comes out as an import file and a summary alongside the PO. The three-way match still happens later, by hand, against a record that exists.\n\n## Step 4 — Make it a rhythm\n\nRay Okonkwo runs Okonkwo Mechanical off a parts shelf he checks when something is missing, which is always too late. With Google Calendar connected, offer once — after a restock the owner found useful — to put a recurring block on the calendar for the reorder decision.\n\nThis works far better as a rhythm than as a fire drill. Offer it once. On a no or on silence, drop it.\n\n## Fallback path\n\nA sales CSV plus a stock count is a fully supported input. Many businesses count on a clipboard, and that is legitimate data. Velocity, stockout dates, reorder sizing, the PO, and the vendor email all come out the same. The books entry becomes an import file.\n\n## What not to do\n\n- **Do not send a PO or a vendor email without approval.** One spends money, the other spends goodwill.\n- **Do not treat the buy-list approval as approval to send.** Two gates, two decisions.\n- **Do not reorder a zero-velocity item.**\n- **Do not size a reorder without subtracting what is already inbound.** Double-ordering a slow item buries cash for years.\n- **Do not invent a velocity, a lead time, or a stockout date.** Too little history is reported by SKU.\n- **Do not pay anything here.** POs are staged, not paid. Payment is `\u002Fpay-the-bills`.\n- **Do not report units without dollars.** The owner is deciding about cash, not pieces.\n\n## Output\n\n**Deliver the reorder plan per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `..\u002F..\u002Fshared\u002Fartifact-style.md`):\n\n- **Visual artifact (the default):** render the plan as an HTML page in the house style — total committed as the lead stat tile in dollars, each SKU a row with velocity, stockout date, and reorder size in tabular-nums, and a pill on anything already inbound. The PO documents and any import file ride along as working files, not second deliverables.\n- **docx \u002F md \u002F notion \u002F canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.\n- **Best for skill:** use the visual artifact — this output is a buy decision, not prose.\n\n## After the run\n\nThe POs are out and a coded record is waiting for the bills to match against. When those bills land, the natural next step is \"pay the bills\" — `\u002Fpay-the-bills` runs the match, the cash check, and the payment gate. Also nearby: \"cash forecast\" (`cash-flow-snapshot`) to see what the committed orders do to the next 60 days, and \"close the month\" (`\u002Fclose-month`) when the period ends. Offer at most three, and skip any offer the owner already declined this session.\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,"description":7,"allowed-tools":48},"Read, WebFetch","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","small-business\u002Fskills\u002Frestock",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill restock",{"tool":63,"command":64},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill restock",{"tool":66,"command":67},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill restock","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Frestock\u002FSKILL.md",true,[],[72,97,118,141,170,194],{"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,37,86,87,88,89,90,91,92,93,94,95,96,31],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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",[],[104,105,106,107,42,108,109,110,111,112,37,36,113,114,33,115,31,27,116,117],"tax season organizer","tax","us federal","which","paid","end","usd","only","now","xero","scanning","request","list","stripe",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"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",[],[125,105,126,127,106,128,129,42,130,131,132,133,134,135,136,109,137,138,139,140],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","for","trigger","material","question","paypal","business",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":152,"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",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[153,154,155,156,157,158,130,159,160,161,162,163,164,165,37,166,167,88,168,169],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者",[180,181,182,183,184,185,127,186,187,188,189,82,190,37,191,192,32,31,193,30],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","write",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"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",[],[201,202,203,128,204,135,136,205,84,206,112,140,207,208,209,210,211,191,212,92],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]