ClawHub

COMMS.md Creator

v1.0.1

Create a COMMS.md — a structured, queryable document expressing someone's communication preferences for humans and agents. Use when: (1) someone wants to art...

⭐ 0· 573·0 current·0 all-time
byStedman Halliday@stedmanhalliday
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name, description, and provided files (template + example + SKILL.md) align with the stated goal of generating a COMMS.md. No unrelated binaries, env vars, or configs are requested.
✓
Instruction Scope
Runtime instructions are a step-by-step interviewing and drafting workflow limited to asking questions, filling a provided template, reviewing with the user, and asking where to save the document. There are no instructions to read arbitrary system files, access credentials, or transmit data to hidden endpoints.
✓
Install Mechanism
No install spec or code files are provided; this is instruction-only, so nothing is written to disk or downloaded by the skill itself.
✓
Credentials
The skill requests no environment variables, credentials, or config paths. The guidance to ask where to save the document mentions external targets (personal website, Notion, Obsidian) but does not itself require or access those services' credentials.
✓
Persistence & Privilege
always is false and the skill has normal user-invocable/autonomous-invocation defaults. The skill does not request persistent agent-level privileges or attempt to modify other skills or system settings.
Assessment
This skill appears coherent and low-risk: it only contains instructions and templates for an interview that produces a COMMS.md. Before installing/using, consider privacy and placement: the generated document may include sensitive preferences or personal examples, so be deliberate about where you (or an agent) save or publish it (personal website vs private vault). The skill itself does not request credentials, but if you instruct your agent to save the COMMS.md into a third-party service (Notion, GitHub, etc.), that will involve separate credentials and permissions — verify those flows and consent before allowing the agent to store or publish the document. If you plan to pair this with automations (e.g., comms-md-reader), confirm access controls so the COMMS.md is shared only with intended parties.

Like a lobster shell, security has layers — review code before you run it.

latestvk972g8n25ehqamd4stnar995wh81nj7n

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments