[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718VPGKP906BWTRTYGJMK5M":3,"skill-same:01M718VPGKP906BWTRTYGJMK5M":77},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M718VPGKP906BWTRTYGJMK5M","marketing-monday",null,"Delivers the weekly growth briefing as one merged read — whether the growth engine is working, what customers are saying in public and private, what competitors actually changed, and the three growth actions worth taking this week. The growth twin of the Monday brief, chaining growth-pulse and review-reputation and adding a web-native competitor scan, merged into a single page rather than three reports. Offers to run on a weekly cadence once, and sets it up on a yes. Use this whenever the owner wants a recurring or one-off growth check, including phrasings like \"how's marketing doing,\" \"growth check for the week,\" \"give me my Monday growth brief,\" \"what should I be doing about growth this week,\" \"are we winning or losing out there,\" or \"set up a weekly marketing update.\" Reach for it when the owner asks how the business is growing rather than how it is paying its bills.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35379,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fmarketing-monday\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"marketing","monday","marketing monday","me","when","competitor scan","weekly","briefing","native","cadence","monday brief","growth engine","review","reports","up","pulse","how","SET","brief","actions","2026-11-10 10:12:30",false,"---\nname: marketing-monday\ndescription: Delivers the weekly growth briefing as one merged read — whether the growth engine is working, what customers are saying in public and private, what competitors actually changed, and the three growth actions worth taking this week. The growth twin of the Monday brief, chaining growth-pulse and review-reputation and adding a web-native competitor scan, merged into a single page rather than three reports. Offers to run on a weekly cadence once, and sets it up on a yes. Use this whenever the owner wants a recurring or one-off growth check, including phrasings like \"how's marketing doing,\" \"growth check for the week,\" \"give me my Monday growth brief,\" \"what should I be doing about growth this week,\" \"are we winning or losing out there,\" or \"set up a weekly marketing update.\" Reach for it when the owner asks how the business is growing rather than how it is paying its bills.\nallowed-tools: Read, WebFetch\n---\n\nRun the weekly growth briefing by chaining two skills — `growth-pulse` for whether the engine is working and `review-reputation` for what customers are saying — then adding a web-native competitor scan. The three parts feed one merged brief; this is not three reports stapled together.\n\nConnectors: any one of PayPal, Shopify, or HubSpot is enough to run. Apollo, Clay, Mailchimp, Square, Stripe, and TikTok Ads each add a layer. TikTok Ads contributes the paid layer to Step 1 through growth-pulse: last week's spend, results, and cost per result beside the sales trend, reported as the platform's own claim next to the CRM's lead count, never blended (`..\u002Fgrowth-pulse\u002Freference\u002Fdata_sources.md`). Mailchimp contributes the email channel to Step 1 (its `get_capabilities` call needs `user_request` and a `category`; `..\u002F..\u002Fshared\u002Fconnector-call-shapes.md`) — campaign analytics with revenue attribution and audience-growth numbers. It is read-only in this brief: nothing is drafted or sent from here, and its attributed revenue is reported as the email channel's own claim beside the platform and CRM numbers, never blended into one figure. With none of them, CSV exports and pasted reviews go in, and the competitor scan runs web-native with no connector at all.\n\nDefault window: the last 7 days for the pulse, the last 90 days for reviews, and since the last run for the competitor watchlist.\n\n## Step 1 — Is the engine working (growth-pulse)\n\nTrigger the `growth-pulse` skill workflow. Pull every connector in one parallel batch; a serial run is a wait nobody sits through twice.\n\n**In:** whatever is connected, or exports. **Out:** channel trend, funnel conversion, campaign return, product performance, and sentiment — each with a status, and anything missing marked \"n\u002Fa\" rather than silently dropped.\n\n**Handoff:** carry forward the single sentence that explains the period, plus the biggest drop-off in the funnel and any product carrying the whole trend. Do not carry the full five-view dashboard into the merged brief.\n\n**No gate here.** The command was invoked; run it. Reading data is not an approval-worthy action.\n\n## Step 2 — What customers are saying (review-reputation)\n\nTrigger the `review-reputation` skill workflow.\n\n**In:** public reviews, PayPal disputes, HubSpot tickets, complaint-language email threads, and pasted or exported reviews when nothing reads them directly. **Out:** three to five themes with verbatim quotes, reviews needing a reply, and customers who have gone quiet.\n\n**Handoff:** carry forward the themes and the rating direction. Carry the drafted replies as a separate approval queue, not as brief content.\n\n**Gate:** nothing posts publicly without the owner reading it first, one review at a time. This gate survives the chain intact — a merged brief does not become blanket approval to reply on the owner's behalf.\n\nIf the quiet-customer list is worth working, point at `\u002Freactivate` rather than starting win-back drafts inside this brief.\n\n## Step 3 — What competitors did (web research)\n\nRun this leg inline — it needs no connector. Check the owner's saved watchlist of competitors (or ask for three or four names the first time, then save them) and scan public sources: their site and pricing pages, social and ad activity, job postings, and any press. Add HubSpot win-loss notes when HubSpot is connected.\n\n**Out:** what changed, with observed facts and inferences labeled separately and everything dated. Never present an inference as an observation.\n\n**Handoff:** carry forward only material changes. A quiet week is reported as a quiet week — three lines, no padding. That honesty is what makes the week something real happens land hard.\n\n**Gate:** nothing acts on the intel. A price move or a campaign is the owner's decision.\n\n## Step 4 — Merge into one brief\n\nThis is the step that makes the command worth having, so do not shortcut it.\n\nThe output is **one page**, not three sections handed over intact. Read the three inputs together and find where they explain each other. The connections that usually matter:\n\n- Sentiment sliding while revenue holds is the early warning that shows up in revenue two months out.\n- A competitor's price move against a product whose margin is already thin is a decision, not a note.\n- Falling win rate with strong lead volume, plus review complaints about response time, is one story told twice.\n- A quiet-customer list growing alongside a new competitor location is churn with a named cause.\n\nStructure:\n\n1. **Headline** — the one thing that matters this week, in a sentence\n2. **How growth performed** — the numbers, each with its comparison\n3. **What customers said** — themes with verbatim quotes\n4. **What changed around you** — competitor moves, observed and dated\n5. **Do these three things this week** — exactly three, ranked by size of impact\n\nEvery action needs what to do, the number from this brief that justifies it, and roughly what it is worth. Rank by impact, not by ease — Ray Okonkwo can judge what is easy; only the brief can tell him what is big.\n\nIf the honest answer is that nothing needs to change, say that. A brief that manufactures three actions every week trains the owner to ignore all of them.\n\n## Step 5 — Offer the cadence, once\n\nOffer to run this weekly. Ask once. On a yes, set the schedule and confirm the day and time. On a no or no answer, move on and do not ask again in the same run.\n\nEach scheduled run compares against the previous one and rolls the baseline forward, because change only means anything against a baseline.\n\n## Approval gates (must hold)\n\n- No public review response posts without per-review approval.\n- No win-back message sends from this command — that is `\u002Freactivate`.\n- No pricing or campaign action is taken on competitor intel. Recommend and stop.\n- The cadence is set only on an explicit yes.\n- If a connector fails, name it in the sources line and continue. A named gap is information; a silent one looks like good news.\n\n## What not to do\n\n- **Do not staple three reports together.** One merged brief with three actions at the end is the deliverable. If the output reads as a growth section, then a review section, then a competitor section with no connective sentence between them, it failed.\n- **Do not pad a quiet week.** \"Nothing material changed\" protects the credibility of the week something did.\n- **Do not invent attribution or a competitor move.** Both get repeated to other people.\n- **Do not report CRM forecast value as revenue.** Deal values are hopes; invoices are facts.\n- **Do not ask about the schedule more than once.**\n- **Do not exceed three actions.** Four is a to-do list nobody works.\n- **Do not read expenses or margin from the QuickBooks P&L summary.** Its `totalExpenses` can be zero against real rows; total the rows or `monthlyBreakdown` (`..\u002F..\u002Fshared\u002Fquickbooks-report-traps.md`, Trap 2).\n\n## Output\n\nOne page in chat, with the three actions last. Offer once to save it as a file or post it to Slack, then stop asking.\n\nAlso deliver the merged brief 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 brief as an HTML page in the house style. One page, mirroring the merge: growth stat tiles for the headline numbers, a sentiment-themes panel with verbatim quotes, the competitor-changes list dated and labeled observed vs. inferred, and a three-actions panel last. The chat summary stays — the artifact is additive, never the only copy.\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 — a weekly brief is scanned, not filed.\n\n## Closing offer\n\nEnd with one line on what was delivered — the week's headline and the three actions. Then offer the single most relevant next step with its exact trigger phrase, usually \"win back quiet customers\" (`\u002Freactivate`) when the quiet-customer list is worth working. Offer at most two others drawn from the router's table, such as \"what should I promote?\" (`content-strategy`) or \"who should I call?\" (`lead-triage`). Three offers maximum, and never re-offer something 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","Run the weekly growth briefing by chaining two skills — `growth-pulse` for whether the engine is working and `review-reputation` for what customers are saying — then adding a web-native competitor scan. The three parts feed one merged brief; this is not three reports stapled together.\n\nConnectors: any one of PayPal, Shopify, or HubSpot is enough to run. Apollo, Clay, Mailchimp, Square, Stripe, and TikTok Ads each add a layer. TikTok Ads contributes the paid layer to Step 1 through growth-pulse: last week's spend, results, and cost per result beside the sales trend, reported as the platform's own claim next to the CRM's lead count, never blended (`..\u002Fgrowth-pulse\u002Freference\u002Fdata_sources.md`). Mailchimp contributes the email channel to Step 1 (its `get_capabilities` call needs `user_request` and a `category`; `..\u002F..\u002Fshared\u002Fconnector-call-shapes.md`) — campaign analytics with revenue attribution and audience-growth numbers. It is read-only in this brief: nothing is drafted or sent from here, and its attributed revenue is reported as the email channel's own claim beside the platform and CRM numbers, never blended into one figure. With none of them, CSV exports and pasted reviews go in, and the competitor scan runs web-native with no connector at all.\n\nDefault window: the last 7 days for the pulse, the last 90 days for reviews, and since the last run for the competitor watchlist.\n\n## Step 1 — Is the engine working (growth-pulse)\n\nTrigger the `growth-pulse` skill workflow. Pull every connector in one parallel batch; a serial run is a wait nobody sits through twice.\n\n**In:** whatever is connected, or exports. **Out:** channel trend, funnel conversion, campaign return, product performance, and sentiment — each with a status, and anything missing marked \"n\u002Fa\" rather than silently dropped.\n\n**Handoff:** carry forward the single sentence that explains the period, plus the biggest drop-off in the funnel and any product carrying the whole trend. Do not carry the full five-view dashboard into the merged brief.\n\n**No gate here.** The command was invoked; run it. Reading data is not an approval-worthy action.\n\n## Step 2 — What customers are saying (review-reputation)\n\nTrigger the `review-reputation` skill workflow.\n\n**In:** public reviews, PayPal disputes, HubSpot tickets, complaint-language email threads, and pasted or exported reviews when nothing reads them directly. **Out:** three to five themes with verbatim quotes, reviews needing a reply, and customers who have gone quiet.\n\n**Handoff:** carry forward the themes and the rating direction. Carry the drafted replies as a separate approval queue, not as brief content.\n\n**Gate:** nothing posts publicly without the owner reading it first, one review at a time. This gate survives the chain intact — a merged brief does not become blanket approval to reply on the owner's behalf.\n\nIf the quiet-customer list is worth working, point at `\u002Freactivate` rather than starting win-back drafts inside this brief.\n\n## Step 3 — What competitors did (web research)\n\nRun this leg inline — it needs no connector. Check the owner's saved watchlist of competitors (or ask for three or four names the first time, then save them) and scan public sources: their site and pricing pages, social and ad activity, job postings, and any press. Add HubSpot win-loss notes when HubSpot is connected.\n\n**Out:** what changed, with observed facts and inferences labeled separately and everything dated. Never present an inference as an observation.\n\n**Handoff:** carry forward only material changes. A quiet week is reported as a quiet week — three lines, no padding. That honesty is what makes the week something real happens land hard.\n\n**Gate:** nothing acts on the intel. A price move or a campaign is the owner's decision.\n\n## Step 4 — Merge into one brief\n\nThis is the step that makes the command worth having, so do not shortcut it.\n\nThe output is **one page**, not three sections handed over intact. Read the three inputs together and find where they explain each other. The connections that usually matter:\n\n- Sentiment sliding while revenue holds is the early warning that shows up in revenue two months out.\n- A competitor's price move against a product whose margin is already thin is a decision, not a note.\n- Falling win rate with strong lead volume, plus review complaints about response time, is one story told twice.\n- A quiet-customer list growing alongside a new competitor location is churn with a named cause.\n\nStructure:\n\n1. **Headline** — the one thing that matters this week, in a sentence\n2. **How growth performed** — the numbers, each with its comparison\n3. **What customers said** — themes with verbatim quotes\n4. **What changed around you** — competitor moves, observed and dated\n5. **Do these three things this week** — exactly three, ranked by size of impact\n\nEvery action needs what to do, the number from this brief that justifies it, and roughly what it is worth. Rank by impact, not by ease — Ray Okonkwo can judge what is easy; only the brief can tell him what is big.\n\nIf the honest answer is that nothing needs to change, say that. A brief that manufactures three actions every week trains the owner to ignore all of them.\n\n## Step 5 — Offer the cadence, once\n\nOffer to run this weekly. Ask once. On a yes, set the schedule and confirm the day and time. On a no or no answer, move on and do not ask again in the same run.\n\nEach scheduled run compares against the previous one and rolls the baseline forward, because change only means anything against a baseline.\n\n## Approval gates (must hold)\n\n- No public review response posts without per-review approval.\n- No win-back message sends from this command — that is `\u002Freactivate`.\n- No pricing or campaign action is taken on competitor intel. Recommend and stop.\n- The cadence is set only on an explicit yes.\n- If a connector fails, name it in the sources line and continue. A named gap is information; a silent one looks like good news.\n\n## What not to do\n\n- **Do not staple three reports together.** One merged brief with three actions at the end is the deliverable. If the output reads as a growth section, then a review section, then a competitor section with no connective sentence between them, it failed.\n- **Do not pad a quiet week.** \"Nothing material changed\" protects the credibility of the week something did.\n- **Do not invent attribution or a competitor move.** Both get repeated to other people.\n- **Do not report CRM forecast value as revenue.** Deal values are hopes; invoices are facts.\n- **Do not ask about the schedule more than once.**\n- **Do not exceed three actions.** Four is a to-do list nobody works.\n- **Do not read expenses or margin from the QuickBooks P&L summary.** Its `totalExpenses` can be zero against real rows; total the rows or `monthlyBreakdown` (`..\u002F..\u002Fshared\u002Fquickbooks-report-traps.md`, Trap 2).\n\n## Output\n\nOne page in chat, with the three actions last. Offer once to save it as a file or post it to Slack, then stop asking.\n\nAlso deliver the merged brief 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 brief as an HTML page in the house style. One page, mirroring the merge: growth stat tiles for the headline numbers, a sentiment-themes panel with verbatim quotes, the competitor-changes list dated and labeled observed vs. inferred, and a three-actions panel last. The chat summary stays — the artifact is additive, never the only copy.\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 — a weekly brief is scanned, not filed.\n\n## Closing offer\n\nEnd with one line on what was delivered — the week's headline and the three actions. Then offer the single most relevant next step with its exact trigger phrase, usually \"win back quiet customers\" (`\u002Freactivate`) when the quiet-customer list is worth working. Offer at most two others drawn from the router's table, such as \"what should I promote?\" (`content-strategy`) or \"who should I call?\" (`lead-triage`). Three offers maximum, and never re-offer something 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":54},"Read, WebFetch","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","small-business\u002Fskills\u002Fmarketing-monday",3918,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-11 11:16:59",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill marketing-monday",{"tool":69,"command":70},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill marketing-monday",{"tool":72,"command":73},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill marketing-monday","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fmarketing-monday\u002FSKILL.md",true,[],[78,103,128,150,177,201],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":49},"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",[],[85,86,87,43,88,89,90,33,91,92,93,94,95,96,97,98,99,100,101,102],"ticket","ticket deflector","mode","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":49},"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",[],[110,111,112,113,114,115,116,117,118,119,33,120,121,122,123,124,102,125,126,127],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":49},"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",[],[135,111,136,46,112,137,138,114,139,140,141,142,143,144,145,116,146,147,148,149],"tax prep","prep","as","ready","never","zoho books","get","chain","profit","for","trigger","material","question","paypal","business",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":49},"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",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",[160,161,162,163,164,165,139,166,167,168,169,170,171,172,33,173,174,93,175,176],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":186,"publishedAt":49},"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",[183],{"categoryNo":184,"categoryName":185,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[187,188,189,190,191,192,46,47,193,194,195,43,196,33,32,197,198,102,199,200],"social","social content engine","engine","content engine","social content","content","posts","Captions","prices","campaign","product","calendar","write","drafts",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":49},"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",[],[208,209,210,137,211,144,145,212,89,213,119,149,214,215,216,217,218,32,219,97],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]