Security audit
Security checks for vulnerabilities and agentic risk
This sales-coaching skill is not malicious, but it asks the agent to pull CRM, email, and meeting-note context without clear privacy limits or user confirmation.
Install only if you are comfortable with the agent using sales-related CRM records, email threads, and meeting notes for coaching. Prefer explicit invocation per meeting, limit retrieved records to the deal and participants involved, and avoid displaying raw confidential customer or internal content in shared meeting contexts.
The manifest description says to use the skill 'when Shawn is in a sales meeting,' 'when analyzing a meeting transcript,' or 'when preparing talk tracks for upcoming meetings' without defining explicit trigger phrases, exclusions, or invocation boundaries. In a markdown skill description, this is ambiguous enough to cause unintended activation across many routine sales-assistance contexts.
The skill instructs loading CRM records, email threads, prior meeting notes, and external company research without any data-minimization, consent, or sensitivity-handling guidance. In a live-meeting context, this can cause unnecessary aggregation of personal, confidential, or commercially sensitive data and increase the chance of exposing it in prompts, outputs, or to unauthorized participants.
The trigger list for pricing and budget uses common business terms like 'price', 'cost', and 'budget' without additional gating conditions. In a live-meeting coaching skill, this can cause the card to activate on routine discussion that is not actually a pricing objection, producing misleading real-time guidance and reducing trust in the assistant at decision points.
The competitor trigger relies on broad phrases like 'alternative' and 'compared to' and mixes generic language with specific company names. This ambiguity can trigger competitive-positioning advice during harmless comparison talk, which may steer a seller into unnecessary objection handling or manipulative framing inappropriately.
Buying-signal triggers include ordinary phrases such as 'next steps', 'team involved', and 'who else should see this', which commonly appear in exploratory meetings. Misclassifying these as strong purchase intent is risky in a real-time sales coach because it can prompt premature closing behavior, distort the conversation, and negatively affect customer trust or deal outcomes.
Terms like 'API', 'security', and 'how does it work' are common in many product conversations and do not necessarily indicate a technical deep dive. Overbroad matching in this context may cause the skill to inject overly technical or overconfident guidance at the wrong moment, potentially leading to inaccurate claims or distraction from the buyer's actual concern.
The stalling logic uses vague cues like long pauses, 'interesting', or 'let me think', which are highly subjective and may reflect normal conversational behavior rather than deal risk. In a live coaching setting, false detection can push aggressive recovery tactics at the wrong time, increasing the chance of awkward or manipulative responses and harming the interaction.
Discovery-mode triggers such as 'tell me about' and 'what do you do' are extremely common openings and can occur outside true early-stage discovery. Because this skill gives real-time coaching, over-triggering can cause repetitive or mistimed sales scripts that steer the meeting away from the user's actual context and degrade judgment.
No suspicious patterns detected.
