广泛触发后会自动读取隐藏的产品营销文件
原文依据:3 处技能要求在提问前检查并读取多个固定名称的本地营销文件。由于触发范围包括一般的“我该写什么”等请求,用户可能没有意识到一次普通规划会访问现有项目中的内部背景资料。
若文件包含未公开的客户画像、产品定位、销售信息或商业计划,这些内容可能进入模型上下文并被用于回答;若回答随后被复制或分享,相关信息可能被间接披露。文件中没有自动上传或外发指令,因此风险取决于文件内容和回答的使用方式。
当该技能因“内容想法”等宽泛请求触发时,它会先检查并读取项目中若干固定名称的营销背景文件;用户不必在当次请求中明确提供这些资料。文件内容可能包含客户、产品定位或内部业务信息,并会影响后续建议。证据未显示上传或对外发送。用户可要求作者在读取前列出目标文件并征得确认,或将技能限制在不含敏感营销资料的工作区。
**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.查看另外 2 个位置
---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: