Security audit

Podcast Transcript Mining Authority Positioning

Security checks for vulnerabilities and agentic risk

Overview

This markdown-only skill is coherent for podcast transcript analysis, but users should be careful with transcript sharing and optional publishing integrations.

Before installing, assume podcast transcripts, business context, generated pitches, and repurposed content may be sent to configured third-party services. Use least-privilege API keys, avoid confidential transcripts unless approved, keep WordPress publishing in draft or staging by default, and only configure Slack, Zapier, RSS, Whisper, or WordPress integrations you actually intend to use.

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
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (6)

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 7)May include surrounding context.
md
ACK_WEBHOOK_URL"],"bins":["ffmpeg"]},"os":["macos","linux","win32"],"files":["SKILL.md"],"emoji":"🎙️"}}

Scope Creep

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The manifest advertises WordPress integration in the skill documentation, but the declared required metadata does not consistently surface the credentials and external access that integration depends on. This can cause operators to enable or trust the skill without clear awareness of all external systems it may access or modify, increasing the chance of accidental over-permissioning or unsafe deployment.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The skill describes sending transcripts and related business content to OpenAI, Google Search, Slack, WordPress, and Zapier, but does not clearly warn that user-supplied data may be transmitted to third parties. That creates a meaningful privacy and compliance risk, especially if transcripts contain sensitive business, personal, or contractual information.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The skill documents pushing content directly to WordPress via REST API without clearly warning that it can modify an external site. This raises integrity risk because generated or incorrect content could be published, overwritten, or staged on a production site using stored credentials.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 84% confidence
Finding: Automatic ingestion of podcast RSS feeds can lead to continuous collection and analysis of new episodes without a prominent warning or explicit user confirmation. While the source material is often public, automated monitoring may still create unexpected processing, storage, cost, or policy implications for the operator.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 88% confidence
Finding: The config example sets language: "en", which implies an English-only locale default in natural-language behavior. The document does not state that language is user-selectable or explain why English is required, creating a potential language/locale policy issue.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.