Flowdo
v2.0.0Task and workflow manager with kanban-style status tracking. Use when you need flowdo.
⭐ 0· 252·0 current·0 all-time
byBytesAgain2@ckchzh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (kanban-style task manager) matches the SKILL.md and the included bash script. The script implements add/list/done/doing/stats-like operations and stores data locally; there are no unrelated capabilities or asked-for services.
Instruction Scope
SKILL.md only documents CLI commands and usage examples. It does not instruct reading arbitrary system files, accessing external endpoints, or exfiltrating data. Runtime behavior (as seen in scripts/script.sh) is limited to local file read/write and simple text operations.
Install Mechanism
No install spec is provided (instruction-only). The included script is a plain bash script (no downloads or package installs). No high-risk install behavior or remote archives are present.
Credentials
The skill requests no credentials or special env vars. The script uses standard environment variables (FLOWDO_DIR, XDG_DATA_HOME, HOME) to decide where to store data. Note: it will write task data and a history log to the chosen data directory, so any sensitive text entered as a task will be stored in those files.
Persistence & Privilege
always:false and the skill does not modify other skills or system-wide settings. It persists only by creating its own data directory (default $XDG_DATA_HOME/flowdo or $HOME/.local/share/flowdo) with data.log and history.log. This behavior is expected for a task manager but is a form of local persistence.
Assessment
This skill appears to do exactly what it says: a small terminal task manager implemented as a bash script that stores data locally. Before installing or running it: (1) review the script (scripts/script.sh) yourself if you want assurance; (2) be aware it will create files under $FLOWDO_DIR (or $XDG_DATA_HOME/flowdo or $HOME/.local/share/flowdo) and log commands/history — avoid putting secrets or passwords into task text; (3) if you prefer a different location, set FLOWDO_DIR to a directory you control; (4) you can inspect file permissions after first run to limit access (e.g., chmod 600 data files). Overall the skill is coherent and low risk.Like a lobster shell, security has layers — review code before you run it.
latestvk9713k2nxq50d3rr7e53fhxsyn832w1w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.