Broad triggers cause automatic reading of hidden product-marketing files
Source references: 3The Skill instructs the agent to check and read several fixed-name local marketing files before asking questions. Because it also triggers for broad requests such as not knowing what to write, a user may not realize that an ordinary planning request accesses internal project context.
If the file contains non-public customer profiles, positioning, sales information, or business plans, that material can enter the model context and influence the response. It could be indirectly disclosed if the response is copied or shared. There is no instruction to upload or transmit the file automatically, so the risk depends on its contents and use of the response.
When broadly triggered by requests such as “content ideas,” the skill checks and reads several fixed-name marketing-context files before asking questions, even if the user did not explicitly provide them for that request. Those files may contain customer, positioning, or internal business information and will shape the recommendations. The evidence does not show upload or external transmission. A user can require confirmation and disclosure of the exact file before access, or run the skill only in a workspace without sensitive marketing material.
**Check for product marketing context first:**If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.Show 2 other places
---name: content-strategydescription: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.metadata:name: content-strategydescription: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.metadata: