other
- Location
SKILL.md:567- Finding
Automatic Newsletter Enrollment Without Explicit Consent
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a newsletter strategy guide with no executable behavior, though users should revise one growth tactic to require explicit subscriber consent.
Installers should understand this skill as a marketing and newsletter-writing playbook, not an automation tool. Before following the subscriber-growth tactics, replace automatic enrollment with clear, optional opt-in consent, keep unsubscribe handling in place, and review applicable email marketing and privacy rules for the target jurisdiction.
SKILL.md:567Automatic Newsletter Enrollment Without Explicit Consent
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# Newsletter Creation & Curation
A comprehensive skill for creating, structuring, and curating email newsletters for B2B SaaS companies.
The README says users can 'simply mention newsletter-related tasks' and that the system will 'automatically' use the skill, but it does not define clear activation boundaries or non-goals beyond a general limitations section. In an agent environment, overly broad trigger language can cause the skill to activate in loosely related contexts, increasing the chance of inappropriate influence on responses or unintended workflow selection.
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.
ADVANTAGES:
✅ No approval needed (publish freely)
✅ Personal voice = authentic
✅ Company brand = personal brand
✅ Can share metrics ("We're at $5M ARR")
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.
CHALLENGES:
⚠️ Company may want control over messaging
⚠️ Can't share company metrics without approval
⚠️ Must add "Views are my own" disclaimer
⚠️ Manager needs to be aware
The guidance instructs users to use Indian companies, rupee pricing, and Indian regulations as the default for the India strategy, which is a locale constraint expressed in imperative language. Because the document elsewhere routes users by geography rather than offering flexible locale selection at the point of use, this can violate language/locale policy expectations when users have not explicitly opted in to localized conventions.
No suspicious patterns detected.