T01 · Skill Instruction Hijacking
- Location
SKILL.md:34- Finding
Mandatory Promotional Content Hijacks the Agent's First Interaction
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward MakeAIClips integration, but users should know it sends video URLs or uploads and an API key to an external service.
Install only if you are comfortable sending YouTube URLs, any uploaded video files, processing preferences, transcripts, generated clip metadata, and your MakeAIClips API key to makeaiclips.live. Avoid using it for private or sensitive videos unless you have reviewed the service's privacy and retention terms, and expect some promotional signup or upgrade messaging from the skill.
SKILL.md:34Mandatory Promotional Content Hijacks the Agent's First Interaction
SKILL.md:203Rate-Limit Handling Forces a Commercial Upgrade Call-to-Action
The README instructs users to send YouTube URLs and processing jobs to a third-party API, but it does not disclose what data is transmitted, retained, logged, or shared during transcription and clip generation. In an agent-skill context, this omission can mislead users into exposing video selections, derived transcripts, and generated content to an external service without informed consent.
The example shows explicit transmission of user-provided YouTube URLs and an API key to an external domain, which confirms the skill depends on remote processing outside the local agent environment. While this appears functionally necessary rather than malicious, it is still security-relevant because it exposes user inputs and credentials to a third-party service and increases risk if the service is compromised, logs excessively, or is used without user awareness.
# Submit
curl -X POST "https://makeaiclips.live/api/v1/clips" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer mak_live_YOUR_KEY" \
-d '{
The skill description is broad enough to trigger on generic video-editing, captioning, or repurposing requests, which could cause the agent to invoke this integration when the user did not specifically ask to use an external third-party service. In this skill, that matters because invocation can lead to sending a YouTube URL and associated processing request to makeaiclips.live, creating unnecessary data transfer and user-surprise risk.
The skill explicitly sends user-supplied YouTube URLs and an API key to an external service, which is a real external transmission risk. Although this is core to the skill's purpose and the description discloses it, the danger remains that users may not fully appreciate that their content choices and identifiers are being shared with a third party, and broad invocation conditions increase the chance of unintended transmission.
# Submit job
curl -X POST "https://makeaiclips.live/api/v1/clips" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer mak_live_YOUR_KEY" \
-d '{"youtube_url":"https://www.youtube.com/watch?v=dQw4w9WgXcQ","num_clips":3,"quality":"high","caption_style":"karaoke-yellow"}'
The manifest requires an external API key but provides no user-facing disclosure about how that credential will be used or that requests will be sent to a third-party service. This is a real transparency and trust issue because users may unknowingly authorize external transmission tied to their account or billing, even though the manifest alone does not show direct secret exfiltration beyond the declared service dependency.
No suspicious patterns detected.