[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718ED4Z6NT6HM19NRJ13M4P":3,"skill-same:01M718ED4Z6NT6HM19NRJ13M4P":86},{"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":37,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":6,"updatedAt":71,"install":72,"resources":85},"01M718ED4Z6NT6HM19NRJ13M4P","draft-content",null,"Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.","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\u002Fmarketing\u002Fskills\u002Fdraft-content\u002FSKILL.md",[18,23,26,29,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"draft content","content","draft","with","type","you","when","use","writing","social media","pages","social","landing","for","seo","email","platform","Media","brand","posts","2026-11-10 10:12:30",false,"---\nname: draft-content\ndescription: Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.\nargument-hint: \"\u003Ccontent type and topic>\"\n---\n\n# Draft Content\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate marketing content drafts tailored to a specific content type, audience, and brand voice.\n\n## Trigger\n\nUser runs `\u002Fdraft-content` or asks to draft, write, or create marketing content.\n\n## Inputs\n\nGather the following from the user. If not provided, ask before proceeding:\n\n1. **Content type** — one of:\n   - Blog post\n   - Social media post (specify platform: LinkedIn, Twitter\u002FX, Instagram, Facebook)\n   - Email newsletter\n   - Landing page copy\n   - Press release\n   - Case study\n\n2. **Topic** — the subject or theme of the content\n\n3. **Target audience** — who this content is for (role, industry, seniority, pain points)\n\n4. **Key messages** — 2-4 main points or takeaways to communicate\n\n5. **Tone** — e.g., authoritative, conversational, inspirational, technical, witty (optional if brand voice is configured)\n\n6. **Length** — target word count or format constraint (e.g., \"1000 words\", \"280 characters\", \"3 paragraphs\")\n\n## Brand Voice\n\n- If the user has a brand voice configured in their local settings file, apply it automatically. Inform the user that brand voice settings are being applied.\n- If no brand voice is configured, ask: \"Do you have brand voice guidelines you'd like me to follow? If not, I'll use a neutral professional tone.\"\n- Apply the specified or default tone consistently throughout the draft.\n\n## Content Generation by Type\n\n### Blog Post\n- Engaging headline (provide 2-3 options)\n- Introduction with a hook (question, statistic, bold statement, or story)\n- 3-5 organized sections with descriptive subheadings\n- Supporting points, examples, or data references in each section\n- Conclusion with a clear call to action\n- SEO considerations: suggest a primary keyword, include it in the headline and first paragraph, use related keywords in subheadings\n\n### Social Media Post\n- Platform-appropriate format and length\n- Hook in the first line\n- Hashtag suggestions (3-5 relevant hashtags)\n- Call to action or engagement prompt\n- Emoji usage appropriate to brand and platform\n- If LinkedIn: professional framing, paragraph breaks for readability\n- If Twitter\u002FX: concise, punchy, within character limit\n- If Instagram: visual-first language, story-driven, hashtag block\n\n### Email Newsletter\n- Subject line (provide 2-3 options with open-rate considerations)\n- Preview text\n- Greeting\n- Body sections with clear hierarchy\n- Call to action button text\n- Sign-off\n- Unsubscribe note reminder\n\n### Landing Page Copy\n- Headline and subheadline\n- Hero section copy\n- Value propositions (3-4 benefit-driven bullets or sections)\n- Social proof placeholder (suggest testimonial or stat placement)\n- Primary and secondary CTAs\n- FAQ section suggestions\n- SEO: meta title and meta description suggestions\n\n### Press Release\n- Headline following press release conventions\n- Dateline and location\n- Lead paragraph (who, what, when, where, why)\n- Supporting quotes (provide placeholder guidance)\n- Company boilerplate placeholder\n- Media contact placeholder\n- Standard press release formatting\n\n### Case Study\n- Title emphasizing the result\n- Customer overview (industry, size, challenge)\n- Challenge section\n- Solution section (what was implemented)\n- Results section with metrics (prompt user for data)\n- Customer quote placeholder\n- Call to action\n\n## SEO Considerations (for web content)\n\nFor blog posts, landing pages, and other web-facing content:\n- Suggest a primary keyword based on the topic\n- Recommend keyword placement: headline, first paragraph, subheadings, meta description\n- Suggest internal and external linking opportunities\n- Recommend a meta description (under 160 characters)\n- Note image alt text opportunities\n\n## Output\n\nPresent the draft with clear formatting. After the draft, include:\n- A brief note on what brand voice and tone were applied\n- Any SEO recommendations (for web content)\n- Suggestions for next steps (e.g., \"Review with your team\", \"Add customer quotes\", \"Pair with a visual\")\n\nAsk: \"Would you like me to revise any section, adjust the tone, or create a variation for a different channel?\"\n","# Draft Content\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate marketing content drafts tailored to a specific content type, audience, and brand voice.\n\n## Trigger\n\nUser runs `\u002Fdraft-content` or asks to draft, write, or create marketing content.\n\n## Inputs\n\nGather the following from the user. If not provided, ask before proceeding:\n\n1. **Content type** — one of:\n   - Blog post\n   - Social media post (specify platform: LinkedIn, Twitter\u002FX, Instagram, Facebook)\n   - Email newsletter\n   - Landing page copy\n   - Press release\n   - Case study\n\n2. **Topic** — the subject or theme of the content\n\n3. **Target audience** — who this content is for (role, industry, seniority, pain points)\n\n4. **Key messages** — 2-4 main points or takeaways to communicate\n\n5. **Tone** — e.g., authoritative, conversational, inspirational, technical, witty (optional if brand voice is configured)\n\n6. **Length** — target word count or format constraint (e.g., \"1000 words\", \"280 characters\", \"3 paragraphs\")\n\n## Brand Voice\n\n- If the user has a brand voice configured in their local settings file, apply it automatically. Inform the user that brand voice settings are being applied.\n- If no brand voice is configured, ask: \"Do you have brand voice guidelines you'd like me to follow? If not, I'll use a neutral professional tone.\"\n- Apply the specified or default tone consistently throughout the draft.\n\n## Content Generation by Type\n\n### Blog Post\n- Engaging headline (provide 2-3 options)\n- Introduction with a hook (question, statistic, bold statement, or story)\n- 3-5 organized sections with descriptive subheadings\n- Supporting points, examples, or data references in each section\n- Conclusion with a clear call to action\n- SEO considerations: suggest a primary keyword, include it in the headline and first paragraph, use related keywords in subheadings\n\n### Social Media Post\n- Platform-appropriate format and length\n- Hook in the first line\n- Hashtag suggestions (3-5 relevant hashtags)\n- Call to action or engagement prompt\n- Emoji usage appropriate to brand and platform\n- If LinkedIn: professional framing, paragraph breaks for readability\n- If Twitter\u002FX: concise, punchy, within character limit\n- If Instagram: visual-first language, story-driven, hashtag block\n\n### Email Newsletter\n- Subject line (provide 2-3 options with open-rate considerations)\n- Preview text\n- Greeting\n- Body sections with clear hierarchy\n- Call to action button text\n- Sign-off\n- Unsubscribe note reminder\n\n### Landing Page Copy\n- Headline and subheadline\n- Hero section copy\n- Value propositions (3-4 benefit-driven bullets or sections)\n- Social proof placeholder (suggest testimonial or stat placement)\n- Primary and secondary CTAs\n- FAQ section suggestions\n- SEO: meta title and meta description suggestions\n\n### Press Release\n- Headline following press release conventions\n- Dateline and location\n- Lead paragraph (who, what, when, where, why)\n- Supporting quotes (provide placeholder guidance)\n- Company boilerplate placeholder\n- Media contact placeholder\n- Standard press release formatting\n\n### Case Study\n- Title emphasizing the result\n- Customer overview (industry, size, challenge)\n- Challenge section\n- Solution section (what was implemented)\n- Results section with metrics (prompt user for data)\n- Customer quote placeholder\n- Call to action\n\n## SEO Considerations (for web content)\n\nFor blog posts, landing pages, and other web-facing content:\n- Suggest a primary keyword based on the topic\n- Recommend keyword placement: headline, first paragraph, subheadings, meta description\n- Suggest internal and external linking opportunities\n- Recommend a meta description (under 160 characters)\n- Note image alt text opportunities\n\n## Output\n\nPresent the draft with clear formatting. After the draft, include:\n- A brief note on what brand voice and tone were applied\n- Any SEO recommendations (for web content)\n- Suggestions for next steps (e.g., \"Review with your team\", \"Add customer quotes\", \"Pair with a visual\")\n\nAsk: \"Would you like me to revise any section, adjust the tone, or create a variation for a different channel?\"\n",{"name":5,"description":7,"argument-hint":63},"\u003Ccontent type and topic>","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","marketing\u002Fskills\u002Fdraft-content",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":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill draft-content",{"tool":78,"command":79},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill draft-content",{"tool":81,"command":82},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill draft-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fmarketing\u002Fskills\u002Fdraft-content\u002FSKILL.md",true,[],[87,112,137,159,186,207],{"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":58},"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",[],[94,95,96,97,98,99,46,44,100,101,102,103,104,105,106,107,108,109,110,111],"ticket","ticket deflector","mode","up","payments","open","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"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":58},"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",[],[119,120,121,122,123,124,125,126,127,128,44,129,130,131,132,133,111,134,135,136],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","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":58},"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,120,145,146,121,147,148,123,149,150,151,152,153,51,154,125,155,156,157,158],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":58},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000034","行政与办公人员",[169,170,171,172,173,174,149,175,176,177,178,179,180,181,44,182,183,102,184,185],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":58},"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",[192],{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},[49,194,195,196,197,39,146,198,57,199,200,97,201,44,202,203,204,111,205,206],"social content engine","engine","content engine","social content","brief","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":58},"01M718XMPJVH0EVRVP998BVZPC","smb-router","The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks \"what can you do,\" \"help me with my business,\" \"what should I focus on,\" \"I don't know where to start,\" or any open-ended business request that doesn't clearly match a single skill.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsmb-router\u002FSKILL.md",[],[214,215,216,147,217,51,154,218,99,219,128,158,43,220,221,41,222,202,223,106],"router","smb","smb router","do","front","single","vague","can","plugin","focus"]