content-strategy

Security checks across static analysis, malware telemetry, and agentic risk

Overview

This is a coherent content-planning skill; the main things to notice are that it may read a local marketing context file and use web search for research.

This skill appears safe to install for content strategy work. Before using it, check the local marketing context file for sensitive information and be mindful that web-search research may include your business, competitor, or topic names.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

#
ASI06: Memory and Context Poisoning
Low
What this means

Stored business context may influence the strategy the agent produces and may include sensitive company details.

Why it was flagged

The skill incorporates a persistent local project context file into its reasoning. This is specific and relevant to marketing strategy, but the file may contain proprietary product, audience, or customer information.

Skill content
If `.claude/product-marketing-context.md` exists, read it before asking questions.
Recommendation

Review `.claude/product-marketing-context.md` and keep out any information you do not want used during content strategy tasks.

#
ASI07: Insecure Inter-Agent Communication
Info
What this means

Company names, competitor names, topics, or market research terms could be included in external search queries.

Why it was flagged

The skill may direct external web searches using user-provided topics, competitors, or business context. This is expected for content research, but query terms may be sent to whatever search tooling is available.

Skill content
Use web search to find content ideas: ... `site:reddit.com [topic]` ... Use web search to analyze competitor content: `site:competitor.com/blog`
Recommendation

Avoid using confidential project names or sensitive unreleased strategy details in web-search-driven research prompts.