v1.0.1

Qsr Daily Ops Monitor

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 7:44 AM.

Analysis

The provided artifacts show a coherent instruction-only restaurant checklist skill, with the main user-notice items being recurring reminders and stored operational check history.

GuidanceBefore installing, decide who is allowed to respond to checks and receive summaries, configure the schedule carefully, and set expectations for how long check history and employee-related notes should be retained.

Findings (2)

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.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Rogue Agents

SeverityLowConfidenceHighStatusNote

SKILL.md

Scheduling — use OpenClaw cron to initiate checks at configured times. If cron is unavailable, prompt via messaging channel. ... if no response within 30 minutes, send one reminder.

The skill asks for recurring autonomous check-ins and reminders; this is disclosed and bounded but creates ongoing agent activity.

User impactThe agent may continue prompting respondents and logging missed checks on the configured schedule without a fresh manual request each time.

RecommendationSet the schedule deliberately, tell respondents what will be logged, and disable the cron or reminder workflow when no longer needed.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

SKILL.md

Memory format — store each completed check as: [DATE] | [CHECK: opening/midshift/closing] | [PASSED: X/5] | [FAILED: items or "none"] | [RESPONDENT: name/role] | [NOTES: text or "none"]

The skill explicitly keeps an ongoing record of compliance results, respondent identity/role, and free-text notes for future pattern tracking.

User impactOperational issues and employee or shift-related details may persist in agent memory and influence later summaries.

RecommendationConfirm where memory is stored, who can access summaries, and how to edit or delete old entries; avoid recording unnecessary personal details.