Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
swarma - growth loops
v1.0.0Agent teams that run growth experiments and build their own playbook. GROWS loop: generate hypothesis, run experiment, observe signal, weigh verdict, stack p...
⭐ 0· 45·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (growth experiment loops, agent teams) match the SKILL.md functionality (teams, cycles, scoring, playbooks). However the registry metadata lists no required env vars or binaries while SKILL.md explicitly requires a runtime (Python/pip/terminal) and an OPENROUTER_API_KEY. The absence of declared runtime/credentials in the registry is an incoherence that should be resolved.
Instruction Scope
SKILL.md contains concrete runtime instructions (CLI commands like swarma cycle, serve, run; read/write strategy.md; import CSV metrics; start REST/MCP server). These are within the skill's stated purpose, but they instruct the agent to run servers and continuous engines and to read/write experiment files. There is no instruction to access unrelated system files or secrets beyond the OpenRouter key, but the instructions give the agent capability to open network endpoints and import arbitrary CSVs which increases risk if left unchecked.
Install Mechanism
No install spec is provided even though SKILL.md lists compatibility (Python 3.11+, pip) and references a GitHub repo. That means an agent following the skill may be expected to install a package at runtime (pip from GitHub or similar). Instruction-only skills that implicitly require installing third-party code increase risk because they can cause arbitrary code to be fetched/executed; the upstream package source and exact install steps are not declared in the registry metadata.
Credentials
SKILL.md declares a single required environment variable (OPENROUTER_API_KEY) for LLM calls, which is proportionate for an LLM-driven experiment runner. However, the registry record lists no required env vars — this inconsistency is concerning and should be clarified. No other credentials or sensitive environment paths are demanded in the SKILL.md.
Persistence & Privilege
The skill does not request always:true and uses the normal autonomous-invocation default. That is not a problem by itself. However, the skill instructs running scheduled engines and starting REST/MCP servers (persistent network-facing processes). If the agent is allowed to invoke this autonomously, those capabilities amplify risk — verify whether you'll allow the skill to run continuously or expose network ports.
What to consider before installing
This skill appears to implement the advertised growth-experiment loop, but there are a few mismatches and practical risks to address before installing:
- Confirm required credentials: SKILL.md requires OPENROUTER_API_KEY for LLM usage but the registry shows no required env vars. Only provide this key if you trust the upstream code and understand its LLM usage and limits.
- Confirm install/source: SKILL.md refers to Python/pip and a GitHub repo but the registry has no install spec. Ask the publisher for an explicit install plan (exact pip package name or vetted release URL) and inspect the repository before running pip install.
- Sandbox runtime installs and servers: Because the skill can start servers (REST/MCP) and a scheduled engine, consider running it in a sandboxed environment (container or VM) and restricting network exposure until you audit the code.
- Review code/repo: Before giving any API keys or allowing autonomous runs, review the repository (https://github.com/glitch-rabin/swarma) or ask the author for a trustworthy release. Look for unexpected network calls, telemetry, or credential exfiltration code.
- Least privilege: Provide only the minimum API key scope needed for OpenRouter (or prefer ephemeral/test keys) and avoid supplying high-privilege secrets (cloud credentials, SSH keys, database passwords).
If the publisher can (a) add an explicit install spec, (b) reconcile registry metadata with SKILL.md (declare OPENROUTER_API_KEY requirement), and (c) provide a vetted release link or package name, that would materially reduce the uncertainty.Like a lobster shell, security has layers — review code before you run it.
latestvk97bgt3875qr3ds155nd6zm7s183tc94
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
