Slot

v2.0.3

Use when managing time slots, creating schedule blocks, detecting booking conflicts, exporting calendars, or applying scheduling templates for appointments.

0· 99·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (time slots, conflict detection, exports, templates) match the provided SKILL.md and the Bash implementation: creating/listing/checking/exporting slots and applying templates. There are no unrelated credentials, services, or surprising dependencies requested.
Instruction Scope
Runtime instructions are limited to running scripts/script.sh with explicit commands. The script only reads/writes a local CSV in $SLOT_DATA_DIR or $HOME/.slot-manager and uses standard shell utilities. Minor note: the script references an optional SLOT_DATA_DIR environment variable (used to change storage location) but SKILL.md does not document this optional env var.
Install Mechanism
No install spec or downloads — the skill is instruction-only plus a bundled script, so nothing is pulled from the network at install time. This is low-risk.
Credentials
The skill requires no secrets or declared env vars. The script does use an optional SLOT_DATA_DIR and the HOME variable for storage location. It also invokes external commands (e.g., sha256sum) that are not declared as required binaries in the manifest — this is a minor mismatch but not a sign of data-exfiltration or unrelated credential access.
Persistence & Privilege
always:false and user-invocable:true. The script persists only its own data under ~/.slot-manager (or SLOT_DATA_DIR). It does not modify other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: a local Bash-based scheduler that stores slots in a CSV under $HOME/.slot-manager (or a directory you set with SLOT_DATA_DIR). Before installing or running: 1) Note that data is stored locally — inspect ~/.slot-manager if you care about privacy or backups. 2) The script calls sha256sum to generate IDs; if your system lacks sha256sum (macOS may use shasum/coreutils), install the appropriate utility or adjust the script. 3) No network calls or credential requests are present, and the skill does not request special privileges. 4) As always, review the script contents and set SLOT_DATA_DIR if you want storage in a specific location.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ftbk2r7bczmg6e25mv48r0983mc1m

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments