[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7135HGF05HXZZVWHTDN2C8G":3,"skill-same:01M7135HGF05HXZZVWHTDN2C8G":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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M7135HGF05HXZZVWHTDN2C8G","wechat-article-writer",null,"Project-level WeChat article drafting workflow for turning source materials, repo intakes, product notes, screenshots, or existing markdown into a publishable Chinese公众号 draft. Use for writing, rewriting, evidence-gating, title options, platform adaptation, and image planning before optional publishing.","EthanYoQ\u002FSkill-hub","EthanYoQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257484394?v=4","01M70C9QKWR1YS0S7V26DNB18H","Ethan","01M70C9QMER047R5ANZZA6KC2P",11,"MIT","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fwechat-article-writer\u002Fbb28e73c36e86c6d\u002Fwechat-article-writer\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"wechat","article writer","article","wechat article","wechat article writer","writer","source","markdown","options","product","title","notes","drafting","公众号","image","workflow","gating","writing","adaptation","project","2026-11-10 10:12:30",false,"---\nname: wechat-article-writer\ndescription: Project-level WeChat article drafting workflow for turning source materials, repo intakes, product notes, screenshots, or existing markdown into a publishable Chinese公众号 draft. Use for writing, rewriting, evidence-gating, title options, platform adaptation, and image planning before optional publishing.\n---\n\n# WeChat Article Writer\n\nUse this skill for the writing part of the project. Use `wechat-mp-writer` when the user also wants intake automation or publishing.\n\n## Required Context\n\nRead these project files when drafting from product or repo material:\n\n- `docs\u002Fcontent-agent\u002Fworkflow.md`\n- `docs\u002Fcontent-agent\u002Fagent-prompt.md`\n- `docs\u002Fcontent-agent\u002Frules\u002Fwriting-rules.md` if present and relevant\n- The source ledger or intake summary for the current article\n\n## Drafting Flow\n\n1. Normalize inputs.\n   - Identify source files, URLs, screenshots, README files, and user notes.\n   - Ask focused questions only when a missing fact would materially change the article.\n2. Build evidence.\n   - Maintain verified, reasonable inference, unverified, and do-not-publish labels.\n   - Do not turn unverified hypotheses into factual claims.\n3. Choose article angle.\n   - Prefer product-backed, concrete workplace or technical value.\n   - Avoid generic \"AI tool recommendation\" framing unless the user explicitly wants it.\n4. Write a WeChat draft.\n   - Start with a concrete scene, contradiction, or strong conclusion.\n   - Keep paragraphs scannable without flattening depth.\n   - Make the authorial \"I\" light and functional.\n   - Use source-backed technical details and product decisions.\n5. Produce title options and visual plan.\n   - Use `wechat-title-strategist` before selecting the final title.\n   - Reject titles that are merely accurate but lack either depth or open-rate pull.\n   - Avoid stale AI discourse (\"别再写 Prompt\", \"Prompt 已死\", generic \"AI 时代来了\") unless the article's evidence makes that phrasing newly valuable.\n   - Use `wechat-visual-director` to create distinct cover\u002Fbody visual routes.\n   - Separate cover prompt from body illustration prompts.\n   - Recommend screenshots where they carry more evidence than generated art.\n6. Run a final risk gate.\n   - Remove secrets, private customer data, unverifiable superiority claims, and sensitive internal strategy.\n\n## Output Contract\n\nUnless the user narrows the request, return or create:\n\n- Final WeChat title\n- Article markdown\n- Evidence notes for major claims\n- Cover direction\n- Body image plan\n- Self-review and remaining open questions\n\nDo not publish from this skill directly; hand off to `wechat-mp-writer` or `baoyu-post-to-wechat`.\n","# WeChat Article Writer\n\nUse this skill for the writing part of the project. Use `wechat-mp-writer` when the user also wants intake automation or publishing.\n\n## Required Context\n\nRead these project files when drafting from product or repo material:\n\n- `docs\u002Fcontent-agent\u002Fworkflow.md`\n- `docs\u002Fcontent-agent\u002Fagent-prompt.md`\n- `docs\u002Fcontent-agent\u002Frules\u002Fwriting-rules.md` if present and relevant\n- The source ledger or intake summary for the current article\n\n## Drafting Flow\n\n1. Normalize inputs.\n   - Identify source files, URLs, screenshots, README files, and user notes.\n   - Ask focused questions only when a missing fact would materially change the article.\n2. Build evidence.\n   - Maintain verified, reasonable inference, unverified, and do-not-publish labels.\n   - Do not turn unverified hypotheses into factual claims.\n3. Choose article angle.\n   - Prefer product-backed, concrete workplace or technical value.\n   - Avoid generic \"AI tool recommendation\" framing unless the user explicitly wants it.\n4. Write a WeChat draft.\n   - Start with a concrete scene, contradiction, or strong conclusion.\n   - Keep paragraphs scannable without flattening depth.\n   - Make the authorial \"I\" light and functional.\n   - Use source-backed technical details and product decisions.\n5. Produce title options and visual plan.\n   - Use `wechat-title-strategist` before selecting the final title.\n   - Reject titles that are merely accurate but lack either depth or open-rate pull.\n   - Avoid stale AI discourse (\"别再写 Prompt\", \"Prompt 已死\", generic \"AI 时代来了\") unless the article's evidence makes that phrasing newly valuable.\n   - Use `wechat-visual-director` to create distinct cover\u002Fbody visual routes.\n   - Separate cover prompt from body illustration prompts.\n   - Recommend screenshots where they carry more evidence than generated art.\n6. Run a final risk gate.\n   - Remove secrets, private customer data, unverifiable superiority claims, and sensitive internal strategy.\n\n## Output Contract\n\nUnless the user narrows the request, return or create:\n\n- Final WeChat title\n- Article markdown\n- Evidence notes for major claims\n- Cover direction\n- Body image plan\n- Self-review and remaining open questions\n\nDo not publish from this skill directly; hand off to `wechat-mp-writer` or `baoyu-post-to-wechat`.\n",{"name":5,"description":7},"mine","1e7390741dffd3d5041fca4ebc056071ee3ba137","archives\u002Fuser-installed-skills\u002Fwechat-article-writer\u002Fbb28e73c36e86c6d\u002Fwechat-article-writer",5,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub","https:\u002F\u002Fgithub.com\u002FEthanYoQ","www.orz.md","Part Marketer, Part AI Explorer.","2026-11-07 14:52:29",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add EthanYoQ\u002FSkill-hub --skill wechat-article-writer",{"tool":72,"command":73},"bunx","bunx skills add EthanYoQ\u002FSkill-hub --skill wechat-article-writer",{"tool":75,"command":76},"pnpm","pnpm dlx skills add EthanYoQ\u002FSkill-hub --skill wechat-article-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fwechat-article-writer\u002Fbb28e73c36e86c6d\u002Fwechat-article-writer\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fwechat-article-writer\u002Fbb28e73c36e86c6d\u002Fwechat-article-writer\u002Fagents\u002Fopenai.yaml",[87,114,143,166,184,199],{"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":94,"publishedAt":52},"01M713CBDSYARG4PXFXK2R2NNN","xhs-pharma-social-listening","Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes\u002Fcomments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA\u002F461 fallback to Agent Reach\u002FOpenCLI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fxhs-pharma-social-listening\u002FSKILL.md",[93],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[95,96,97,98,99,100,101,102,103,104,43,105,106,107,108,109,110,111,112,113],"social","xhs pharma social listening","social listening","xhs","medical","counting","when","collection","batch","analyze","run","opencli","fallback","captcha","agent reach","evidence","for","collect","produce",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":124,"publishedAt":52},"01M713C8Q76ZP0WXXBRAFKS6EE","healthcare-phi-compliance","Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-phi-compliance\u002FSKILL.md",[120,121],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":122,"categoryName":123,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[125,126,127,128,129,130,131,132,101,133,134,135,136,137,138,139,111,140,141,142],"healthcare","phi","compliance","healthcare phi compliance","pii","compliance patterns","information","access","encryption","code","common","audit","data","patterns","Access Control","system","applications","Auditing Access Control",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":52},"01M713C5R2GE43X45T2K75TB76","healthcare-eval-harness","Patient safety evaluation harness for healthcare application deployments. Automated test suites for CDSS accuracy, PHI exposure, clinical workflow integrity, and integration compliance. Blocks deployments on safety failures. Use when a healthcare deployment must be gated on patient-safety tests for CDSS accuracy, PHI exposure, and workflow integrity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-eval-harness\u002FSKILL.md",[149],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[125,151,152,153,154,155,156,101,47,157,158,159,126,111,160,161,162,163,164,165],"eval","harness","healthcare eval harness","eval harness","clinical","patient","Evaluation","Safety","integrity","deployment","accuracy","tests","deployments","use","super",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":52},"01M713C2J17S91VYR7A8M696VR","healthcare-emr-patterns","EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-emr-patterns\u002FSKILL.md",[172],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[125,174,138,175,176,99,155,177,101,178,179,180,158,137,181,182,183,111,141,164],"EMR","healthcare emr patterns","decision","workflows","support","clinical decision support","features","ui","as","development",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":52},"01M713BZERTXV0N8X6SW9DDVWZ","healthcare-cdss-patterns","Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows. Use when building clinical decision support — drug interaction checks, dose validation, clinical scoring, or alert severity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-cdss-patterns\u002FSKILL.md",[190],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[125,138,192,176,155,174,177,101,193,194,178,179,195,183,140,196,164,197,165,198],"healthcare cdss patterns","scoring","interaction","severity","classification","alert","decision support",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":52},"01M713BVK3PQR7V4ZKYGMWMXJD","dxy-task-clarify","用户的请求含糊、缺背景、缺资料说明、缺读者或用途时使用。先用少量带选项的追问把任务问清楚，写成任务卡，用户确认后再执行。尤其适用于医生、科研人员和药企各岗位的工作，例如「帮我分析一下这些数据」「帮我准备明天的拜访」「写个总结」「做个 PPT」「回一下这封邮件」「整理一下会议纪要」「整理一下这些文献」「帮我准备下周的讲课」「写个病例汇报」「帮我写个提示词」。用户说「先问我」「帮我理清需求」「我不知道怎么描述」「我不会问 AI」时也使用。用途、资料、读者都已说清的请求，纯翻译，以及写代码、改代码，不使用。","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fdxy-task-clarify\u002FSKILL.md",[205],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[207,208,209,210,211,212,213,214],"clarify","dxy task clarify","task","pptx","整理","翻译","数据","总结"]