T03 · Remote Payload Retrieval and Execution
- Location
scripts/check_dependencies.sh:36- Finding
Unpinned Remote Installer Piped Directly to Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This schedule skill is mostly purpose-aligned, but it gives agents direct access to create, modify, and delete Calendar and Reminders data with weak safeguards around destructive actions.
Install only if you are comfortable granting the invoking terminal access to your Calendar and Reminders. Before allowing delete, complete, or bulk planning actions, ask the agent to show the exact matching items and require explicit confirmation. Consider avoiding the third-party reminders-cli dependency unless you trust its source, and inspect any Homebrew installer command before running it.
scripts/check_dependencies.sh:36Unpinned Remote Installer Piped Directly to Bash
scripts/check_dependencies.sh:16Unpinned Security-Sensitive Dependency from a Third-Party Homebrew Tap
SKILL.md:108Calendar Deletion Uses a Non-Unique Title and Can Remove Multiple Events
The trigger phrases are broad everyday language such as ‘记一下’, ‘别忘了’, ‘todo’, and ‘schedule’, which can cause the skill to activate in contexts where the user did not intend calendar or reminder actions. Because the skill performs real shell-backed reads and writes to Calendar and Reminders, accidental activation can lead to unintended data creation, modification, or disclosure.
The skill invokes shell-capable tools (osascript, reminders-cli) but does not declare an explicit tool scope such as permissions or allowed-tools. That makes execution boundaries ambiguous and increases the risk of unintended command execution or overbroad agent authority when the skill is triggered.
The skill documents destructive delete operations for calendar events without an adjacent warning, confirmation requirement, or safe targeting guidance. The example deletes every event whose summary matches a string, which can remove multiple items at once and cause irreversible user data loss if used imprecisely.
The document provides a direct example for deleting an entire calendar without any warning, confirmation step, or emphasis that the action permanently removes calendar data. In a skill designed to manage schedules via osascript, this increases the chance that an agent or user will reuse the example in an unsafe way and cause destructive data loss.
The event deletion examples show bulk deletion by title or date range but omit any warning that all matching events will be permanently removed. In the context of an automation skill that triggers on natural-language scheduling requests, ambiguous matching or accidental invocation could delete multiple legitimate events and cause meaningful data loss.
The document includes a direct list deletion example with no warning, confirmation step, or guidance about irreversible data loss. In a skill designed to automate Reminders actions, this omission increases the chance that an agent or user applies the command to real data without understanding the destructive consequence.
The reminder deletion examples demonstrate permanent removal of reminders, including completed items, without cautionary language or safeguards. Because this skill targets task and schedule management, an agent may operationalize these snippets against a user's live reminders, causing unintended loss of productivity data.
The bulk completion example modifies many reminders in one operation without warning about mass state changes or how to verify the selection. In the context of a GTD/calendar management skill, this can silently alter a large portion of a user's task system and undermine trust, accuracy, and downstream planning.
The guide explicitly documents state-changing and destructive commands such as completing, uncompleting, and deleting reminders without any caution that they modify or permanently remove user data. In this skill context, the agent is intended to manage Apple Reminders directly, so undocumented destructive operations increase the risk of accidental data loss or unsafe automation when the model follows the reference blindly.
The cross-project planning workflow instructs the agent to scan ~/code/*/planning/schedules/*.yaml, which may expose project names, timelines, and capacity data across repositories without clearly warning the user or requesting consent. Even though the path is limited, this is still local file discovery and aggregation of potentially sensitive planning information.
No suspicious patterns detected.