Security audit

Sv Content Calendar

Security checks for vulnerabilities and agentic risk

Overview

This is a document-only planning skill for short-video content calendars, with no executable code, network access, credential handling, or hidden persistence.

Review the broad trigger terms if you want tighter routing, and treat posting-time or trend-fit recommendations as planning guidance rather than guaranteed performance advice.

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

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 (5)

Vague Triggers

Medium

Confidence: 94% confidence
Finding: The trigger keywords are very generic planning terms such as 'content calendar', 'posting schedule', and 'video planning', which are likely to match ordinary user requests outside the intended skill-routing boundary. This can cause over-triggering of the skill, increasing the chance the agent invokes it in inappropriate contexts and bypasses more suitable workflows or user intent disambiguation.

Vague Triggers

Medium

Confidence: 95% confidence
Finding: The trigger keywords are generic planning terms such as content calendar, posting schedule, and content timeline, which can overlap with many unrelated user requests. In an agent routing system, this can cause over-broad activation, inappropriate skill selection, and unintended exposure of the skill in contexts where a more suitable or safer skill should handle the request.

Natural-Language Policy Violations

Medium

Confidence: 94% confidence
Finding: The manifest sets "language": "en", which indicates the skill is constrained to English. Under the policy rules, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.

Natural-Language Policy Violations

Low

Confidence: 93% confidence
Finding: The checklist explicitly marks 'English-first documentation' as an acceptance criterion. This is a natural-language locale policy constraint, and the file does not indicate that users can choose another language or that the restriction is justified by a region-specific requirement.

Natural-Language Policy Violations

Low

Confidence: 81% confidence
Finding: The file presents one scenario entirely in Chinese and tailored to WeChat Channels, but it does not state that the skill is region-specific or that users may choose their preferred language. This can create an implicit language/locale preference without clear opt-in or justification.

Static analysis

No suspicious patterns detected.