[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P01N4JDFNF6RR029YNPD6":3,"skill-same:01M71P01N4JDFNF6RR029YNPD6":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71P01N4JDFNF6RR029YNPD6","slack-messaging",null,"Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fslack-messaging\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fslack-messaging\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"messaging","slack","slack messaging","for","messages","slack messages","knowledge","work","github","https","guidance","syntax","plugins","partner","knowledge-work","2026-11-10 10:56:23",false,"---\nname: slack-messaging\ndescription: \"Guidance for composing well-formatted, effective Slack messages using mrkdwn syntax\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"partner-built\u002Fslack\u002Fskills\u002Fslack-messaging\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\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,"tags":44,"tools":45,"source":46,"license":14,"description":7,"source_path":47,"source_commit":48},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","partner-built\u002Fslack\u002Fskills\u002Fslack-messaging","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fslack-messaging",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add monoes\u002Fmonomind --skill slack-messaging",{"tool":64,"command":65},"bunx","bunx skills add monoes\u002Fmonomind --skill slack-messaging",{"tool":67,"command":68},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill slack-messaging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fslack-messaging\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[78,105,140,166,186,213],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":104},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[85,86,87,88,89,90,91,30,92,93,94,95,96,97,98,99,100,101,102,103],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":121,"publishedAt":104},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[113,116],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[122,123,124,89,125,126,127,128,93,129,130,131,132,133,134,135,136,137,138,139],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":104},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000031","产品经理",[133,151,152,153,154,30,155,127,156,157,31,132,158,159,160,161,162,163,164,165],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":104},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师",[93,133,177,178,27,179,30,164,127,180,181,182,183,31,32,184,33,35,36,185],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","data",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":198,"publishedAt":104},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[199,200,201,202,27,203,204,205,206,92,207,208,209,93,96,32,210,211,212,33],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":220,"publishedAt":104},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[219],{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},[201,221,222,223,224,225,226,27,227,228,129,229,230,231,96,32,232,233,33,234],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]