Think-Plan
v1.0.0深度思考与规划 Skill。用于复杂任务的需求挖掘、方案设计和执行规划。 触发场景： 1. 用户说"帮我规划一下..."、"我想做一个..."、"分析一下这个方案" 2. 用户明确说"使用 think-plan"或"用思考规划 Skill" 3. 用户提出的任务需求不清晰、需要梳理 4. 用户需要多个可选方案对比...
⭐ 0· 54·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (deep planning, requirement elicitation, multi-option design) match the SKILL.md and the included reference files. It does not request unrelated binaries, env vars, or external services.
Instruction Scope
Runtime instructions are focused on elicitation, producing 2-3 plans, and executing them. It tells the agent to read local reference files and to write chosen plans to workspace/plans/YYYYMMDD-[task-name].md, and to spawn subagents via sessions_spawn for multi-agent execution. These actions are coherent with a planning skill but you should be aware it will create files in the agent workspace and may spawn child sessions. The SKILL.md does not mention filename sanitization (risk: task-name could be used to craft harmful path names).
Install Mechanism
Instruction-only skill with no install spec, no external downloads, and no code files — lowest-risk install footprint.
Credentials
The skill requests no environment variables, no credentials, and no config paths. All required resources are the bundled reference docs and the agent runtime features (file writes, sessions_spawn), which are proportionate to the described functionality.
Persistence & Privilege
always:false (not force-included). The skill writes plan files into workspace/plans and can spawn subagents (sessions_spawn). Both are reasonable for execution but increase runtime privileges compared with a read-only assistant — review whether automatic file writes and spawning are acceptable in your environment.
Assessment
This skill appears to do what it says: deep requirement digging, 2-3 option plan generation, and optional execution via child agents. Before installing, consider: (1) It will write plan files into the agent workspace (workspace/plans/YYYYMMDD-[task-name].md) — ensure that writing to that location is acceptable and that filenames will be sanitized to avoid path traversal. (2) It uses sessions_spawn to create subagents for multi-agent execution — confirm your runtime's policy for spawned sessions (what they can access, whether they make external network calls, and whether their activity is auditable). (3) The skill will be deliberately critical of user assumptions (by design). (4) No credentials or external installs are requested. If you need extra assurance, ask the skill author to (a) explicitly sanitize task-name when creating filenames, (b) limit/confirm the maximum number of spawned subagents, and (c) document any external network access those subagents might perform.Like a lobster shell, security has layers — review code before you run it.
latestvk97dfkg5409ndg2ej5eftdedw184h3fx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.