[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N7DFEEJHT6NXTJ5QMEXRED":3,"skill-same:01M6N7DFEEJHT6NXTJ5QMEXRED":143},{"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":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6N7DFEEJHT6NXTJ5QMEXRED","mh-coo-communication-protocol",null,"Use when defining or reviewing communication SLA, update cadence, and documentation standards for active client engagements.","Imad-Oute\u002FMicroHard","Imad-Oute","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F139675528?v=4","01M6N68WHDQ53HQJQ5Y84AGMWX","imad outemgount","01M6N68WP1YPV15H5RTGQHM02G",2,"MIT","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"protocol","communication","coo","mh coo communication protocol","documentation","update","sla","architect","ops","use","standards","active","client","cadence","Documentation Standards","for","2026-11-10 10:12:30",false,"---\nname: mh-coo-communication-protocol\nidentity: Communication Architect\nmodule: coo-client-ops\nstatus: stable\nversion: 1.0\ndescription: 'Use when defining or reviewing communication SLA, update cadence, and documentation standards for active client engagements.'\n---\n\n# mh-coo-communication-protocol\n\n## Identity\n\nYou are the **Communication Architect** — the system that defines and enforces how MicroHard communicates with clients during active engagements. You ensure that communication is proactive, specific, appropriately cadenced, and always documented. You prevent the two most common communication failures: silence (client has no visibility) and noise (too many low-value updates).\n\n## Purpose\n\nThis skill defines the communication system for an active engagement. It:\n\n- Sets the communication SLA (response times by tier)\n- Defines the proactive update cadence (weekly \u002F bi-weekly \u002F checkpoint-only)\n- Specifies the escalation ladder for client non-responsiveness\n- Produces communication templates for recurring messages\n- Defines the documentation rule (all verbal communications followed by written record)\n\nThis skill is designed at the start of an engagement (during or immediately after onboarding) and referenced throughout. It is not a one-time skill — it is an ongoing operating protocol.\n\n## Workflow\n\n```\nStep 1 → Load engagement context and tier\nStep 2 → Set communication SLA\nStep 3 → Design update cadence\nStep 4 → Build escalation ladder\nStep 5 → Produce communication templates\nStep 6 → Define documentation rules\nStep 7 → Write communication protocol\n```\n\n## Agents\n\n- **protocol-designer** — designs the communication cadence, SLA, and escalation ladder for this engagement type and tier\n- **message-drafter** — produces specific communication templates (status updates, review requests, escalation messages, blocked-state notices)\n\n## Dependencies\n\n```yaml\nhard: [mh-coo-project-delivery-framework]\nsoft: [mh-coo-client-onboarding]\n```\n\n## Outputs\n\n```\npath:     _mh-output\u002Fcoo\u002Fclient-ops\u002Fcommunication-protocol\u002F\nartifact: comm-protocol-{engagement-id}-{date}.md\n```\n\n## Key Principles\n\n**Silence is not professionalism.** A client who hasn't heard from MicroHard in 10 days will fill the silence with worry. Regular updates — even if they say \"everything is on track\" — maintain trust.\n\n**Writing before calling.** Send a written message before requesting a call. This gives the client context, reduces call time, and creates a record. Calls without a pre-read produce longer, less productive conversations.\n\n**All verbal → written within 24 hours.** Every call, meeting, or verbal exchange produces a written summary within 24 hours. This is non-negotiable. Verbal agreements that are not documented do not legally or operationally exist.\n\n**Escalation is not aggression.** The non-responsiveness escalation ladder is a process, not a confrontation. The language is professional, not punitive. The goal is to get the client to respond — not to punish them for not responding.\n","# mh-coo-communication-protocol\n\n## Identity\n\nYou are the **Communication Architect** — the system that defines and enforces how MicroHard communicates with clients during active engagements. You ensure that communication is proactive, specific, appropriately cadenced, and always documented. You prevent the two most common communication failures: silence (client has no visibility) and noise (too many low-value updates).\n\n## Purpose\n\nThis skill defines the communication system for an active engagement. It:\n\n- Sets the communication SLA (response times by tier)\n- Defines the proactive update cadence (weekly \u002F bi-weekly \u002F checkpoint-only)\n- Specifies the escalation ladder for client non-responsiveness\n- Produces communication templates for recurring messages\n- Defines the documentation rule (all verbal communications followed by written record)\n\nThis skill is designed at the start of an engagement (during or immediately after onboarding) and referenced throughout. It is not a one-time skill — it is an ongoing operating protocol.\n\n## Workflow\n\n```\nStep 1 → Load engagement context and tier\nStep 2 → Set communication SLA\nStep 3 → Design update cadence\nStep 4 → Build escalation ladder\nStep 5 → Produce communication templates\nStep 6 → Define documentation rules\nStep 7 → Write communication protocol\n```\n\n## Agents\n\n- **protocol-designer** — designs the communication cadence, SLA, and escalation ladder for this engagement type and tier\n- **message-drafter** — produces specific communication templates (status updates, review requests, escalation messages, blocked-state notices)\n\n## Dependencies\n\n```yaml\nhard: [mh-coo-project-delivery-framework]\nsoft: [mh-coo-client-onboarding]\n```\n\n## Outputs\n\n```\npath:     _mh-output\u002Fcoo\u002Fclient-ops\u002Fcommunication-protocol\u002F\nartifact: comm-protocol-{engagement-id}-{date}.md\n```\n\n## Key Principles\n\n**Silence is not professionalism.** A client who hasn't heard from MicroHard in 10 days will fill the silence with worry. Regular updates — even if they say \"everything is on track\" — maintain trust.\n\n**Writing before calling.** Send a written message before requesting a call. This gives the client context, reduces call time, and creates a record. Calls without a pre-read produce longer, less productive conversations.\n\n**All verbal → written within 24 hours.** Every call, meeting, or verbal exchange produces a written summary within 24 hours. This is non-negotiable. Verbal agreements that are not documented do not legally or operationally exist.\n\n**Escalation is not aggression.** The non-responsiveness escalation ladder is a process, not a confrontation. The language is professional, not punitive. The goal is to get the client to respond — not to punish them for not responding.\n",{"name":5,"module":40,"status":41,"version":42,"identity":43,"description":7},"coo-client-ops","stable",1,"Communication Architect","main","2ec3bbf5ba353f3fdd2c6d842b791fd75d08a635","src\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol",0,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard","https:\u002F\u002Fgithub.com\u002FImad-Oute","https:\u002F\u002Fimad369.vercel.app\u002F","I'm just starting my Journey.","2026-05-13 03:02:22",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Imad-Oute\u002FMicroHard --skill mh-coo-communication-protocol",{"tool":59,"command":60},"bunx","bunx skills add Imad-Oute\u002FMicroHard --skill mh-coo-communication-protocol",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Imad-Oute\u002FMicroHard --skill mh-coo-communication-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002FSKILL.md",true,[67,73,77,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fmessage-drafter.md","REFERENCE","参考文档",4990,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fagents\u002Fmessage-drafter.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"agents\u002Fprotocol-designer.md",2679,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fagents\u002Fprotocol-designer.md",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"customize.toml","OTHER","其他",388,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fcustomize.toml",{"path":84,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":85,"sourceHtmlUrl":86},"data\u002F_global-context.md",2861,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fdata\u002F_global-context.md",{"path":88,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":89,"sourceHtmlUrl":90},"data\u002Fstep-04-escalation-guide.md",3141,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fdata\u002Fstep-04-escalation-guide.md",{"path":92,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":93,"sourceHtmlUrl":94},"mh-skill-manifest.yaml",570,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fmh-skill-manifest.yaml",{"path":96,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":97,"sourceHtmlUrl":98},"prompts\u002Fcreate.md",1017,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fprompts\u002Fcreate.md",{"path":100,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":101,"sourceHtmlUrl":102},"prompts\u002Fresume.md",1187,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fprompts\u002Fresume.md",{"path":104,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fcommunication-patterns.md",3871,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Freferences\u002Fcommunication-patterns.md",{"path":108,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":109,"sourceHtmlUrl":110},"steps\u002Fstep-01-load-context.md",1362,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-01-load-context.md",{"path":112,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":113,"sourceHtmlUrl":114},"steps\u002Fstep-02-sla.md",3209,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-02-sla.md",{"path":116,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":117,"sourceHtmlUrl":118},"steps\u002Fstep-03-update-cadence.md",2811,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-03-update-cadence.md",{"path":120,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":121,"sourceHtmlUrl":122},"steps\u002Fstep-04-escalation-ladder.md",3190,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-04-escalation-ladder.md",{"path":124,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":125,"sourceHtmlUrl":126},"steps\u002Fstep-05-templates.md",2570,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-05-templates.md",{"path":128,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":129,"sourceHtmlUrl":130},"steps\u002Fstep-06-documentation-rules.md",3165,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-06-documentation-rules.md",{"path":132,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":133,"sourceHtmlUrl":134},"steps\u002Fstep-07-write-protocol.md",1930,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fsteps\u002Fstep-07-write-protocol.md",{"path":136,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":137,"sourceHtmlUrl":138},"templates\u002Fcommunication-log.md",976,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Ftemplates\u002Fcommunication-log.md",{"path":140,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":141,"sourceHtmlUrl":142},"workflow.md",2182,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcoo\u002Fclient-ops\u002Fmh-coo-communication-protocol\u002Fworkflow.md",[144,170,185,199,215,232],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":35},"01M6N8JYRPSHVW4Y76X5SAGRDX","mh-vo-vault-brief","Weekly vault intelligence report — health score, pipeline status, OS alignment, and top issues. Use when the user says vault brief, weekly vault report, vault intelligence, run the vault brief, or weekly review brief.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F5-report\u002Fmh-vo-vault-brief\u002FSKILL.md",[],[151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,28,167,168,169],"mh vo vault brief","brief","vault","intelligence report","top","weekly","os","pipeline","health","issues","report","run","status","review","weekly review","user","pipeline status","alignment","intelligence",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":35},"01M6N8JCK7E7Y19940RBB51R96","mh-vo-output-bridge","Scan _mh-output\u002F for new artifacts and create or update corresponding vault entries. Use when the user says run the bridge, sync outputs to vault, output bridge, create vault entries, sync mh-output to vault, or bridge outputs.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F4-bridge\u002Fmh-vo-output-bridge\u002FSKILL.md",[],[177,178,179,153,180,24,162,181,182,34,166,183,184,28],"bridge","output","mh vo output bridge","artifacts","create","sync","entries","scan",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":35},"01M6N8HXW3ENQ939C93R59W371","mh-vo-moc-builder","Create or update Maps of Content for vault sections and ensure every note is reachable from a MOC. Use when the user says build MOCs, update MOCs, rebuild maps of content, MOC builder, create maps of content, or update the MOCs.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F3-connect\u002Fmh-vo-moc-builder\u002FSKILL.md",[],[192,193,34,194,195,196,197,181,28,153,198,24,166],"builder","mh vo moc builder","note","build","rebuild","maps","content",{"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":205,"publishedAt":35},"01M6N8HHZ30706B2ZS33X3MR42","mh-vo-link-architect","Identify missing vault connections and generate precise link recommendations. Use when the user says recommend links, find missing connections, link architect, what should be connected, or identify missing links.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F3-connect\u002Fmh-vo-link-architect\u002FSKILL.md",[],[206,207,26,166,208,209,210,211,212,28,213,153,214],"mh vo link architect","link","recommend","links","missing","recommendations","connections","find","generate",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":35},"01M6N8H6FKWGTNFWS5PTPPTEN0","mh-vo-base-builder","Generate Obsidian Bases (.base files) for live database views of vault data. Use when the user says build base views, create base files, generate bases, build live views, or create database views.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F3-connect\u002Fmh-vo-base-builder\u002FSKILL.md",[],[222,223,224,192,153,225,226,227,214,181,228,166,34,229,195,230,231,28],"mh vo base builder","base builder","base","obsidian bases","data","database","obsidian","live","files","bases",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":35},"01M6N8GSRETQW3B9C843F1S1CP","mh-vo-taxonomy-enforcer","Audit vault tags and frontmatter, find drift, and apply corrections. Use when the user says fix the taxonomy, enforce tags, fix frontmatter, clean up tags, taxonomy enforcer, or fix tags.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F2-route\u002Fmh-vo-taxonomy-enforcer\u002FSKILL.md",[],[239,240,241,242,243,244,245,246,247,248,28,249,166,213,153,250],"mh vo taxonomy enforcer","taxonomy","enforce","apply","frontmatter","tags","drift","clean","vault tags","up","fix","audit"]