Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
openclaw-behavior-plan
v1.0.0Generates structured behavior plans for OpenClaw agents based on user requirements. Use when the user asks to create a plan, design agent behavior, plan mult...
⭐ 0· 339·0 current·0 all-time
by@umfl
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name and description match the instructions: it produces structured behavior plans mapped to tools/skills (search_web, read_file, execute_shell, calendar, slack, etc.). It does not request unrelated binaries, env vars, or installs.
Instruction Scope
SKILL.md explicitly instructs the agent to generate actionable steps that may call read_file, write_file, execute_shell, fetch_url, and external skills (calendar, slack). This is coherent for a planning tool, but it means generated plans can ask to read local files or run shell commands — sensitive operations that require explicit user consent before execution. The skill itself does not attempt to exfiltrate data or call hidden endpoints.
Install Mechanism
No install spec and no code files — lowest-risk instruction-only skill. Nothing will be written to disk by an installer.
Credentials
The skill declares no required environment variables or credentials. Example plans reference third-party skills (calendar, slack) which legitimately require user authorization; those credentials are not requested by this skill itself.
Persistence & Privilege
always:false and no persistence or configuration changes are requested. The skill does not ask to modify other skills or system-wide settings.
Assessment
This skill appears to do what it says — it generates step-by-step plans that may reference tools which can read files or run shell commands. Before installing or invoking it, decide whether you will allow plans generated by the skill to access local files or execute commands. If you expect the agent to interact with calendars, Slack, or other services, grant those integrations only through the official connectors and avoid pasting secrets directly into prompts. Require explicit user confirmation before allowing any plan step that modifies or deletes system files or sends sensitive data to external endpoints.Like a lobster shell, security has layers — review code before you run it.
latestvk9798bawa6tmnkv11ewtysbsdh821cmn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
