Execution Plan Splitter
v1.0.0把大目标拆为 30/60/90 天执行路径、阶段成果、资源需求与放弃条件。；use for execution-plan, roadmap, 90-day workflows；do not use for 承诺无法验证的收益, 替代正式预算审批.
⭐ 0· 100·0 current·0 all-time
byvx：17605205782@52yuanchangxing
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description request python3 and local resources; the bundle contains a Python script, templates, and a spec.json that drive structured brief generation. Required binaries and declared resources match the skill's stated purpose (structuring inputs into 30/60/90-day plans).
Instruction Scope
SKILL.md stays on-purpose and cautions not to perform unreviewed system changes. The runtime instructions allow invoking scripts (python3 scripts/run.py) and say to use local resources if execution isn't possible. The provided script accepts files or directories as input and will recursively read and sample text files in a provided directory—so if an agent or user points it at broad system directories it can read many local files and include their contents or metadata in its output. That behaviour is coherent for an audit/brief tool but can surface sensitive data if used carelessly.
Install Mechanism
No install spec; this is instruction-plus-local-script only and requires only python3 (standard library). Nothing is downloaded from external URLs or written to unusual system locations.
Credentials
The skill declares no required environment variables or credentials. The script does pattern scanning for secrets when given input, but requires the user/agent to supply the target path—there are no unexplained secret or credential requests in the manifest.
Persistence & Privilege
always:false and no modifications to other skills or system-wide configs. The skill can be invoked autonomously (disable-model-invocation:false) which is the platform default; this is expected and not by itself a red flag.
Assessment
This skill appears to do what it says: it structures inputs into 30/60/90-day plans using a local Python script and templates. Before running or allowing an agent to run it: (1) review scripts/run.py locally to be comfortable with its behavior; (2) avoid giving it broad system paths (do not point it at /, your home directory, or other sensitive folders); (3) prefer using the examples or a sanitized input file, or use --dry-run; (4) inspect outputs before sharing them externally (the tool may surface snippets from whatever files you pointed it at); (5) run it in a sandbox or restricted environment if you need to audit unknown inputs. If you want stricter guarantees, require the agent to only accept explicit file paths you provide rather than allowing autonomous selection of inputs.Like a lobster shell, security has layers — review code before you run it.
latestvk97bmf2k9d1bfep562wg2tvhb583357h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🪜 Clawdis
OSmacOS · Linux · Windows
Binspython3