Ops Shifts

v1.0.0

View and manage shift schedules and team rosters for operations.

0· 107·0 current·0 all-time
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
Name/description (shift scheduling, rosters) match the instructions: the SKILL.md only needs to read/write roster and shift JSON files and present tables. No unrelated credentials, binaries, or services are requested.
Instruction Scope
Runtime instructions are narrowly scoped to creating/reading/writing ~/.ops-commander/teams.json and ~/.ops-commander/shifts.json and presenting tables/coverage checks. This file I/O is appropriate for a scheduling assistant. Note: the skill will store personal/team data locally — the SKILL.md does not instruct transmitting that data externally.
Install Mechanism
There is no install spec and no code files; this is instruction-only so nothing is written to disk by an installer. Lowest-risk install posture.
Credentials
No environment variables, credentials, or config paths outside the stated ~/.ops-commander files are requested. The requested access is proportional to the skill's functionality.
Persistence & Privilege
Skill flags are defaults (not always:true). It does create and maintain its own files under ~/.ops-commander but does not request elevated or cross-skill privileges.
Assessment
This skill is coherent and appears to only manage local roster/shift files. Before installing, consider: (1) these files live in ~/.ops-commander and may contain personal/team information — if sensitive, ensure proper file permissions and backups; (2) the skill will create and overwrite teams.json and shifts.json in that path — check for conflicts with any existing ~/.ops-commander data; (3) the SKILL.md references a 'Pro' offering at skillnexus.dev — the skill does not itself contact that site, but verify the vendor before providing payment or external contact details; (4) because this is instruction-only, inspect the SKILL.md (which you already have) and confirm you're comfortable with local file storage; (5) avoid storing secrets (passwords, API keys) in the roster/shifts JSON. Overall, nothing about the skill's requirements or instructions is disproportionate to a scheduling assistant.

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

latestvk97c0eqkr0e679acd54aej4ryx835dpa

License

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

Runtime requirements

calendar Clawdis

Comments