Sol Build Session
v1.0.0Framework for focused autonomous work sessions to build, explore, or create a single useful deliverable, then log and commit progress.
⭐ 0· 916·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
The SKILL.md describes a build-session framework and the included scripts (pick-task.sh and session-log.sh) directly support that purpose (picking an idea and logging session notes). There are no extra binaries, credentials, or unrelated capabilities requested.
Instruction Scope
Instructions stay on-task (timebox, pick one thing, build, log, commit). The SKILL.md explicitly suggests running git add/commit/push; the included session-log.sh runs git status in the workspace. This is expected for a workflow skill but means the agent may use the user's git credentials/network when following commit/push steps — review before allowing pushes.
Install Mechanism
No install spec; the skill is instruction-only with two small shell scripts. Nothing is downloaded or written by an installer, minimizing install-time risk.
Credentials
The skill declares no required environment variables. The scripts optionally honor OPENCLAW_WORKSPACE (defaulting to $HOME/.openclaw/workspace) which is proportional to their purpose. No secrets or unrelated service credentials are requested.
Persistence & Privilege
always is false and the skill does not request persistent system-wide modifications. The scripts create and write to a per-workspace memory directory (expected behavior for a logging helper).
Assessment
This skill appears benign and does what it says: help structure build sessions and log them. Before installing or running: 1) Confirm OPENCLAW_WORKSPACE points to an intended directory (defaults to ~/.openclaw/workspace). 2) Understand that following the SKILL.md's 'Commit' step (git add/commit/push) will use your git credentials and may push data to remote repositories — review changes before pushing. 3) Inspect the two small shell scripts (they only read/write local files and run git status) and ensure your project-ideas.md and workspace contain only the data you want the agent to access. If you want to avoid network pushes, skip the push step or constrain the agent's permissions.Like a lobster shell, security has layers — review code before you run it.
latestvk97f0q0fv4gw0y4zyx5qnamzh580szg6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.