Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md "files": ["SKILL.md"],
Security audit
Security checks for vulnerabilities and agentic risk
This is a single-file customer-intent classification skill, but it encourages broad analysis of customer communications and automated routing/actions without clear privacy and approval boundaries.
Review this skill before installing if you plan to use it on real customer data. Treat customer messages as sensitive, redact PII and secrets, confirm authorization for OpenAI and workflow-tool processing, disable automatic CRM/Slack/customer-impacting actions until reviewed, and avoid relying on the blanket GDPR/CCPA claim without your own compliance controls.
Referenced artifact was not completely inspected
"files": ["SKILL.md"],
The skill description is framed broadly for real-time intent detection across many customer communication channels without defining clear invocation constraints, consent prerequisites, or data-sensitivity limits. In practice, that increases the chance the skill will be used on sensitive customer content by default, including cases where sending data to a third-party model is inappropriate.
The overview promotes analyzing support tickets, DMs, emails, and comments across external platforms, but it does not prominently warn that this content may be sent to a third-party API provider. Because these inputs commonly contain personal, confidential, or commercially sensitive information, omission of an upfront disclosure can lead to accidental data exfiltration and noncompliant processing.
The skill's safety section says it only returns recommendations and does not automatically send messages, but other sections explicitly describe routing to Slack/CRM and triggering follow-up automations. This inconsistency can mislead operators about the degree of automation and human oversight, increasing the risk of unauthorized outreach or autonomous business actions based on imperfect classifications.
Although this line says the skill will not automatically send emails/messages, the broader document repeatedly describes automated routing, notifications, and workflow triggers. That mismatch can conceal autonomous downstream actions taken from model output, which is risky because classification errors can directly affect customer treatment, sales motions, or retention interventions.
### What This Skill WILL NOT Do
❌ **Make final decisions** → Always flag low-confidence classifications for human review (< 65%)
❌ **Automatically send emails/messages** → Returns recommendations only; humans control outreach
❌ **Guarantee perfect accuracy** → Depends on input quality; ambiguous text may score evenly across buckets
❌ **Access customer data without consent** → Requires explicit permission to analyze; doesn't store or log data (unless configured)
❌ **Override business logic** → Recommendations are suggestions, not rules; your playbooks take precedence
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
❌ **Make final decisions** → Always flag low-confidence classifications for human review (< 65%)
❌ **Automatically send emails/messages** → Returns recommendations only; humans control outreach
❌ **Guarantee perfect accuracy** → Depends on input quality; ambiguous text may score evenly across buckets
❌ **Access customer data without consent** → Requires explicit permission to analyze; doesn't store or log data (unless configured)
❌ **Override business logic** → Recommendations are suggestions, not rules; your playbooks take precedence
❌ **Detect sarcasm 100%** → Sarcasm and irony may be misclassified; review high-confidence satire flagged by human reviewers
The document claims no data retention and strong privacy/compliance posture, but elsewhere says classifications may be logged for continuous learning and sent to workflow integrations such as Slack, CRMs, and dashboards. Those conflicting statements can cause users to process customer communications under false assumptions about storage, sharing, and compliance obligations, creating privacy and regulatory exposure.
No suspicious patterns detected.