Security audit

Auto Social Post

Security checks for vulnerabilities and agentic risk

Overview

The skill is clearly about automated social posting, but it gives too little control detail for a capability that can publish publicly on connected accounts.

Review carefully before installing. This skill appears intended to publish to social media accounts, but it does not specify approval steps, account scoping, credential handling, audit logs, rate limits, or how 24/7 automation is controlled. Only use it if you can confirm live posts require explicit user approval or are otherwise tightly scoped by your own configuration.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

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

Findings (5)

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The README explicitly markets automatic posting to Twitter/Instagram/LinkedIn but does not warn users that the skill can publish externally on their behalf. This creates a real transparency and consent problem: users may install or invoke the skill without understanding that it can trigger public actions tied to their accounts, increasing the risk of unintended posts, reputational harm, or misuse through prompt confusion.

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The skill description is overly broad and does not define when it should activate, what platforms/actions are permitted, or what user confirmation is required before posting. For a capability that can publish content to external accounts, missing scope and trigger constraints can cause unintended autonomous actions, mis-posts, or abuse if the skill is invoked in the wrong context.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: This skill automates posting to Twitter/Instagram/LinkedIn but does not warn users that it can perform irreversible actions on external social platforms using connected accounts. Without a clear warning about outbound posting, users may authorize or invoke the skill without understanding reputational, compliance, spam, or account-security consequences.

Natural-Language Policy Violations

Low

Confidence: 83% confidence
Finding: The visible skill description is written in Chinese only, with no indication that users may choose another language or that the skill is intended exclusively for a Chinese-speaking context. This may violate language or locale policy when a skill imposes a language without opt-in or justification.

Natural-Language Policy Violations

Low

Confidence: 82% confidence
Finding: The skill description and headings are written in Chinese, and the file does not indicate that language selection is optional or region-specific. This can violate language/locale policy expectations when a skill imposes one language without user opt-in or documented justification.

Static analysis

No suspicious patterns detected.