article-content by kostja94/marketing-skills
npx skills add https://github.com/kostja94/marketing-skills --skill article-content指导创建文章正文内容——博客文章、指南和长篇内容中的实际文本(引言、正文、结论)。专注于写什么。关于内容放置位置(页面结构、模式、元数据),请参阅 article-page-generator。关于短篇转化文案(广告、落地页、行动号召),请参阅 copywriting。
调用时:在首次使用时,如果有帮助,可以先用 1-2 句话说明此技能涵盖的内容及其重要性,然后提供主要输出。在后续使用或用户要求跳过时,直接进入主要输出。
质量优于长度:谷歌优先考虑对搜索意图的全面覆盖,而非字数。使长度与主题深度和意图相匹配。
| 类型 | 字数 | 用例 |
|---|---|---|
| 新闻 / 公告 | 300–600 | 产品更新、突发新闻、常见问题解答 |
| 短篇 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 500–800 |
| 落地页、产品页面(可浏览) |
| 标准文章 / 操作指南 | 1,000–1,500 | 单一主题;可操作性强;列表文章 |
| 列表文章 | 1,200–2,000 | "十大"、"最佳 X";编号列表可将点击率提升约 70% |
| 集群文章 | 800–2,500 | 子主题;链接到支柱内容 |
| 支柱 / 基石内容 | 2,000–3,500+ | 全面;集群中心;6–12 个部分 |
| 竞争性关键词 | 1,800–2,500 | 搜索结果第一页的 SEO 文章平均约 2,400 字 |
基于意图(谷歌 2025):验证型 1,200–2,000;探索型 2,000–3,500;比较型 600–1,200;操作型 900–1,500;了解型 300–800。信息型文章比交易型长约 40%。
避免:少于 300 字(内容单薄);超过 7,000 字(通常因焦点分散而表现不佳)。
文章内容基于四个输入。完整工作流请参阅 article-page-generator。
| 输入 | 目的 |
|---|---|
| 产品 | 关联性、功能、行动号召放置位置 |
| 关键词 | 目标关键词、主要/次要关键词 |
| 文章意图 | 信息型、商业型、交易型 |
| 竞争对手文章 | 可借鉴的结构、内容差距、长度目标 |
信息增益 = 一个页面在现有排名靠前结果之外提供的净新增信息。谷歌评估的是独特价值,而非全面性。内容密度(每 100 字中的独特实体、数据点、见解)比字数更重要。摩天大楼技术(越长越好)不再具有区分度;人工智能使得全面性变得廉价。
信息增益的四个来源:
避免共识内容:重复排名前 10 结果中的常见事实 = 零信息增益。写作前审核搜索结果页面;列出"共识层";识别差距(未回答的问题、过时的数据、服务不足的细分领域)。以新内容开头;采用答案优先的结构。
密度检查:计算独特的数据点、原创见解、具体主张。如果新信息与字数的比率较低,则删减填充内容。高密度内容(800-1,500 字,包含 3 个以上原创观点)通常优于冗长的重复指南。
选择其一;放置在引言之后。包含这些元素的内容被 AI 引用的概率高出约 35%。
| 格式 | 规格 |
|---|---|
| TL;DR | 50–100 字的加粗摘要段落 |
| 关键要点 | 5–7 个要点列表 |
完整的 GEO 策略请参阅 generative-engine-optimization。
长度:40–120 字;2–3 个段落。读者约在 8 秒内做出决定;吸引点必须立即生效。
| 元素 | 指南 |
|---|---|
| 吸引点 | 前 1–2 句:痛点、统计数据或问题;好奇心缺口;具体数据或反直觉事实 |
| 主要关键词 | 在前 100 字内 |
| 期望设定 | 说明读者将学到什么 |
吸引点类型:"你做错了 X";"97% 的 Y…";大胆提问;挑战假设。精心设计的吸引点可将点击率提升 30–50%。
| 元素 | 指南 |
|---|---|
| 问答模式 | 问题(H2) → 答案(2 句话) → 证据(数据、示例、列表) |
| 答案优先 | 在每个 H2 标题后的前 40–60 字内给出直接答案 |
| 答案块 | 每部分 100–200 字;直接答案 + 上下文 + 证据 |
| 段落长度 | 40–80 字;2–4 句话;避免大段文字 |
| 拆分长段落 | 每 2–3 个段落使用列表、H3 标题、图片、标注框 |
| 可浏览性 | 前置关键信息(F 型模式);加粗关键短语;每个段落一个核心思想 |
长篇内容(1,000+ 字):每 500–600 字放置一个互动吸引点;混合 40–50% 的解释性文本、20–25% 的示例、10–15% 的数据、5–10% 的可视化内容。
总结 + 行动号召:新闻通讯注册、相关内容、产品(在相关时链接到产品/功能)。与产品关联的内容自然地与产品联系起来。
文章应与产品相关联(它解决的问题、功能、用例)。避免纯粹通用的内容。在结论中或上下文合适时,自然地链接到产品/功能页面。
将文案写作框架应用于文章结构。完整的 PAS、AIDA、BAB 请参阅 copywriting。
| 框架 | 文章用途 |
|---|---|
| AIDA | 引言(注意);正文(兴趣、欲望);结论(行动/行动号召) |
| PAS | 操作指南:引言提出问题;正文激化问题;全文提供解决方案 |
| BAB | 案例研究、转变:之前 → 之后 → 桥梁 |
根据受众选择:AIDA 适用于准备购买者;PAS 适用于痛点驱动者;BAB 适用于寻求转变者。
标题公式(如何、数字、问题→解决方案)请参阅 copywriting。针对文章标题:
| 场景 | 实践 |
|---|---|
| 数据或统计 | 行内引用(例如"根据 Source,72% 的…")或在参考文献部分列出 |
| 专家引述 | 注明出处;链接到来源 |
| 参考文献部分 | 适用于 5 个以上引用;在"相关文章"之前列出 |
| 格式 | 首选行内链接;学术风格使用编号引用 [1]、[2] |
关于 E-E-A-T、作者简介、引用、YMYL,请参阅 eeat-signals。
| 元素 | 指南 |
|---|---|
| 可读性 | 8–10 年级水平(Flesch-Kincaid);短句、清晰语言 |
| 深度 | 与类型匹配;全面覆盖而非填充内容 |
| 原创性 | 独特角度、数据、示例;避免单薄或重复的内容 |
| 信息增益 | 这篇文章增加了排名前 10 结果所没有的什么?反叙事、新数据、专家引述或专有见解 |
| E-E-A-T | 作者简介、引用、专家引述——参见 eeat-signals |
审核或优化文章内容时:
| 维度 | 检查项 |
|---|---|
| 吸引点 | 引言是否以痛点、统计数据或问题开头? |
| 前 100 字内的关键词 | 主要关键词是否存在? |
| 问答模式 | H2 标题是否作为问题?每个部分是否答案优先(40–60 字)? |
| 字数 | 是否符合类型?(新闻 300–600,集群 1,000–2,500,支柱 2,500+) |
| 段落长度 | 每段 40–80 字?没有大段文字? |
| 产品关联 | 是否与产品关联?是否自然地链接到功能/定价页面? |
| 行动号召 | 放置位置(结论、文中);清晰度;产品链接 |
| 参考文献 | 数据/统计是否引用?5 个以上引用是否有参考文献部分? |
| 差距 | 排名靠前的文章涵盖了哪些本文遗漏的内容? |
| 信息增益 | 是否至少具备以下一点:反叙事、新数据、专家视角、专有数据?还是共识内容的重复? |
竞争对手分析请参阅 competitor-research;页面结构和元数据请参阅 article-page-generator。
当内容由 AI 辅助时:发布前需进行人工审核;核实事实并添加引用;包含原创见解或数据;避免通用措辞。关于 E-E-A-T 和 AI 内容指南,请参阅 eeat-signals。
每周安装数
123
代码库
GitHub 星标数
239
首次出现
14 天前
安全审计
安装于
cursor114
gemini-cli112
kimi-cli112
codex112
opencode112
github-copilot112
Guides creation of article body content —the actual text (intro, body, conclusion) for blog posts, guides, and long-form pieces. Focus on what to write. For where it goes (page structure, schema, metadata), see article-page-generator. For short conversion copy (ads, landing pages, CTAs), see copywriting.
When invoking : On first use , if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Quality over length : Google prioritizes comprehensive coverage of search intent, not word count. Match length to topic depth and intent.
| Type | Word count | Use case |
|---|---|---|
| News / announcements | 300–600 | Product updates, breaking news, FAQs |
| Short-form | 500–800 | Landing pages, product pages (scannable) |
| Standard articles / how-tos | 1,000–1,500 | Single topic; actionable; listicles |
| Listicles | 1,200–2,000 | "Top 10," "Best X"; numbered lists boost CTR ~70% |
| Cluster articles | 800–2,500 | Subtopic; links to pillar |
| Pillar / cornerstone | 2,000–3,500+ | Comprehensive; cluster hub; 6–12 sections |
| Competitive keywords | 1,800–2,500 | Page-one SEO posts avg ~2,400 words |
Intent-based (Google 2025): Validate 1,200–2,000; Explore 2,000–3,500; Compare 600–1,200; Do 900–1,500; Know 300–800. Informational ~40% longer than transactional.
Avoid : Under 300 words (thin); over 7,000 (often underperforms due to reduced focus).
Article content rests on four inputs. See article-page-generator for full workflow.
| Input | Purpose |
|---|---|
| Product | Connection, features, CTA placement |
| Keywords | Target keyword, primary/secondary |
| Article intent | Informational, commercial, transactional |
| Competitor articles | Structure to adopt, content gaps, length target |
Information gain = net new information a page provides beyond what exists in top-ranking results. Google evaluates unique value, not comprehensiveness. Content density (unique entities, data points, insights per 100 words) matters more than word count. Skyscraper Technique (longer = better) no longer differentiates; AI made comprehensiveness cheap.
Four sources of information gain :
Avoid consensus content : Restating common facts across top 10 results = zero information gain. Audit SERP before writing; list the "consensus layer"; identify gaps (unanswered questions, outdated data, underserved segments). Lead with what is new; structure answer-first.
Density check : Count unique data points, original insights, specific claims. If ratio of new information to word count is low, cut filler. High-density content (800-1,500 words with 3+ original points) often outperforms long rehashed guides.
Choose one; place after intro. Content with these elements is cited ~35% more by AI.
| Format | Spec |
|---|---|
| TL;DR | 50–100 word bold summary paragraph |
| Key Takeaways | 5–7 bullet points |
See generative-engine-optimization for full GEO strategy.
Length : 40–120 words; 2–3 paragraphs. Readers decide in ~8 seconds; hook must work instantly.
| Element | Guideline |
|---|---|
| Hook | First 1–2 sentences: pain point, stat, or question; curiosity gap; specific data or contrarian fact |
| Primary keyword | In first 100 words |
| Expectations | Set what reader will learn |
Hook types : "You're doing X wrong"; "97% of Y…"; bold question; challenge assumption. Well-crafted hooks boost CTR 30–50%.
| Element | Guideline |
|---|---|
| QAE pattern | Question (H2) → Answer (2 sentences) → Evidence (data, examples, lists) |
| Answer-first | Direct answer in first 40–60 words after each H2 |
| Answer blocks | 100–200 words per section; direct answer + context + evidence |
| Paragraph length | 40–80 words; 2–4 sentences; avoid walls of text |
| Break long blocks | Lists, H3s, images, callout boxes every 2–3 paragraphs |
| Scannability | Front-load key info (F-pattern); bold key phrases; one idea per paragraph |
Long-form (1,000+ words) : Place engagement hooks every 500–600 words; mix 40–50% explanatory text, 20–25% examples, 10–15% data, 5–10% visuals.
Summary + CTA : newsletter signup, related content, product (link to product/feature when relevant). Product-linked content ties to product naturally.
Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content. Link to product/feature pages naturally in conclusion or when context fits.
Apply copywriting frameworks to article structure. See copywriting for full PAS, AIDA, BAB.
| Framework | Article use |
|---|---|
| AIDA | Intro (Attention); body (Interest, Desire); conclusion (Action/CTA) |
| PAS | How-to guides: Problem in intro; Agitation in body; Solution throughout |
| BAB | Case studies, transformation: Before → After → Bridge |
Choose by audience : AIDA for ready-to-buy; PAS for pain-driven; BAB for transformation seekers.
See copywriting for headline formulas (How to, Number, Problem→Solution). For article titles specifically:
| Scenario | Practice |
|---|---|
| Data or statistics | Cite inline (e.g. "According to Source, 72% of…") or in References section |
| Expert quotes | Attribute; link to source |
| Reference section | For 5+ citations; list at end before Related posts |
| Format | Inline links preferred; numbered refs [1], [2] for academic-style |
See eeat-signals for E-E-A-T, author bio, citations, YMYL.
| Element | Guideline |
|---|---|
| Readability | Grade 8–10 (Flesch-Kincaid); short sentences, clear language |
| Depth | Match type; comprehensive coverage over padding |
| Originality | Unique angle, data, examples; avoid thin or rehashed content |
| Information gain | What does this add that top 10 results don't? Counter-narrative, fresh data, SME quote, or proprietary insight |
| E-E-A-T | Author bio, citations, expert quotes — see eeat-signals |
When auditing or optimizing article content:
| Dimension | Check |
|---|---|
| Hook | Intro opens with pain point, stat, or question? |
| Keyword in first 100 words | Primary keyword present? |
| QAE pattern | H2s as questions? Answer-first (40–60 words) in each section? |
| Word count | Matches type? (300–600 news, 1,000–2,500 cluster, 2,500+ pillar) |
| Paragraph length | 40–80 words per paragraph? No walls of text? |
| Product connection | Ties to product? Natural links to features/pricing? |
| CTA | Placement (conclusion, mid-article); clarity; product link |
| References | Data/stats cited? Reference section for 5+ citations? |
| Gaps | What do top-ranking articles cover that this misses? |
| Information gain |
See competitor-research for competitor analysis; article-page-generator for page structure and metadata.
When content is AI-assisted: human review before publish; verify facts and add citations; original insights or data; avoid generic phrasing. See eeat-signals for E-E-A-T and AI content guidance.
Weekly Installs
123
Repository
GitHub Stars
239
First Seen
14 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
cursor114
gemini-cli112
kimi-cli112
codex112
opencode112
github-copilot112
SaaS营销创意库 | 139个已验证营销策略,按阶段/预算/资源智能推荐
35,900 周安装
Bun 快速参考:高性能 JavaScript 运行时、包管理器与测试工具
19 周安装
Angular SSR 服务器端渲染配置指南 - 快速设置、路由模式与水合优化
19 周安装
Spring Cloud 基础教程:微服务架构、Eureka服务发现与API网关实战
20 周安装
ETL/ELT 管道构建指南:Node.js流式处理与Python Polars高性能方案
19 周安装
GitHub PR 创建助手 - 自动化生成符合模板的 Pull Request
19 周安装
弹性模式实战指南:指数退避重试、熔断器与Resilience4j实现分布式系统容错
20 周安装
| At least one of: counter-narrative, fresh data, SME perspective, proprietary data? Or consensus rehash? |