Security audit

Documentation Writer

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-writing guide with broad activation wording but no hidden code, persistence, or unsafe behavior.

This skill is reasonable to install for documentation work. Review generated docs before publishing so placeholder tokens, example URLs, and sample API keys are not replaced with real secrets or copied into public documentation unintentionally.

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

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The manifest says the skill triggers on broad terms like "documentation" and "readme," and also says "Use when writing docs," without narrowing context or giving exclusion conditions. These phrases are common in ordinary requests and could cause unintended invocation because the file does not define clear scope boundaries or negative examples.
Content: No source excerpt is available for this finding.

External Transmission