Succession Plan
v2.0.1Design succession plans with role mapping and transition roadmaps. Use when adding positions, listing candidates, prioritizing paths, planning transfers.
⭐ 0· 352·1 current·1 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 and description match the provided scripts and SKILL.md: a simple CLI task/logging tool for succession planning. The scripts only read/write local files under a per-user data directory and provide planning templates. No unrelated services, credentials, or remote endpoints are requested.
Instruction Scope
Runtime instructions and scripts operate within the stated purpose and only touch the declared data directory. However, every command is appended to history.log (timestamped), so sensitive candidate names or confidential notes will be recorded. Also, SKILL.md claims "zero dependencies" in one place but the code requires Bash 4+ and invokes python3 (the Requirements section mentions Bash but not python3), which is a small documentation mismatch to be aware of.
Install Mechanism
No install spec is provided (instruction-only), and included shell/Python scripts are plain text. There is no download-from-URL or package installation step in the manifest. The risk surface is limited to the provided script contents being executed on the user's system.
Credentials
The skill requests no credentials or special environment variables. It supports optional SUCCESSION_PLAN_DIR and honors XDG_DATA_HOME and HOME for data location — these are appropriate for its function.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings, and only creates a per-user data directory (default ~/.local/share/succession-plan). That directory stores data.log and history.log locally.
Assessment
This skill appears to do what it says: a lightweight local CLI planner that logs items and a history of commands to ~/.local/share/succession-plan by default. Before installing or using it: 1) Be aware that history.log will record every command and its arguments (candidate names, assessments, etc.) — avoid logging highly sensitive PII unless you accept local storage. 2) The code calls python3 but the top-level text is slightly inconsistent about dependencies; ensure you have Bash 4+ and python3 available. 3) If you prefer data elsewhere, set SUCCESSION_PLAN_DIR to a secure location and consider filesystem permissions or encryption for confidential records. 4) As with any script, you can review the two provided scripts (scripts/script.sh and scripts/succession.sh) before running them to confirm there are no changes you don’t expect.Like a lobster shell, security has layers — review code before you run it.
latestvk97eq7d390e92bzn2pfd96wd45834zpqproductivityvk9750zg9ff5vkpbb7vgq2z68vs82rc44
License
MIT-0
Free to use, modify, and redistribute. No attribution required.