跳转到正文
报告库
用途分类 / 内容写作

Content Strategy Skill 安全审计

作者说它能做什么(原文)

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 "

第三方安全检查结论

发现安全风险

已检查文件
4
发现的风险
2
会不会运行危险命令?检查是否下载程序后直接运行、让他人远程控制电脑,或藏起要运行的命令。未发现风险
会不会泄露文件和密钥?检查是否发送含密码或密钥的文件,以及代码里是否直接写了密钥。发现 1 项风险
中风险

广泛触发后会自动读取隐藏的产品营销文件

原文依据:3 处
发现了什么

技能要求在提问前检查并读取多个固定名称的本地营销文件。由于触发范围包括一般的“我该写什么”等请求,用户可能没有意识到一次普通规划会访问现有项目中的内部背景资料。

为什么需要注意

若文件包含未公开的客户画像、产品定位、销售信息或商业计划,这些内容可能进入模型上下文并被用于回答;若回答随后被复制或分享,相关信息可能被间接披露。文件中没有自动上传或外发指令,因此风险取决于文件内容和回答的使用方式。

当该技能因“内容想法”等宽泛请求触发时,它会先检查并读取项目中若干固定名称的营销背景文件;用户不必在当次请求中明确提供这些资料。文件内容可能包含客户、产品定位或内部业务信息,并会影响后续建议。证据未显示上传或对外发送。用户可要求作者在读取前列出目标文件并征得确认,或将技能限制在不含敏感营销资料的工作区。

SKILL.md:14来自说明文档打开原文件
**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 个位置
SKILL.md: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:
SKILL.md:3来自说明文档打开原文件
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:
会不会删除文件或一直在后台运行?检查是否大范围删除文件、改写磁盘,或设置自动启动。未发现风险
会不会绕过安全保护?检查是否跳过网站安全验证、开放过多文件权限,或取消操作前的确认。未发现风险
会不会误导 AI 或隐藏内容?检查工作说明是否要求 AI 忽略你的指令、干扰检查结果,或夹带看不见的文字。未发现风险
会不会偷偷改推广链接或收款方?检查是否强制替换推广链接或收款对象,同时要求隐瞒更改。发现 1 项风险
低风险

外链预算建议依赖单一供应商研究的格式倍数

原文依据:3 处
发现了什么

技能用一项供应商对 B2B SaaS 网站的研究得出“统计汇总页优先于原创研究或终极指南”的方向,并给出具体倍数。文本确实标明该研究只是方向性依据,但所提供材料中没有原始报告链接或方法信息供核验。

为什么需要注意

如果用户把这些倍数当作普遍规律,可能把内容预算转向统计汇总页,而实际行业、网站权重或受众的外链行为并不相同。

技能明确用一项“单一供应商”研究的倍数来建议优先制作统计汇总页,并承认数据仅具方向性。材料没有提供原始报告链接、样本或方法,因此用户若据此分配外链预算,可能高估这些精确倍数对自身行业的适用性。它没有把研究或指南说成无价值。用户可要求作者补充可核验来源和方法,并在投入预算前用自身历史数据或小规模测试验证。

SKILL.md:129来自说明文档打开原文件
When the goal of a piece is backlinks specifically, format choice matters more than production effort. Foundation Inc.'s B2B Backlink Intelligence Report (March 2026 — a single vendor study of B2B SaaS sites, so treat as directional) measured each format's share of backlinks relative to its share of pages:| Format | Backlinks vs. page share ||---|---|| Statistics / data roundups | **4.25x** || Glossary / definition pages | 1.47x || Interactive tools / calculators (see **free-tools**) | 1.38x || How-to / tutorials | 1.36x || Original research / reports | 0.80x || Ultimate guides | 0.77x || Thought leadership | 0.74x || Templates / frameworks | 0.68x |
查看另外 2 个位置
SKILL.md:142来自说明文档打开原文件
The counterintuitive read: **curating statistics earns ~5x the links of producing original research.** Writers link to whatever makes citation easiest — a maintained stat-roundup page is citation infrastructure, while original research often gets cited *via* the roundups that aggregate it. Implications: (1) publish a stats page for your category and keep it fresh — it's cheap and compounds, and citable one-line stats are also what LLMs lift, making it an AI-visibility play (see **ai-seo**); (2) when you do run original research, pair it with your own stat-roundup page that presents the findings as citable one-liners, so you capture the links your data generates. The formats at the bottom aren't dead — guides, templates, and thought leadership earn their keep on rankings, conversions, and brand. Judge each piece by the job it's for, and don't expect links from formats that don't earn them.
SKILL.md:131来自说明文档打开原文件
| Format | Backlinks vs. page share ||---|---|| Statistics / data roundups | **4.25x** || Glossary / definition pages | 1.47x || Interactive tools / calculators (see **free-tools**) | 1.38x || How-to / tutorials | 1.36x || Original research / reports | 0.80x || Ultimate guides | 0.77x || Thought leadership | 0.74x || Templates / frameworks | 0.68x |

Skill 逻辑拆解

8 个说明模块

该技能主要生成内容战略:收集业务与客户背景,建立内容支柱和主题集群,并按客户影响、产品匹配、搜索潜力和资源需求排序。

查看原文
SKILL.md:17来自说明文档打开原文件
Gather this context (ask if not provided):### 1. Business Context- What does the company do?- Who is the ideal customer?- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)- What problems does your product solve?
SKILL.md:308来自说明文档打开原文件
Score each idea on four factors:### 1. Customer Impact (40%)- How frequently did this topic come up in research?
SKILL.md:333来自说明文档打开原文件
### Scoring Template| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total ||------|----------------------|-------------------------|----------------------|-----------------|-------|| Topic A | 8 | 9 | 7 | 6 | 8.0 || Topic B | 6 | 7 | 9 | 8 | 7.1 |Score 1-10 per factor, multiply by the weight, sum for the total. Rank the list; make the top-scoring pieces first.

它会处理用户提供的关键词导出、销售或客户通话记录以及调查数据,并从中提取主题、痛点、异议、竞品信息和原话引用。

查看原文
SKILL.md:231来自说明文档打开原文件
If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:- Topic clusters (group related keywords)- Buyer stage (awareness/consideration/decision/implementation)- Search intent (informational, commercial, transactional)- Quick wins (low competition + decent volume + high relevance)- Content gaps (keywords competitors rank for that you don't)
SKILL.md:243来自说明文档打开原文件
If user provides sales or customer call transcripts, extract:- Questions asked → FAQ content or blog posts- Pain points → problems in their own words- Objections → content to address proactively- Language patterns → exact phrases to use (voice of customer)- Competitor mentions → what they compared you toOutput content ideas with supporting quotes.
SKILL.md:254来自说明文档打开原文件
If user provides survey data, mine for:- Open-ended responses (topics and language)- Common themes (30%+ mention = high priority)- Resource requests (what they wish existed)- Content preferences (formats they want)

分发建议是规划性指导:将一份核心内容拆分到社交、邮件等渠道,并把流量引回自有渠道。提供的文件没有脚本、安装步骤或自动发布指令。

查看原文
references/content-distribution.md:60来自说明文档打开原文件
1. **Create** one exceptional flagship piece (guide, video, podcast, original research), with distribution hooks built in.2. **Atomize** it into channel-native cuts—clips, threads, carousels, quote graphics, email, subhead-posts.3. **Distribute** across owned → rented → borrowed, routing everything back to owned.4. **Engage** with the responses; capture the questions, objections, and reactions.5. **Feed back** — the engagement surfaces the next flagship topic (what resonated, what got asked), and top-performing atoms signal what to make more of.

CMS 参考资料建议使用草稿—审核—批准—发布流程,并区分作者、编辑和管理员权限;它没有要求向技能提供访问令牌。

查看原文
references/headless-cms.md:80来自说明文档打开原文件
### Draft → Review → Publish Cycle1. **Draft** — Author creates or edits content2. **Review** — Editor reviews for accuracy, brand voice, SEO3. **Approve** — Stakeholder signs off4. **Schedule** — Set publish date/time5. **Publish** — Content goes live via API
references/headless-cms.md:98来自说明文档打开原文件
### Roles and Permissions| Role | Can Create | Can Edit | Can Publish | Can Delete ||------|:----------:|:--------:|:-----------:|:----------:|| Author | Yes | Own | No | Own drafts || Editor | Yes | All | Yes | Drafts || Admin | Yes | All | Yes | All |Exact permission models vary by platform. Sanity uses role-based access. Contentful has space-level roles. Strapi has granular RBAC.
从这里开始 · 工作说明SKILL.md
content-strategy
连线表示工作说明包含的模块,不是实际运行顺序。点击模块可查看原文。 另有 7 个章节,可在原文件中查看。

文件引用关系图

2 处引用
哪些文件发起引用引用了什么
连线表示真实的文件引用,不是运行顺序。点击节点可高亮相关连线,并查看具体文件和原文位置。虚线表示还有文件需要定位。
文件与检查记录4 个文件

检查范围与遗漏

逐文件查看涉及的内容

下方列出本次涉及的原文范围;纳入检查不代表已查清所有问题。

  • SKILL.md已纳入全文
  • references/content-distribution.md已纳入全文
  • references/headless-cms.md已纳入全文
  • evals/evals.json已纳入全文

这份报告只针对上方版本。我们看了拿到的代码和说明文件,没有实际运行 Skill,也没有检查它另外安装的软件包。因此,这不是“保证安全”的承诺;换了版本或使用环境,结果也可能不同。

  • SKILL.md工作说明
  • evals/evals.json配套文件
  • references/content-distribution.md配套文件
  • references/headless-cms.md配套文件
读取了多少行
836
文件校验值(用于核对版本)
af6548e5e98c54fa10e0eec8bfaaef9a5a950b5e49d9596d8326daa2a98f1ad2