Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Openclaw Team Builder
v1.0.0Discover, compose, and activate specialist teams from 3 rosters — OpenClaw Core (CEO/IG/Artist), Agency Division (55+ specialists), and Research Lab (autonom...
⭐ 0· 156·0 current·0 all-time
byJoe Szeles@joeszeles
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The stated purpose is to propose and activate specialist teams (planner/reviewer/orchestrator). That scope does not legitimately explain some capabilities the documents claim: live market access and trade execution (scalper bot control, Config Write API), use of particular models/services (openai/gpt-4o, xAI grok image APIs), and persistent workspaces under .openclaw. A team-composition skill would not itself need direct trading credentials or cloud/model API keys; those are missing from the declared requirements and therefore disproportionate to the stated purpose.
Instruction Scope
SKILL.md and the companion docs instruct agents to read local reference files, adopt other agents' identities, read/write from .openclaw workspaces, 'read current strategy config from IG dashboard', run autonomous Research Lab loops ('LOOP FOREVER'), and promote configs via a 'Config Write API'. The skill's instructions reference external services and system paths outside the skill folder without declaring how to access them, and include an autonomous infinite-loop pattern for experiments which could run indefinitely if invoked.
Install Mechanism
No install spec and no code files are included (instruction-only). This reduces risk from arbitrary downloads or installs. However, the absence of an install step amplifies the other inconsistencies (the skill claims capabilities that would normally require installed clients or credentials).
Credentials
The skill declares no required environment variables or credentials, yet the content repeatedly references services that would need secrets (trading accounts/APIs for IG/scalper control, OpenAI/xAI API access for models and image generation, possible Config Write API credentials). This mismatch (capability claims vs. zero credential requirements) is a key incoherence and could hide assumptions about platform-provided privileges or be an engineering oversight.
Persistence & Privilege
The skill is not flagged always:true and is user-invocable (defaults). That is appropriate. However, internal docs describe 'always running' Core agents and an autonomous Research Lab 'LOOP FOREVER' experiment loop — if activated on a platform that permits long-running/autonomous execution, that could lead to indefinite or repeated actions (including config writes and trading experiments). The skill metadata does not request elevated persistence, but the behavioral docs imply it.
What to consider before installing
This skill is mostly documentation for composing teams, which is fine, but there are important mismatches you should clarify before installing or using it:
- Ask the author how the skill expects to access external services: where do trading credentials, OpenAI/xAI keys, or a 'Config Write API' token come from? The skill declares none.
- Confirm whether the referenced reference/agency-agents-main files and any required workspaces (e.g., .openclaw/workspace/) are actually bundled or available on your platform. The SKILL references many file paths that are not present in the package manifest.
- Be cautious about activating Research Lab workflows: the docs describe an autonomous, indefinite loop that can modify configs and run experiments. If the platform grants the skill live execution or the ability to write configs, this could cause continuous actions against trading systems or other services. Refuse or sandbox such behavior unless you trust the source and have safe limits (rate limits, timeouts, least privileges).
- Do not grant trading or account credentials to this skill unless you fully trust the publisher and have audited how those credentials will be used. Prefer least-privilege API keys and test in a sandbox account.
- If you want to proceed: require the author to add explicit 'required env vars' and an install/usage README explaining how credentials are provided, what external APIs are invoked, and what safety bounds (timeouts, budget limits, experiment caps) protect autonomous loops.
Given the above mismatches (capability claims vs. zero declared credentials and implicit ability to change live configs/trades), treat installation as suspicious until the author explains and fixes these gaps.Like a lobster shell, security has layers — review code before you run it.
latestvk97bx33gyb6rh7s5kewzrwtfa5831444
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
