ClawHub

Community Building Playbook

v1.0.1

Community Building Playbook — Build engaged developer and user communities from scratch. Discord community growth, Slack community management, open source co...

⭐ 0· 61·0 current·0 all-time
by@gingiris
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 and description describe community-building guidance and the SKILL.md contains exactly that content (a link to the Gingiris playbook and a short summary). There are no unrelated binaries, env vars, or config paths requested.
ℹ
Instruction Scope
The SKILL.md is minimal and primarily redirects to a public GitHub URL. It does not instruct the agent to read local files, access credentials, or transmit data elsewhere, but it also provides no embedded actionable automation — it's a pointer to external documentation rather than an executable playbook.
✓
Install Mechanism
No install spec and no code files are present. Because this skill is instruction-only, nothing is written to disk or installed by the skill itself.
✓
Credentials
The skill requests no environment variables, keys, or credentials. There is no disproportionate access requested for the stated purpose.
✓
Persistence & Privilege
Defaults are used (always: false, autonomous invocation allowed). The skill does not request persistent or elevated presence beyond normal skill behavior.
Assessment
This skill is essentially a link to a public GitHub playbook and does not request credentials or install software, so it is internally coherent and low-risk. Before installing: (1) check the linked GitHub repository (author, README, LICENSE, recent commits) to ensure the content is what you expect and that the repo is trustworthy; (2) be aware the skill provides guidance only — it doesn't automate actions or integrate with services; (3) monitor future updates to the skill (a later version could add installs or env var requirements); and (4) if you need the agent to act on the playbook content (e.g., fetch or summarize the repo), ask the developer to include explicit, transparent instructions and permissions rather than relying on an external link.

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

latestvk97bx0nem4c2nc5jv6cmf3pmh583tk3g

License

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

Comments