ClawHub

Message

v1.0.0

Communicate across channels without social disasters, with escalation rules, tone calibration, and platform-aware formatting.

⭐ 0· 839·8 current·8 all-time
byIván@ivangdavila
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
The skill is a guidance/behaviour policy for drafting and sending messages across platforms. It makes no unusual demands (no env vars, no binaries, no installs) and the requested capabilities (tone matching, escalation, platform-aware formatting) align with the description.
ℹ
Instruction Scope
SKILL.md and supporting files are explicit about what the agent should do (e.g., 'read the last 5 messages', 'check you're in the RIGHT chat', 'never auto-send for high-stakes categories'). These are within scope for a messaging assistant, but they imply the agent will need access to message history and the ability to send/schedule messages — the skill itself does not declare or require those platform credentials or APIs. That mismatch is informational (not malicious) — actual integrations/permissions must be obtained elsewhere.
✓
Install Mechanism
Instruction-only skill with no install spec, no downloaded artifacts, and no code files. Low surface area: nothing is written to disk or fetched during install.
✓
Credentials
No environment variables, credentials, or config paths are requested. The lack of requested secrets is proportionate to an instructional policy-only skill.
✓
Persistence & Privilege
always is false and the skill is user-invocable. The skill does not request persistent privileges or to modify other skills. The default ability for the agent to invoke the skill autonomously is normal; the skill's rules explicitly discourage auto-sending for many cases.
Assessment
This skill is a set of best-practice rules and formatting guides — it does not itself connect to your accounts or install code. Before enabling it in a workflow, confirm how your agent will obtain access to message history and sending capability (separate integration or connector). Grant only the minimum permissions needed (read recent history, send/schedule messages), require human review for categories the skill marks as 'never auto-send', and test templates in a safe environment. If you expect the agent to operate autonomously, make sure platform-level controls/logging and explicit user-approval steps are in place for high-stakes messages.

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

latestvk978wf27pctxpnf979gtf4a56h81bav2

License

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

Runtime requirements

💬 Clawdis
OSLinux · macOS · Windows

Comments