Security audit
Security checks for vulnerabilities and agentic risk
This skill automates disclosed client-onboarding work across files, email, calendar, tasks, reminders, and a client registry, with risks that are expected for that purpose.
Before installing, confirm where client folders and registries will be stored, review recipients and message bodies before sending email, and be mindful that client contact details, budgets, project status, reminders, and templates may persist in workspace memory or local/cloud files.
The invocation phrases are broad enough to capture common project-management or status requests, which can cause the skill to activate in contexts where the user did not intend onboarding automation. Because the skill performs side-effecting actions across storage, email, calendar, and task tools, overbroad triggering increases the risk of unintended writes, messages, and scheduling operations.
The skill creates folders and saves project documents to local or cloud storage without an explicit user-facing notice that persistent file writes will occur. In practice, this can expose sensitive client information to unintended locations, shared drives, synced folders, or misconfigured local paths, especially when the base path or cloud destination is only implied.
The skill drafts or sends email using extracted client contact information without clearly warning that personal data will be transmitted to an external email system. This creates privacy and misdelivery risks if the extracted address is wrong, if the user did not expect outbound communication, or if the email is sent automatically with incomplete review.
The skill stores a client registry, business configuration, and contact/project metadata in workspace memory or files without clearly disclosing persistent retention. This can accumulate sensitive business and personal information over time, increasing exposure from unauthorized access, cross-task reuse, oversharing in later prompts, or insecure local/cloud storage.
The manifest describes onboarding across email, calendar, file storage, task management, and client/project tracking tools. At L235-L236, the documentation says users can configure onboarding templates to also perform GitHub repo setup and Slack channel creation, adding engineering collaboration capabilities not declared in the manifest's stated purpose or tool scope.
No suspicious patterns detected.
