[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718V4AHWD7BRVRNNS1KAV8R":3,"skill-same:01M718V4AHWD7BRVRNNS1KAV8R":90},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M718V4AHWD7BRVRNNS1KAV8R","inventory-planner",null,"Works out what to reorder and when, from what is actually selling: pulls sales history and stock on hand from Shopify, Square, NetSuite, or an uploaded CSV, computes 7-day and 28-day sales velocity per item, projects a conservative stockout date for each, sizes a 60-day reorder quantity, and drafts the purchase orders and vendor emails to cover it. Flags the money sitting still too — overstock, dead stock, and zero-velocity items, reported as slow movers to clear rather than things to buy more of. Seasonality is applied where the history supports it and named where it does not. Nothing is ordered and no vendor is emailed without approval. Reach for this whenever stock comes up — \"what do I need to reorder,\" \"am I going to run out,\" \"what should I order this month,\" \"we keep running out of filters,\" \"how much cash is sitting in the warehouse,\" \"what is not moving,\" or \"draft a PO for my supplier.\"","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35563,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"inventory planner","planner","inventory","my","cover","flags","square","drafts","read","run","how","velocity","hand","when","filters","up","purchase","stock","netsuite","projects","2026-11-10 10:12:30",false,"---\nname: inventory-planner\ndescription: >\n  Works out what to reorder and when, from what is actually selling: pulls\n  sales history and stock on hand from Shopify, Square, NetSuite, or an\n  uploaded CSV, computes 7-day and 28-day sales velocity per item, projects a\n  conservative stockout date for each, sizes a 60-day reorder quantity, and\n  drafts the purchase orders and vendor emails to cover it. Flags the money\n  sitting still too — overstock, dead stock, and zero-velocity items, reported\n  as slow movers to clear rather than things to buy more of. Seasonality is\n  applied where the history supports it and named where it does not. Nothing\n  is ordered and no vendor is emailed without approval. Reach for this\n  whenever stock comes up — \"what do I need to reorder,\" \"am I going to run\n  out,\" \"what should I order this month,\" \"we keep running out of filters,\"\n  \"how much cash is sitting in the warehouse,\" \"what is not moving,\" or \"draft\n  a PO for my supplier.\"\nallowed-tools: Read, WebFetch\n---\n\n# Inventory Planner\n\nBuy what sells, before it runs out, and stop buying what doesn't.\n\nStock is cash the owner already spent. Two things go wrong: running out of the item customers came for, and sitting on a pallet of something nobody wants. Both are visible in the sales history well before they become a problem, which is what this skill reads for.\n\n## Step 1 — Get sales and stock\n\n**Preferred:** Shopify for sales and inventory levels. Square and NetSuite work the same way.\n\n**Fallback, fully supported:** a CSV of sales history plus a stock-on-hand count. Two files, or one with both. This path works with zero connectors and gives the same output. Many businesses count on a clipboard, and that is a legitimate input.\n\nYou need, per item: SKU, name, units sold by date, current stock on hand, unit cost, unit price, vendor, and lead time if known. Missing lead time is asked for once and remembered — see `reference\u002Fdata_sources.md`.\n\n**Say what the count is as of.** A stock figure two weeks old produces a stockout date two weeks wrong.\n\n## Step 2 — Compute velocity, both windows\n\nFor every item, compute:\n\n- **7-day velocity** — units per day over the last week. Catches what is happening now.\n- **28-day velocity** — units per day over four weeks. The stable baseline.\n\nBoth matter, and disagreement between them is information. An item selling three times its 28-day rate this week is either trending or had one bulk order, and those need different responses. `reference\u002Fvelocity_and_reorder.md` covers how to tell them apart.\n\nExclude one-off distortions from the baseline where you can identify them: a single wholesale order, a returned batch, a stockout period where the item could not sell. **A period of zero sales because there was no stock is not zero demand**, and treating it as such is how an item gets under-ordered forever.\n\n## Step 3 — Project stockout dates, conservatively\n\nStockout date is stock on hand divided by the daily velocity you trust least — the higher of the two windows. Being early is cheap; being late loses the sale.\n\nThen compare against lead time. The number that matters is not when it runs out, it is whether there is still time to order:\n\n- **Past the point of no return** — lead time exceeds days of cover. Already going to stock out. Say so plainly.\n- **Order now** — cover is within lead time plus a safety buffer.\n- **Order soon** — comfortable, but on the next cycle.\n- **Fine** — no action.\n\n**Never state a stockout date for an item with no reliable velocity.** New items with two weeks of history and items whose sales were interrupted get flagged as \"not enough history,\" by name.\n\n## Step 4 — Size the reorder\n\nDefault target is **60 days of cover plus the lead time**, sized on the **28-day rate** — not on the faster of the two. The stock has to last from the day it lands until the next order lands, so leaving the lead time out runs the item short by exactly that many days every cycle. Then adjust for pack size, minimum order quantity, and what is already on order.\n\nThe two rates do different jobs and both get named on the line: the higher one says when it runs out, the 28-day one says how much to buy. Sizing a 60-day order off a one-week spike is how cash ends up in a pallet.\n\nNever size a reorder without subtracting inbound stock. Double-ordering a slow item is how a business ends up with three years of it.\n\nRound to the vendor's pack size and say which direction you rounded. Show the dollar cost of every recommendation — the owner is deciding about cash, not units.\n\n## Step 5 — Handle the items that are not moving\n\nZero-velocity and very slow items are a separate list with a separate purpose. **They are never reorder candidates.**\n\n- **Zero velocity** — no units in 28 days. Report as a slow mover with the cash tied up in it. **Never compute days of cover for these** — nothing is selling, so nothing is running out, and the number is either an error or nonsense. The one exception is an item inside a season the owner has named, which goes on a dated watch list instead of the clear-out list.\n- **Overstock** — more than 120 days of cover. Report the excess units and the dollars.\n- **Dead stock** — no movement in 90 days. Suggest clearing, bundling, or discounting.\n\nTotal the cash sitting in these. That figure is usually the most surprising number in the whole report and often the most useful one.\n\n## Step 6 — Apply seasonality only where history supports it\n\nWith at least a year of history, compare the coming period against the same period last year and adjust.\n\n**With less than a year, say so and do not adjust.** A seasonal multiplier invented from nine months of data is a guess wearing a suit. Ask the owner instead — they know their season better than a short history does. `reference\u002Fseasonality.md` covers both paths.\n\n## Step 7 — Present the buy list\n\nLead with the total dollar amount and the count of items about to stock out. Then: order now, order soon, slow movers, and anything with too little history to judge.\n\nEvery line carries the numbers behind it — velocity, days of cover, lead time, quantity, cost. An owner who can see the reasoning approves in a minute; one who cannot rebuilds the whole thing by hand.\n\nRender the buy list as an HTML artifact using the house artifact style (`..\u002F..\u002Fshared\u002Fartifact-style.md`): a stockout table sorted by stockout date with mono tabular-nums numerals, urgency status pills (order now \u002F order soon \u002F fine \u002F past the point of no return), a reorder panel with quantities and dollar totals, and a slow-movers section with the cash tied up in it. The chat summary stays — the artifact is the full picture, not the only one.\n\n## Step 8 — Draft POs and vendor emails, with approval\n\nPurchase orders commit money and vendor emails go out under the owner's name, so both wait for an explicit yes.\n\nState the vendor, the line items, and the total before asking. Draft the vendor email in the owner's voice per [the shared voice profile](..\u002F..\u002Fshared\u002Fvoice-profile.md). **If no profile exists yet, follow that file's \"When there is no sample\" instruction** — ask for three emails they have already sent a supplier. If they would rather not, write the email plain and neutral and say it is not in their voice. Never invent a personality for someone's vendor relationship.\n\nWith Google Calendar connected, offer a recurring block for the restock decision — this works far better as a rhythm than as a fire drill. Keep the approved PO document here — this skill owns it. With QuickBooks or NetSuite connected, hand `ap-processor` the coded memo for each one (vendor, PO number, total, expected date, and the account, class, and job), so the bill three-way-matches against a real record when it arrives. `ap-processor` reads POs; it does not create them.\n\n## Closing offer\n\nClose with one line on what was decided — the total buy and the items about to run out. Then offer the most relevant next step with its exact trigger phrase: \"reorder\" (`\u002Frestock`) when the owner wants the POs drafted and sent end to end. Up to two more from the router's table, such as \"cash forecast\" (`cash-flow-snapshot`) or \"pay the bills\" (`\u002Fpay-the-bills`). Three offers at most, and never repeat one the owner already declined this session.\n\n## What not to do\n\n- **Do not invent a velocity, a lead time, or a stockout date.** Too little history is reported by SKU, not smoothed over.\n- **Do not treat an out-of-stock period as zero demand.** It is suppressed demand and it biases everything downstream.\n- **Do not recommend reordering a zero-velocity item.** No sales means stop buying, not buy more.\n- **Do not size a reorder without subtracting what is already inbound.**\n- **Do not apply seasonality without a year of history.** Ask the owner instead.\n- **Do not send a PO or a vendor email without approval.** Both spend money or spend goodwill.\n- **Do not report units without dollars.** The owner thinks in cash.\n\n## Reference files\n\n- `reference\u002Fdata_sources.md` — Shopify, Square, NetSuite, and the CSV path, with required fields\n- `reference\u002Fvelocity_and_reorder.md` — the 7\u002F28-day math, distortion handling, and reorder sizing\n- `reference\u002Fseasonality.md` — when to adjust, when to ask, and how to say which you did\n- `reference\u002Fpo_drafting.md` — purchase order structure and vendor email drafting\n- `reference\u002Fgotchas.md` — the mistakes that stock out a bestseller or bury cash in a pallet\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","# Inventory Planner\n\nBuy what sells, before it runs out, and stop buying what doesn't.\n\nStock is cash the owner already spent. Two things go wrong: running out of the item customers came for, and sitting on a pallet of something nobody wants. Both are visible in the sales history well before they become a problem, which is what this skill reads for.\n\n## Step 1 — Get sales and stock\n\n**Preferred:** Shopify for sales and inventory levels. Square and NetSuite work the same way.\n\n**Fallback, fully supported:** a CSV of sales history plus a stock-on-hand count. Two files, or one with both. This path works with zero connectors and gives the same output. Many businesses count on a clipboard, and that is a legitimate input.\n\nYou need, per item: SKU, name, units sold by date, current stock on hand, unit cost, unit price, vendor, and lead time if known. Missing lead time is asked for once and remembered — see `reference\u002Fdata_sources.md`.\n\n**Say what the count is as of.** A stock figure two weeks old produces a stockout date two weeks wrong.\n\n## Step 2 — Compute velocity, both windows\n\nFor every item, compute:\n\n- **7-day velocity** — units per day over the last week. Catches what is happening now.\n- **28-day velocity** — units per day over four weeks. The stable baseline.\n\nBoth matter, and disagreement between them is information. An item selling three times its 28-day rate this week is either trending or had one bulk order, and those need different responses. `reference\u002Fvelocity_and_reorder.md` covers how to tell them apart.\n\nExclude one-off distortions from the baseline where you can identify them: a single wholesale order, a returned batch, a stockout period where the item could not sell. **A period of zero sales because there was no stock is not zero demand**, and treating it as such is how an item gets under-ordered forever.\n\n## Step 3 — Project stockout dates, conservatively\n\nStockout date is stock on hand divided by the daily velocity you trust least — the higher of the two windows. Being early is cheap; being late loses the sale.\n\nThen compare against lead time. The number that matters is not when it runs out, it is whether there is still time to order:\n\n- **Past the point of no return** — lead time exceeds days of cover. Already going to stock out. Say so plainly.\n- **Order now** — cover is within lead time plus a safety buffer.\n- **Order soon** — comfortable, but on the next cycle.\n- **Fine** — no action.\n\n**Never state a stockout date for an item with no reliable velocity.** New items with two weeks of history and items whose sales were interrupted get flagged as \"not enough history,\" by name.\n\n## Step 4 — Size the reorder\n\nDefault target is **60 days of cover plus the lead time**, sized on the **28-day rate** — not on the faster of the two. The stock has to last from the day it lands until the next order lands, so leaving the lead time out runs the item short by exactly that many days every cycle. Then adjust for pack size, minimum order quantity, and what is already on order.\n\nThe two rates do different jobs and both get named on the line: the higher one says when it runs out, the 28-day one says how much to buy. Sizing a 60-day order off a one-week spike is how cash ends up in a pallet.\n\nNever size a reorder without subtracting inbound stock. Double-ordering a slow item is how a business ends up with three years of it.\n\nRound to the vendor's pack size and say which direction you rounded. Show the dollar cost of every recommendation — the owner is deciding about cash, not units.\n\n## Step 5 — Handle the items that are not moving\n\nZero-velocity and very slow items are a separate list with a separate purpose. **They are never reorder candidates.**\n\n- **Zero velocity** — no units in 28 days. Report as a slow mover with the cash tied up in it. **Never compute days of cover for these** — nothing is selling, so nothing is running out, and the number is either an error or nonsense. The one exception is an item inside a season the owner has named, which goes on a dated watch list instead of the clear-out list.\n- **Overstock** — more than 120 days of cover. Report the excess units and the dollars.\n- **Dead stock** — no movement in 90 days. Suggest clearing, bundling, or discounting.\n\nTotal the cash sitting in these. That figure is usually the most surprising number in the whole report and often the most useful one.\n\n## Step 6 — Apply seasonality only where history supports it\n\nWith at least a year of history, compare the coming period against the same period last year and adjust.\n\n**With less than a year, say so and do not adjust.** A seasonal multiplier invented from nine months of data is a guess wearing a suit. Ask the owner instead — they know their season better than a short history does. `reference\u002Fseasonality.md` covers both paths.\n\n## Step 7 — Present the buy list\n\nLead with the total dollar amount and the count of items about to stock out. Then: order now, order soon, slow movers, and anything with too little history to judge.\n\nEvery line carries the numbers behind it — velocity, days of cover, lead time, quantity, cost. An owner who can see the reasoning approves in a minute; one who cannot rebuilds the whole thing by hand.\n\nRender the buy list as an HTML artifact using the house artifact style (`..\u002F..\u002Fshared\u002Fartifact-style.md`): a stockout table sorted by stockout date with mono tabular-nums numerals, urgency status pills (order now \u002F order soon \u002F fine \u002F past the point of no return), a reorder panel with quantities and dollar totals, and a slow-movers section with the cash tied up in it. The chat summary stays — the artifact is the full picture, not the only one.\n\n## Step 8 — Draft POs and vendor emails, with approval\n\nPurchase orders commit money and vendor emails go out under the owner's name, so both wait for an explicit yes.\n\nState the vendor, the line items, and the total before asking. Draft the vendor email in the owner's voice per [the shared voice profile](..\u002F..\u002Fshared\u002Fvoice-profile.md). **If no profile exists yet, follow that file's \"When there is no sample\" instruction** — ask for three emails they have already sent a supplier. If they would rather not, write the email plain and neutral and say it is not in their voice. Never invent a personality for someone's vendor relationship.\n\nWith Google Calendar connected, offer a recurring block for the restock decision — this works far better as a rhythm than as a fire drill. Keep the approved PO document here — this skill owns it. With QuickBooks or NetSuite connected, hand `ap-processor` the coded memo for each one (vendor, PO number, total, expected date, and the account, class, and job), so the bill three-way-matches against a real record when it arrives. `ap-processor` reads POs; it does not create them.\n\n## Closing offer\n\nClose with one line on what was decided — the total buy and the items about to run out. Then offer the most relevant next step with its exact trigger phrase: \"reorder\" (`\u002Frestock`) when the owner wants the POs drafted and sent end to end. Up to two more from the router's table, such as \"cash forecast\" (`cash-flow-snapshot`) or \"pay the bills\" (`\u002Fpay-the-bills`). Three offers at most, and never repeat one the owner already declined this session.\n\n## What not to do\n\n- **Do not invent a velocity, a lead time, or a stockout date.** Too little history is reported by SKU, not smoothed over.\n- **Do not treat an out-of-stock period as zero demand.** It is suppressed demand and it biases everything downstream.\n- **Do not recommend reordering a zero-velocity item.** No sales means stop buying, not buy more.\n- **Do not size a reorder without subtracting what is already inbound.**\n- **Do not apply seasonality without a year of history.** Ask the owner instead.\n- **Do not send a PO or a vendor email without approval.** Both spend money or spend goodwill.\n- **Do not report units without dollars.** The owner thinks in cash.\n\n## Reference files\n\n- `reference\u002Fdata_sources.md` — Shopify, Square, NetSuite, and the CSV path, with required fields\n- `reference\u002Fvelocity_and_reorder.md` — the 7\u002F28-day math, distortion handling, and reorder sizing\n- `reference\u002Fseasonality.md` — when to adjust, when to ask, and how to say which you did\n- `reference\u002Fpo_drafting.md` — purchase order structure and vendor email drafting\n- `reference\u002Fgotchas.md` — the mistakes that stock out a bestseller or bury cash in a pallet\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":44,"allowed-tools":45},"Works out what to reorder and when, from what is actually selling: pulls sales history and stock on hand from Shopify, Square, NetSuite, or an uploaded CSV, computes 7-day and 28-day sales velocity per item, projects a conservative stockout date for each, sizes a 60-day reorder quantity, and drafts the purchase orders and vendor emails to cover it. Flags the money sitting still too — overstock, dead stock, and zero-velocity items, reported as slow movers to clear rather than things to buy more of. Seasonality is applied where the history supports it and named where it does not. Nothing is ordered and no vendor is emailed without approval. Reach for this whenever stock comes up — \"what do I need to reorder,\" \"am I going to run out,\" \"what should I order this month,\" \"we keep running out of filters,\" \"how much cash is sitting in the warehouse,\" \"what is not moving,\" or \"draft a PO for my supplier.\"\n","Read, WebFetch","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","small-business\u002Fskills\u002Finventory-planner",3935,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-13 04:18:26",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill inventory-planner",{"tool":60,"command":61},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill inventory-planner",{"tool":63,"command":64},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill inventory-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002FSKILL.md",true,[68,74,78,82,86],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"reference\u002Fdata_sources.md","REFERENCE","参考文档",4388,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002Freference\u002Fdata_sources.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"reference\u002Fgotchas.md",4550,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002Freference\u002Fgotchas.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"reference\u002Fpo_drafting.md",3939,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002Freference\u002Fpo_drafting.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"reference\u002Fseasonality.md",5414,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002Freference\u002Fseasonality.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"reference\u002Fvelocity_and_reorder.md",8606,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Finventory-planner\u002Freference\u002Fvelocity_and_reorder.md",[91,115,137,160,189,214],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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",[],[98,99,100,34,101,102,103,32,104,105,106,107,108,109,110,111,112,113,114,27],"ticket","ticket deflector","mode","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[122,123,124,125,37,126,127,128,129,130,32,131,132,133,28,134,27,24,135,136],"tax season organizer","tax","us federal","which","paid","end","usd","only","now","books","xero","scanning","request","list","stripe",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"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",[],[144,123,145,146,124,147,148,37,149,150,151,152,153,154,155,127,156,157,158,159],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","for","trigger","material","question","paypal","business",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":171,"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",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[172,173,174,175,176,177,149,178,179,180,181,182,183,184,32,185,186,106,187,188],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":198,"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",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000036","内容创作者",[199,200,201,202,203,204,146,205,206,207,208,34,209,32,210,211,212,27,213,26],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"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",[],[221,222,223,147,224,154,155,225,102,226,130,159,227,228,229,230,231,210,232,110],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]