Community Manager
v1.0.0Manage online communities with engagement strategies, content planning, and audience growth.
⭐ 2· 761·7 current·7 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (community engagement, content planning, onboarding, metrics) match the instructions: the skill is purely advisory and designed to read/write local 'memory' files under ~/community-manager/. There are no unexplained credentials, binaries, or external services required.
Instruction Scope
Runtime instructions explicitly tell the agent to read and update files in ~/community-manager/ (memory.md, per-community .md files, content/calendar.md, archive/). This is coherent for a local assistant that persists state, but it does grant the skill read/write access to a home-directory subpath. The SKILL.md also references a memory-template.md that is not included; you'll need to supply or inspect that file. The skill states it will not connect to platforms or exfiltrate data.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is downloaded or written by an installer, which minimizes risk from supply-chain installs.
Credentials
No environment variables, binaries, or external credentials requested. The declared config path (~/community-manager/) is proportional to the stated purpose of persisting community memory and calendars.
Persistence & Privilege
The skill is not always-enabled and does not request elevated privileges or access to other skills' configs. Its persistence is limited to a local directory under the user's home, which is appropriate for its purpose.
Assessment
This skill is internally consistent and appears to only store local notes and templates under ~/community-manager/. Before installing or using it: (1) create or inspect the ~/community-manager/ directory and the referenced memory-template.md yourself so you control exactly what is stored; (2) avoid putting PII, private contacts, passwords, or API tokens in the memory files; (3) set restrictive file permissions on the directory if it will hold sensitive operational notes; (4) remember the skill says it will not post on your behalf — posting to Discord/Slack/etc. is manual, so confirm you understand the workflow; (5) if you plan to use this in a multi-user or hosted environment, verify how ~ expands in that environment to avoid accidental shared storage. Overall this looks coherent and low-risk, but treat the local memory as potentially sensitive and review its contents regularly.Like a lobster shell, security has layers — review code before you run it.
latestvk97b5za6ggf4sqm7fbbeqqms3x81et4e
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
👥 Clawdis
OSLinux · macOS · Windows