Shift Scheduler

Security checks across malware telemetry and agentic risk

Overview

The skill is mostly coherent for staff scheduling, but its Google Sheets setup guidance could expose private employee schedule data through public-readable links.

Review the data-source setup before installing. Use private, least-privilege access for Google Sheets or files, avoid public schedule links, verify manager-only actions, and set clear retention rules for schedule archives and request history.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

#
ASI03: Identity and Privilege Abuse
Medium
What this means

Employee names, work times, locations, and possibly manager contact details could be exposed outside the intended store or organization if a public Google Sheet link is used.

Why it was flagged

The skill only needs authorized schedule access, but this setup option can make staff schedule data and possible contact details readable to anyone with the link.

Skill content
Share a public-read link or service account access ... "staff_name": "张三" ... "phone": "138..."
Recommendation

Do not use public-read links for staff schedules. Prefer a private sheet shared only with authorized users, a least-privilege service account, or a locally scoped file.

#
ASI02: Tool Misuse and Exploitation
Low
What this means

Incorrect approval or mistaken input could change staff schedules or notify the wrong people.

Why it was flagged

The skill is designed to update schedules and notify employees, but it explicitly places activation behind manager confirmation.

Skill content
店长确认 → 更新排班表 → 通知双方 ... Confirm with manager before activating
Recommendation

Require explicit manager confirmation, verify the requester’s role, review parsed schedule changes before activation, and keep a rollback archive.

#
ASI06: Memory and Context Poisoning
Low
What this means

Old or incorrect schedule history could be reused in later decisions, and retained employee scheduling data may need privacy controls.

Why it was flagged

The skill expects persistent schedule records, time-off/swap status, archives, and history, which are useful but sensitive employee data.

Skill content
Track request status; notify when approved/denied ... 记录换班历史(避免频繁换班模式) ... Archive previous schedule
Recommendation

Define retention limits, restrict who can read archives and request histories, and require validation before old records influence new scheduling decisions.

#
ASI08: Cascading Failures
Low
What this means

A wrong or outdated schedule could route alerts to the wrong manager or delay operational responses.

Why it was flagged

Schedule data is used by other workflows, so schedule errors can propagate into complaint or inventory escalation routing.

Skill content
The shift schedule drives escalation routing in `complaint-handler` and `inventory-query`.
Recommendation

Validate schedules before activation, keep an off-hours fallback contact, and monitor escalation routing after schedule updates.