{ "schemaVersion": "1.0", "item": { "slug": "comms-md", "name": "COMMS.md Creator", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/stedmanhalliday/comms-md", "canonicalUrl": "https://clawhub.ai/stedmanhalliday/comms-md", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/comms-md", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=comms-md", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "references/comms-template.md", "references/example.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/comms-md" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/comms-md", "agentPageUrl": "https://openagent3.xyz/skills/comms-md/agent", "manifestUrl": "https://openagent3.xyz/skills/comms-md/agent.json", "briefUrl": "https://openagent3.xyz/skills/comms-md/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "COMMS.md Creator", "body": "Generate a structured communication preferences document through guided conversation." }, { "title": "What COMMS.md Is", "body": "A queryable personal document that expresses how someone communicates: their natural style, channel preferences, availability rhythms, async voice, and interaction protocols. Designed to be read by both humans and agents before initiating contact." }, { "title": "1. Orient", "body": "Explain the concept briefly:\n\n\"A COMMS.md is a structured doc that captures how you communicate — your style, when you're available, which channels you prefer, how you write in different contexts. Think of it as a user manual for reaching you. Other people (or their agents) can reference it before getting in touch.\"" }, { "title": "2. Interview", "body": "Walk through these areas conversationally. Don't dump all questions at once — do 2-3 per turn, adapt based on answers, skip what's clearly not relevant.\n\nStyle & strengths (start here — it's introspective and sets the tone):\n\nWhat comes naturally when you communicate? (e.g. brevity, storytelling, humor, directness)\nWhat requires effort? (e.g. small talk, follow-through, emotional labor, context-switching)\nWhere does communication break down for you?\n\nCollaboration model:\n\nWhat kind of people do you work best with?\nHow do you prefer to set up working relationships?\n\nWeekly rhythm:\n\nWalk through their week: energy, availability windows, protected time\nWhich days are meeting-heavy? Which are deep work?\n\nSync philosophy:\n\nWhat are calls for? What are they NOT for?\nHow tactical vs. strategic do calls get?\n\nChannel preferences:\n\nFor each situation type (urgent, professional, casual, etc.): what channel, what timing?\nRole of email vs. text vs. voice notes vs. calls?\nHow does closeness change channel choice?\nNotification habits, response triage, focus mode patterns\n\nAsync voice (this section often needs the most drawing out):\n\nHow do they write to close friends vs. professional contacts?\nCapitalization, punctuation, emoji habits?\nWhat do they never do in writing? (anti-patterns)\nHow do they handle outreach to new people? Re-engaging after silence?\nDo they have a gap between how competent they are and how warm they read? How do they bridge it?\n\nBoundaries:\n\nWhat's the fastest way to annoy them?\nWhat should people never do?" }, { "title": "3. Draft", "body": "Read references/comms-template.md for the output structure. Generate the COMMS.md using the template, filling in sections from the interview. Use the person's own words and phrasing where possible.\n\nFor reference on what a completed COMMS.md looks like, see references/example.md." }, { "title": "4. Review and Iterate", "body": "Present the draft and ask what feels off, what's missing, what's too specific or too vague. Expect 1-2 revision rounds. Common adjustments:\n\nTone too formal or too casual for how they actually talk\nMissing a channel or context they care about\nWeekly rhythm needs more nuance\nAnti-patterns section needs real examples" }, { "title": "5. Place the Document", "body": "Ask where they want it saved. Common locations:\n\nPersonal website (for public/professional use)\nNotes app or vault (Obsidian, Notion, etc.)\nWorkspace docs (for team use)" }, { "title": "Related Skills", "body": "comms-md-reader — the companion skill for reading and adapting to someone else's COMMS.md when drafting outreach" }, { "title": "Guidelines", "body": "Use their voice. The doc should sound like them, not like a template. Mirror their register.\nEarn specificity. Generic preferences (\"I prefer email for professional stuff\") are less useful than specific ones (\"Email for intros beyond close friends and anything they'll need to find later\").\nSkip irrelevant sections. Not everyone has a weekly rhythm to document or sync philosophy to articulate. Leave out what doesn't apply rather than filling with filler.\nThe Async Voice section is the highest-value section for agent consumption. Spend extra time here. This is what another agent reads to calibrate tone when drafting a message to this person.\nVersion the output. Include Version 0.1 at the bottom so they can track iterations." } ], "body": "COMMS.md Creator\n\nGenerate a structured communication preferences document through guided conversation.\n\nWhat COMMS.md Is\n\nA queryable personal document that expresses how someone communicates: their natural style, channel preferences, availability rhythms, async voice, and interaction protocols. Designed to be read by both humans and agents before initiating contact.\n\nWorkflow\n1. Orient\n\nExplain the concept briefly:\n\n\"A COMMS.md is a structured doc that captures how you communicate — your style, when you're available, which channels you prefer, how you write in different contexts. Think of it as a user manual for reaching you. Other people (or their agents) can reference it before getting in touch.\"\n\n2. Interview\n\nWalk through these areas conversationally. Don't dump all questions at once — do 2-3 per turn, adapt based on answers, skip what's clearly not relevant.\n\nStyle & strengths (start here — it's introspective and sets the tone):\n\nWhat comes naturally when you communicate? (e.g. brevity, storytelling, humor, directness)\nWhat requires effort? (e.g. small talk, follow-through, emotional labor, context-switching)\nWhere does communication break down for you?\n\nCollaboration model:\n\nWhat kind of people do you work best with?\nHow do you prefer to set up working relationships?\n\nWeekly rhythm:\n\nWalk through their week: energy, availability windows, protected time\nWhich days are meeting-heavy? Which are deep work?\n\nSync philosophy:\n\nWhat are calls for? What are they NOT for?\nHow tactical vs. strategic do calls get?\n\nChannel preferences:\n\nFor each situation type (urgent, professional, casual, etc.): what channel, what timing?\nRole of email vs. text vs. voice notes vs. calls?\nHow does closeness change channel choice?\nNotification habits, response triage, focus mode patterns\n\nAsync voice (this section often needs the most drawing out):\n\nHow do they write to close friends vs. professional contacts?\nCapitalization, punctuation, emoji habits?\nWhat do they never do in writing? (anti-patterns)\nHow do they handle outreach to new people? Re-engaging after silence?\nDo they have a gap between how competent they are and how warm they read? How do they bridge it?\n\nBoundaries:\n\nWhat's the fastest way to annoy them?\nWhat should people never do?\n3. Draft\n\nRead references/comms-template.md for the output structure. Generate the COMMS.md using the template, filling in sections from the interview. Use the person's own words and phrasing where possible.\n\nFor reference on what a completed COMMS.md looks like, see references/example.md.\n\n4. Review and Iterate\n\nPresent the draft and ask what feels off, what's missing, what's too specific or too vague. Expect 1-2 revision rounds. Common adjustments:\n\nTone too formal or too casual for how they actually talk\nMissing a channel or context they care about\nWeekly rhythm needs more nuance\nAnti-patterns section needs real examples\n5. Place the Document\n\nAsk where they want it saved. Common locations:\n\nPersonal website (for public/professional use)\nNotes app or vault (Obsidian, Notion, etc.)\nWorkspace docs (for team use)\nRelated Skills\ncomms-md-reader — the companion skill for reading and adapting to someone else's COMMS.md when drafting outreach\nGuidelines\nUse their voice. The doc should sound like them, not like a template. Mirror their register.\nEarn specificity. Generic preferences (\"I prefer email for professional stuff\") are less useful than specific ones (\"Email for intros beyond close friends and anything they'll need to find later\").\nSkip irrelevant sections. Not everyone has a weekly rhythm to document or sync philosophy to articulate. Leave out what doesn't apply rather than filling with filler.\nThe Async Voice section is the highest-value section for agent consumption. Spend extra time here. This is what another agent reads to calibrate tone when drafting a message to this person.\nVersion the output. Include Version 0.1 at the bottom so they can track iterations." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/stedmanhalliday/comms-md", "publisherUrl": "https://clawhub.ai/stedmanhalliday/comms-md", "owner": "stedmanhalliday", "version": "1.0.1", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/comms-md", "downloadUrl": "https://openagent3.xyz/downloads/comms-md", "agentUrl": "https://openagent3.xyz/skills/comms-md/agent", "manifestUrl": "https://openagent3.xyz/skills/comms-md/agent.json", "briefUrl": "https://openagent3.xyz/skills/comms-md/agent.md" } }