[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718G5EKMAZQ25P2YCBW23MY":3,"skill-same:01M718G5EKMAZQ25P2YCBW23MY":59},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M718G5EKMAZQ25P2YCBW23MY","slack-messaging",null,"Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35660,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fpartner-built\u002Fslack\u002Fskills\u002Fslack-messaging\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"messaging","slack","slack messaging","for","messages","guidance","syntax","slack messages","2026-11-10 10:12:30",false,"---\nname: slack-messaging\ndescription: Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax\n---\n\n# Slack Messaging Best Practices\n\nThis skill provides guidance for composing well-formatted, effective Slack messages.\n\n## When to Use\n\nApply this skill whenever composing, drafting, or helping the user write a Slack message — including when using `slack_send_message`, `slack_send_message_draft`, or `slack_create_canvas`.\n\n## Slack Formatting (mrkdwn)\n\nSlack uses its own markup syntax called **mrkdwn**, which differs from standard Markdown. Always use mrkdwn when composing Slack messages:\n\n| Format | Syntax | Notes |\n|--------|--------|-------|\n| Bold | `*text*` | Single asterisks, NOT double |\n| Italic | `_text_` | Underscores |\n| Strikethrough | `~text~` | Tildes |\n| Code (inline) | `` `code` `` | Backticks |\n| Code block | `` ```code``` `` | Triple backticks |\n| Quote | `> text` | Angle bracket |\n| Link | `\u003Curl\\|display text>` | Pipe-separated in angle brackets |\n| User mention | `\u003C@U123456>` | User ID in angle brackets |\n| Channel mention | `\u003C#C123456>` | Channel ID in angle brackets |\n| Bulleted list | `- item` or `• item` | Dash or bullet character |\n| Numbered list | `1. item` | Number followed by period |\n\n### Common Mistakes to Avoid\n\n- Do NOT use `**bold**` (double asterisks) — Slack uses `*bold*` (single asterisks)\n- Do NOT use `## headers` — Slack does not support Markdown headers. Use `*bold text*` on its own line instead.\n- Do NOT use `[text](url)` for links — Slack uses `\u003Curl|text>` format\n- Do NOT use `---` for horizontal rules — Slack does not render these\n\n## Message Structure Guidelines\n\n- **Lead with the point.** Put the most important information in the first line. Many people read Slack on mobile or in notifications where only the first line shows.\n- **Keep it short.** Aim for 1-3 short paragraphs. If the message is long, consider using a Canvas instead.\n- **Use line breaks generously.** Walls of text are hard to read. Separate distinct thoughts with blank lines.\n- **Use bullet points for lists.** Anything with 3+ items should be a list, not a run-on sentence.\n- **Bold key information.** Use `*bold*` for names, dates, deadlines, and action items so they stand out when scanning.\n\n## Thread vs. Channel Etiquette\n\n- **Reply in threads** when responding to a specific message to keep the main channel clean.\n- **Use `reply_broadcast`** (also post to channel) only when the reply contains information everyone needs to see.\n- **Post in the channel** (not a thread) when starting a new topic, making an announcement, or asking a question to the whole group.\n- **Don't start a new thread** to continue an existing conversation — find and reply to the original message.\n\n## Tone and Audience\n\n- Match the tone to the channel — `#general` is usually more formal than `#random`.\n- Use emoji reactions instead of reply messages for simple acknowledgments (though note: the MCP tools can't add reactions, so suggest the user do this manually if appropriate).\n- When writing announcements, use a clear structure: context, key info, call to action.\n","# Slack Messaging Best Practices\n\nThis skill provides guidance for composing well-formatted, effective Slack messages.\n\n## When to Use\n\nApply this skill whenever composing, drafting, or helping the user write a Slack message — including when using `slack_send_message`, `slack_send_message_draft`, or `slack_create_canvas`.\n\n## Slack Formatting (mrkdwn)\n\nSlack uses its own markup syntax called **mrkdwn**, which differs from standard Markdown. Always use mrkdwn when composing Slack messages:\n\n| Format | Syntax | Notes |\n|--------|--------|-------|\n| Bold | `*text*` | Single asterisks, NOT double |\n| Italic | `_text_` | Underscores |\n| Strikethrough | `~text~` | Tildes |\n| Code (inline) | `` `code` `` | Backticks |\n| Code block | `` ```code``` `` | Triple backticks |\n| Quote | `> text` | Angle bracket |\n| Link | `\u003Curl\\|display text>` | Pipe-separated in angle brackets |\n| User mention | `\u003C@U123456>` | User ID in angle brackets |\n| Channel mention | `\u003C#C123456>` | Channel ID in angle brackets |\n| Bulleted list | `- item` or `• item` | Dash or bullet character |\n| Numbered list | `1. item` | Number followed by period |\n\n### Common Mistakes to Avoid\n\n- Do NOT use `**bold**` (double asterisks) — Slack uses `*bold*` (single asterisks)\n- Do NOT use `## headers` — Slack does not support Markdown headers. Use `*bold text*` on its own line instead.\n- Do NOT use `[text](url)` for links — Slack uses `\u003Curl|text>` format\n- Do NOT use `---` for horizontal rules — Slack does not render these\n\n## Message Structure Guidelines\n\n- **Lead with the point.** Put the most important information in the first line. Many people read Slack on mobile or in notifications where only the first line shows.\n- **Keep it short.** Aim for 1-3 short paragraphs. If the message is long, consider using a Canvas instead.\n- **Use line breaks generously.** Walls of text are hard to read. Separate distinct thoughts with blank lines.\n- **Use bullet points for lists.** Anything with 3+ items should be a list, not a run-on sentence.\n- **Bold key information.** Use `*bold*` for names, dates, deadlines, and action items so they stand out when scanning.\n\n## Thread vs. Channel Etiquette\n\n- **Reply in threads** when responding to a specific message to keep the main channel clean.\n- **Use `reply_broadcast`** (also post to channel) only when the reply contains information everyone needs to see.\n- **Post in the channel** (not a thread) when starting a new topic, making an announcement, or asking a question to the whole group.\n- **Don't start a new thread** to continue an existing conversation — find and reply to the original message.\n\n## Tone and Audience\n\n- Match the tone to the channel — `#general` is usually more formal than `#random`.\n- Use emoji reactions instead of reply messages for simple acknowledgments (though note: the MCP tools can't add reactions, so suggest the user do this manually if appropriate).\n- When writing announcements, use a clear structure: context, key info, call to action.\n",{"name":5,"description":7},"main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","partner-built\u002Fslack\u002Fskills\u002Fslack-messaging",3944,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 06:21:52",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill slack-messaging",{"tool":51,"command":52},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill slack-messaging",{"tool":54,"command":55},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill slack-messaging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fpartner-built\u002Fslack\u002Fskills\u002Fslack-messaging\u002FSKILL.md",true,[],[60,87,112,134,163,189],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":32},"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",[],[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"ticket","ticket deflector","mode","up","payments","open","writing","when","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":32},"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",[],[94,95,96,97,98,99,100,101,102,103,74,104,105,106,107,108,86,109,110,111],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":32},"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",[],[119,95,120,121,96,122,123,98,124,125,126,127,128,27,129,100,130,131,132,133],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":145,"publishedAt":32},"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",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[146,147,148,149,150,151,124,152,153,154,155,156,157,158,74,159,160,77,161,162],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":32},"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",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000036","内容创作者",[173,174,175,176,177,178,121,179,180,181,182,70,183,74,184,185,186,86,187,188],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"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":195,"publishedAt":32},"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",[],[196,197,198,122,199,27,129,200,72,201,103,133,202,203,204,205,206,184,207,81],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]