[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7136FDQADRW9G9FK7W7FF0D":3,"skill-same:01M7136FDQADRW9G9FK7W7FF0D":64},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7136FDQADRW9G9FK7W7FF0D","yq-translate-docs",null,"维护中英双语文档的语义一致、结构对应和自然表达。","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\u002Fyq-translate-docs\u002Fb3db5d20c0e56e98\u002Fyq-translate-docs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29],"docs","translate","translate docs","yq","yq translate docs","文档","2026-11-10 10:12:30",false,"---\r\nname: yq-translate-docs\ndescription: 维护中英双语文档的语义一致、结构对应和自然表达。\n---\n\n# Translate Bilingual Docs\n\nKeep an English and Chinese document pair equivalent without forcing either language into the other's sentence structure. Use the repository's own localization contract; do not import another project's filenames, sidecars, manifests, or validation rules.\n\nThis skill is explicit-only. Use it when the user invokes `$yq-translate-docs` to translate, synchronize, reconcile, rename, or audit bilingual documentation. It covers maintained documentation such as READMEs, guides, release notes, and website pages. Source-code locale dictionaries follow the project's application-i18n workflow unless the user includes them.\n\nWhile this explicitly invoked workflow is active, apply [`$yq-technical-writing`](..\u002Fyq-technical-writing\u002FSKILL.md) to both languages so every source proposition survives in natural prose. Before a user-authorized push or readiness claim, invoke `$yq-pre-push-checks` once for the outgoing change set; do not run it per document or infer permission to commit or push.\n\n## Discover the pair contract\n\nBefore editing, read the applicable repository instructions and determine:\n\n- the default document, its counterpart, and any legacy alias or redirect;\n- whether either side is generated, frozen, or owned by another source;\n- the glossary, terminology table, style sample, link policy, and locale-specific assets already used by the project;\n- existing localization, link, rendering, or documentation checks.\n\nEither language may be the authored side for a change. Product facts come from current code, configuration, release evidence, or another declared owner; neither language automatically overrides those sources.\n\n## Classify the change\n\n- **Update:** one side changed. Translate only the changed semantic units and preserve reviewed wording outside that diff.\n- **New pair:** no counterpart exists. Translate the whole document in sections, keeping the source structure visible as work progresses.\n- **Both sides changed:** compare both sides with their common base and reconcile each changed unit. Preserve independent valid updates instead of choosing one language for the whole file.\n- **Rename or delete:** move or remove the counterpart and repair navigation, language switches, and inbound links according to repository policy.\n- **Alias or redirect:** preserve its routing role. Do not expand a deliberate compatibility stub into a second maintained translation.\n\n## Update an existing pair\n\nUse the current diff, merge base, or repository pairing record to identify what changed. Translate the smallest complete semantic unit that carries the change: a paragraph, list item, table row, heading section, or whole document only when smaller alignment is unsafe.\n\nPreserve meaning clause by clause:\n\n- keep obligations, exceptions, limitations, numbers, platform support, release names, and failure behavior equivalent;\n- follow the project's established terminology and introduce an unresolved term explicitly rather than inventing a silent translation;\n- keep commands, code spans, identifiers, URLs, and file names exact unless the repository deliberately localizes them;\n- keep headings, lists, tables, code blocks, and link targets structurally corresponding, but do not require physical line-count equality;\n- allow language-specific screenshots, alt text, examples, and search wording when they serve the same documented fact and audience.\n\nWrite natural target-language prose first, then compare it with the source clause by clause. Literal sentence transposition is not fidelity when it produces awkward or misleading text.\n\n## Create or reconcile a complete pair\n\nFor a new counterpart, translate section by section and read the completed target alone before the final source comparison. For divergent existing files, establish the owner of each changed claim, merge compatible additions, and report unresolved factual conflicts rather than translating one conflict into the other language.\n\nDo not copy stale facts merely to make both sides match. Repair the owning fact first when authorized; otherwise mark the discrepancy and the evidence needed to resolve it.\n\n## Validate without adding process\n\nRun only the repository's existing relevant checks, such as localized README tests, link checks, documentation rendering, or an established pairing verifier. If no such check exists, compare headings, code blocks, commands, links, assets, version claims, limitations, and language switches manually.\n\nDo not create a sidecar, hash record, translation manifest, line-count rule, test, script, or CI gate merely because the project has a bilingual pair. Add process only when the user separately requests it or the repository already requires it.\n\nReport the pair and authored side, units translated or reconciled, terminology decisions, deliberate locale-specific differences, unresolved conflicts, and checks actually run.\n","# Translate Bilingual Docs\n\nKeep an English and Chinese document pair equivalent without forcing either language into the other's sentence structure. Use the repository's own localization contract; do not import another project's filenames, sidecars, manifests, or validation rules.\n\nThis skill is explicit-only. Use it when the user invokes `$yq-translate-docs` to translate, synchronize, reconcile, rename, or audit bilingual documentation. It covers maintained documentation such as READMEs, guides, release notes, and website pages. Source-code locale dictionaries follow the project's application-i18n workflow unless the user includes them.\n\nWhile this explicitly invoked workflow is active, apply [`$yq-technical-writing`](..\u002Fyq-technical-writing\u002FSKILL.md) to both languages so every source proposition survives in natural prose. Before a user-authorized push or readiness claim, invoke `$yq-pre-push-checks` once for the outgoing change set; do not run it per document or infer permission to commit or push.\n\n## Discover the pair contract\n\nBefore editing, read the applicable repository instructions and determine:\n\n- the default document, its counterpart, and any legacy alias or redirect;\n- whether either side is generated, frozen, or owned by another source;\n- the glossary, terminology table, style sample, link policy, and locale-specific assets already used by the project;\n- existing localization, link, rendering, or documentation checks.\n\nEither language may be the authored side for a change. Product facts come from current code, configuration, release evidence, or another declared owner; neither language automatically overrides those sources.\n\n## Classify the change\n\n- **Update:** one side changed. Translate only the changed semantic units and preserve reviewed wording outside that diff.\n- **New pair:** no counterpart exists. Translate the whole document in sections, keeping the source structure visible as work progresses.\n- **Both sides changed:** compare both sides with their common base and reconcile each changed unit. Preserve independent valid updates instead of choosing one language for the whole file.\n- **Rename or delete:** move or remove the counterpart and repair navigation, language switches, and inbound links according to repository policy.\n- **Alias or redirect:** preserve its routing role. Do not expand a deliberate compatibility stub into a second maintained translation.\n\n## Update an existing pair\n\nUse the current diff, merge base, or repository pairing record to identify what changed. Translate the smallest complete semantic unit that carries the change: a paragraph, list item, table row, heading section, or whole document only when smaller alignment is unsafe.\n\nPreserve meaning clause by clause:\n\n- keep obligations, exceptions, limitations, numbers, platform support, release names, and failure behavior equivalent;\n- follow the project's established terminology and introduce an unresolved term explicitly rather than inventing a silent translation;\n- keep commands, code spans, identifiers, URLs, and file names exact unless the repository deliberately localizes them;\n- keep headings, lists, tables, code blocks, and link targets structurally corresponding, but do not require physical line-count equality;\n- allow language-specific screenshots, alt text, examples, and search wording when they serve the same documented fact and audience.\n\nWrite natural target-language prose first, then compare it with the source clause by clause. Literal sentence transposition is not fidelity when it produces awkward or misleading text.\n\n## Create or reconcile a complete pair\n\nFor a new counterpart, translate section by section and read the completed target alone before the final source comparison. For divergent existing files, establish the owner of each changed claim, merge compatible additions, and report unresolved factual conflicts rather than translating one conflict into the other language.\n\nDo not copy stale facts merely to make both sides match. Repair the owning fact first when authorized; otherwise mark the discrepancy and the evidence needed to resolve it.\n\n## Validate without adding process\n\nRun only the repository's existing relevant checks, such as localized README tests, link checks, documentation rendering, or an established pairing verifier. If no such check exists, compare headings, code blocks, commands, links, assets, version claims, limitations, and language switches manually.\n\nDo not create a sidecar, hash record, translation manifest, line-count rule, test, script, or CI gate merely because the project has a bilingual pair. Add process only when the user separately requests it or the repository already requires it.\n\nReport the pair and authored side, units translated or reconciled, terminology decisions, deliberate locale-specific differences, unresolved conflicts, and checks actually run.\n",{"name":5,"description":7},"mine","1e7390741dffd3d5041fca4ebc056071ee3ba137","archives\u002Fuser-installed-skills\u002Fyq-translate-docs\u002Fb3db5d20c0e56e98\u002Fyq-translate-docs",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add EthanYoQ\u002FSkill-hub --skill yq-translate-docs",{"tool":50,"command":51},"bunx","bunx skills add EthanYoQ\u002FSkill-hub --skill yq-translate-docs",{"tool":53,"command":54},"pnpm","pnpm dlx skills add EthanYoQ\u002FSkill-hub --skill yq-translate-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fyq-translate-docs\u002Fb3db5d20c0e56e98\u002Fyq-translate-docs\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"agents\u002Fopenai.yaml","REFERENCE","参考文档",257,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fyq-translate-docs\u002Fb3db5d20c0e56e98\u002Fyq-translate-docs\u002Fagents\u002Fopenai.yaml",[65,93,124,148,166,181],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":72,"publishedAt":30},"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",[71],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"social","xhs pharma social listening","social listening","xhs","medical","counting","when","collection","batch","analyze","notes","run","opencli","fallback","captcha","agent reach","evidence","for","collect","produce",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":105,"publishedAt":30},"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",[99,100],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[106,107,108,109,110,111,112,113,79,114,115,116,117,118,119,120,90,121,122,123],"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":30},"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",[130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,132,133,134,135,136,137,79,138,139,140,141,107,90,142,143,144,145,146,147],"eval","harness","healthcare eval harness","eval harness","clinical","patient","workflow","Evaluation","Safety","integrity","deployment","accuracy","tests","deployments","use","super",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":30},"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",[154],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,156,119,157,158,77,136,159,79,160,161,162,140,118,163,164,165,90,122,146],"EMR","healthcare emr patterns","decision","workflows","support","clinical decision support","features","ui","as","development",{"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":30},"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",[172],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[106,119,174,158,136,156,159,79,175,176,160,161,177,165,121,178,146,179,147,180],"healthcare cdss patterns","scoring","interaction","severity","classification","alert","decision support",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":30},"01M713BVK3PQR7V4ZKYGMWMXJD","dxy-task-clarify","用户的请求含糊、缺背景、缺资料说明、缺读者或用途时使用。先用少量带选项的追问把任务问清楚，写成任务卡，用户确认后再执行。尤其适用于医生、科研人员和药企各岗位的工作，例如「帮我分析一下这些数据」「帮我准备明天的拜访」「写个总结」「做个 PPT」「回一下这封邮件」「整理一下会议纪要」「整理一下这些文献」「帮我准备下周的讲课」「写个病例汇报」「帮我写个提示词」。用户说「先问我」「帮我理清需求」「我不知道怎么描述」「我不会问 AI」时也使用。用途、资料、读者都已说清的请求，纯翻译，以及写代码、改代码，不使用。","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fdxy-task-clarify\u002FSKILL.md",[187],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[189,190,191,192,193,194,195,196],"clarify","dxy task clarify","task","pptx","整理","翻译","数据","总结"]