Back to skill

Security audit

blog-outline-writer

Security checks for vulnerabilities and agentic risk

Overview

The bundled skill generates blog outlines locally with proportionate file access; its optional Windows application is separate and unreviewed.

Use a dedicated output directory because outline.md is overwritten, and check the template/input mismatch before relying on results. The optional Windows application is unnecessary for the bundled workflow and needs separate evaluation; its supplied hash alone does not establish safety.

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
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: file_write.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Generated outlines require US-specific content without user opt-in.

Low
Category
Output Handling
Confidence
95% confidence
Finding

Every section is instructed to include a US-specific detail, imposing a regional requirement regardless of the user's intended audience. The file provides neither a locale choice nor a documented justification for restricting content to the US.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.