Security audit

Church Event Planner

Security checks for vulnerabilities and agentic risk

Overview

This is a local church event-planning skill that clearly describes its data tracking, but users should be careful because it stores volunteer contact details, preferences, availability, and workload notes in a persistent file.

Install only if you are comfortable keeping church event, vendor, and volunteer information in a local event-data.json file. Avoid storing unnecessary sensitive details, get volunteer consent for contact and preference data, periodically delete stale records, and use explicit church-related prompts to avoid accidental activation.

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The example trigger "What's coming up?" is overly broad and lacks any church- or event-planning scope, which can cause the skill to activate in unrelated conversations. In an agent environment, ambiguous triggers increase the chance of unintended data access, irrelevant workflow execution, or interference with other skills when users ask generic status questions.

Vague Triggers

High

Confidence: 96% confidence
Finding: The skill’s trigger guidance is extremely broad and includes ordinary conversational phrases, which can cause the skill to activate in contexts where the user did not intend event-planning automation. Because the skill is instructed to read and write persistent church event and volunteer data, unintended invocation could expose or modify sensitive operational and personal information without clear user intent.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The skill persistently stores volunteer names, phone numbers, availability, preferences, burnout assessments, and event participation history, but provides no user-facing notice, consent flow, retention limits, or handling guidance for sensitive personal data. This creates privacy and compliance risk, especially because some stored fields reveal sensitive inferences about health, workload, and personal constraints.

Static analysis

No suspicious patterns detected.