seo-content-brief by inferen-sh/skills
npx skills add https://github.com/inferen-sh/skills --skill seo-content-brief通过 inference.sh CLI 创建数据驱动的内容简报。
需要 inference.sh CLI (
infsh)。安装说明
infsh login
# 研究目标关键词
infsh app run tavily/search-assistant --input '{
"query": "best project management tools for small teams 2024"
}'
# 分析排名靠前的内容
infsh app run exa/search --input '{
"query": "project management tools small teams comparison guide"
}'
每个简报在开始写作前都应回答以下问题:
# 内容简报:[暂定标题]
## 目标
- **主要关键词:** [精确关键词]
- **次要关键词:** [3-5 个相关术语]
- **搜索意图:** [信息型 / 商业型 / 交易型 / 导航型]
- **目标字数:** [X,XXX 字]
- **目标 URL:** /blog/[slug]
## 搜索意图分析
- 搜索者想要完成什么?
- 排名靠前的结果使用什么格式?(列表、指南、对比、教程)
- 需要回答哪些问题?
## 大纲
H1: [包含主要关键词的标题]
H2: [第 1 部分]
H3: [子部分]
H2: [第 2 部分]
...
## 需要超越的竞争对手
1. [URL] — [字数] — [他们的优点] — [差距/弱点]
2. [URL] — [字数] — [他们的优点] — [差距/弱点]
3. [URL] — [字数] — [他们的优点] — [差距/弱点]
## 独特角度
这篇文章与已排名的内容相比,有何不同/更好之处?
## 内部链接
- 链接到: [需要从本文链接到的现有页面]
- 来自: [应该链接到这篇新文章的现有页面]
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 意图 | 搜索者想要什么 | 内容格式 | 示例查询 |
|---|---|---|---|
| 信息型 | 学习知识 | 指南、教程、解释说明 | "what is CI/CD" |
| 商业型 | 购买前比较 | 对比、列表、评测 | "best CI/CD tools 2024" |
| 交易型 | 购买/注册 | 产品页面、定价页面 | "GitHub Actions pricing" |
| 导航型 | 查找特定页面 | — (不要以此为目标) | "GitHub login" |
格式要与意图匹配。 如果排名前 10 的结果都是列表,就写列表。如果都是教程,就写教程。与 SERP 格式对抗会失败。
# 第 1 步:查看当前排名情况
infsh app run tavily/search-assistant --input '{
"query": "[你的目标关键词]"
}'
# 第 2 步:分析排名靠前的内容
infsh app run tavily/extract --input '{
"urls": ["https://top-result-1.com/article", "https://top-result-2.com/article"]
}'
# 第 3 步:查找相关问题("用户还问了")
infsh app run tavily/search-assistant --input '{
"query": "[关键词] questions people ask FAQ"
}'
# 第 4 步:寻找内容空白点
infsh app run exa/search --input '{
"query": "[关键词] [竞争对手遗漏的子主题]"
}'
| 数据点 | 原因 |
|---|---|
| 字数 | 设定你的最低目标(匹配或超过前 3 名) |
| 标题结构 | 展示 Google 认为什么是完整覆盖 |
| 涵盖的主题 | 他们涵盖的每个主题,你也必须涵盖 |
| 遗漏的主题 | 你变得更全面的机会 |
| 内容格式 | 列表、指南、教程、对比 |
| 使用的媒体 | 图片、视频、表格、信息图 |
| 内部/外部链接 | 参考质量信号 |
| 指标 | 含义 | 目标 |
|---|---|---|
| 搜索量 | 月搜索量 | 取决于利基市场(长尾词 100+) |
| 关键词难度 | 竞争水平 | 新网站 < 30,成熟网站 < 50 |
| CPC | 广告商支付的费用 | CPC 越高 = 商业价值越高 |
| 搜索意图 | 用户想要什么 | 必须与你的内容类型匹配 |
# 种子关键词研究
infsh app run tavily/search-assistant --input '{
"query": "project management software long tail keywords related searches"
}'
# 查找基于问题的关键词
infsh app run exa/search --input '{
"query": "questions about project management tools for startups"
}'
# 竞争对手关键词分析
infsh app run tavily/search-assistant --input '{
"query": "site:competitor.com/blog top performing pages topics"
}'
将相关关键词分组到一篇内容中:
Primary: "best project management tools for small teams"
Cluster:
- "project management software small business"
- "project management tools comparison"
- "simple project management app"
- "project management for startups"
- "affordable project management software"
每个关键词集群对应一个页面。 不要为每个变体创建单独的页面——那是关键词蚕食。
| 规则 | 原因 |
|---|---|
| 每页一个 H1 | SEO 标准,包含主要关键词 |
| H2 = 主要部分 | 每个都应针对一个次要关键词或问题 |
| H3 = 子部分 | 拆分长的 H2 部分 |
| 主要关键词在 H1 中 | 直接的排名信号 |
| 次要关键词在 H2 中 | 主题覆盖信号 |
| 部分 H2 使用问题格式 | 针对"用户还问了" |
| 逻辑层次结构 | 不要跳过层级(H1 → H3 而没有 H2) |
H1: 适合小型团队的最佳项目管理工具 (2025)
H2: 我们如何评估这些工具
H2: 十大项目管理工具对比
H3: 1. 工具 A — 最适合 [使用场景]
H3: 2. 工具 B — 最适合 [使用场景]
...
H2: 功能对比表
H2: 如何为你的团队选择正确的工具
H3: 团队规模考量
H3: 预算考量
H2: 常见问题解答
H3: 最简单的项目管理工具是什么?
H3: 小型团队需要项目管理软件吗?
H2: 结论
| 内容类型 | 字数 | 适用场景 |
|---|---|---|
| 短篇博客 | 800-1,200 | 新闻、更新、观点 |
| 标准博客 | 1,500-2,000 | 操作指南、教程 |
| 长篇指南 | 2,500-4,000 | 综合指南、对比 |
| 支柱内容 | 4,000-7,000 | 权威指南、中心页面 |
| 术语表/定义 | 300-800 | 快速参考术语 |
规则:匹配或超过排名前 3 结果的平均字数。 不要注水——每个字都应该增加价值。
| 元素 | 规则 |
|---|---|
| 标题标签 | 主要关键词 + 吸引人的钩子,50-60 个字符 |
| 元描述 | 包含关键词,150-160 个字符,包含 CTA |
| URL 别名 | 简短,富含关键词:/best-project-management-tools |
| H1 | 主要关键词,匹配搜索意图 |
| 前 100 字 | 自然地包含主要关键词 |
| 图片替代文本 | 描述性,在自然的情况下包含关键词 |
| 内部链接 | 3-5 个指向相关内容的链接 |
| 外部链接 | 2-3 个权威来源 |
| 结构化数据标记 | 在适用的情况下使用 FAQ、HowTo 或 Article 模式 |
| 角度 | 示例 |
|---|---|
| 原始数据 | "我们调查了 500 位项目经理——以下是他们使用的工具" |
| 专家引言 | 采访从业者以获得原创见解 |
| 真实案例 | 截图、案例研究,而不仅仅是描述 |
| 更全面 | 涵盖竞争对手跳过的子主题 |
| 更新颖 | 更新的数据、更新的工具、近期的变化 |
| 更好的视觉效果 | 对比表格、信息图、决策树 |
# 生成对比信息图
infsh app run infsh/html-to-image --input '{
"html": "<div style=\"width:1200px;height:800px;background:white;padding:40px;font-family:system-ui\"><h2 style=\"font-size:28px;color:#1e293b;text-align:center;margin-bottom:30px\">Project Management Tools Comparison</h2><table style=\"width:100%;border-collapse:collapse;font-size:16px\"><tr style=\"background:#f1f5f9\"><th style=\"padding:12px;text-align:left;border-bottom:2px solid #cbd5e1\">Feature</th><th style=\"padding:12px;text-align:center;border-bottom:2px solid #cbd5e1\">Tool A</th><th style=\"padding:12px;text-align:center;border-bottom:2px solid #cbd5e1\">Tool B</th><th style=\"padding:12px;text-align:center;border-bottom:2px solid #cbd5e1\">Tool C</th></tr><tr><td style=\"padding:12px;border-bottom:1px solid #e2e8f0\">Free tier</td><td style=\"padding:12px;text-align:center;border-bottom:1px solid #e2e8f0\">✅</td><td style=\"padding:12px;text-align:center;border-bottom:1px solid #e2e8f0\">✅</td><td style=\"padding:12px;text-align:center;border-bottom:1px solid #e2e8f0\">❌</td></tr></table></div>"
}'
| 类型 | 目的 |
|---|---|
| 中心 → 分支 | 支柱页面链接到所有子主题文章 |
| 分支 → 中心 | 子主题文章链接回支柱页面 |
| 分支 → 分支 | 相关文章相互交叉链接 |
| 上下文相关 | 在提及主题的地方自然地添加文本内链接 |
| 错误 | 问题 | 解决方法 |
|---|---|---|
| 不做 SERP 分析 | 盲目写作,格式错误 | 在写作前始终分析前 3-5 名 |
| 意图匹配错误 | 用户想要对比时写指南,反之亦然 | 完全匹配 SERP 格式 |
| 关键词堆砌 | 受惩罚,可读性差 | 自然使用,密度最高 1-2% |
| 忽略"用户还问了" | 错失简单的排名机会 | 在你的内容中回答 PAA 问题 |
| 内容太短 | 无法与全面的结果竞争 | 匹配或超过前 3 名的字数 |
| 没有独特角度 | 只是另一篇"我也一样"的文章 | 原始数据、专家引言、更好的视觉效果 |
| 关键词蚕食 | 多个页面相互竞争 | 每个关键词集群对应一个页面 |
| 没有内部链接 | 浪费链接权重,网站结构差 | 每篇文章 3-5 个内部链接 |
| 缺少元描述 | Google 会生成一个(通常很差) | 撰写包含关键词 + CTA 的吸引人的元描述 |
npx skills add inference-sh/skills@seo
npx skills add inference-sh/skills@technical-blog-writing
npx skills add inference-sh/skills@web-search
浏览所有应用:infsh app list
每周安装量
7.0K
仓库
GitHub 星标数
182
首次出现
12 天前
安全审计
安装于
claude-code5.5K
gemini-cli5.0K
codex5.0K
opencode5.0K
amp5.0K
github-copilot5.0K
Create data-driven content briefs via inference.sh CLI.
Requires inference.sh CLI (
infsh). Install instructions
infsh login
# Research target keyword
infsh app run tavily/search-assistant --input '{
"query": "best project management tools for small teams 2024"
}'
# Analyze top-ranking content
infsh app run exa/search --input '{
"query": "project management tools small teams comparison guide"
}'
Every brief should answer these questions before writing begins:
# Content Brief: [Working Title]
## Target
- **Primary keyword:** [exact keyword]
- **Secondary keywords:** [3-5 related terms]
- **Search intent:** [informational / commercial / transactional / navigational]
- **Target word count:** [X,XXX words]
- **Target URL:** /blog/[slug]
## Search Intent Analysis
- What is the searcher trying to accomplish?
- What format do top results use? (listicle, guide, comparison, tutorial)
- What questions need answering?
## Outline
H1: [Title with primary keyword]
H2: [Section 1]
H3: [Subsection]
H2: [Section 2]
...
## Competitors to Beat
1. [URL] — [word count] — [what they do well] — [gap/weakness]
2. [URL] — [word count] — [what they do well] — [gap/weakness]
3. [URL] — [word count] — [what they do well] — [gap/weakness]
## Unique Angle
What makes this piece different/better than what already ranks?
## Internal Links
- Link TO: [existing pages to link to from this article]
- Link FROM: [existing pages that should link to this new article]
| Intent | What Searcher Wants | Content Format | Example Query |
|---|---|---|---|
| Informational | Learn something | Guide, tutorial, explainer | "what is CI/CD" |
| Commercial | Compare before buying | Comparison, listicle, review | "best CI/CD tools 2024" |
| Transactional | Buy/sign up | Product page, pricing page | "GitHub Actions pricing" |
| Navigational | Find a specific page | — (don't target these) | "GitHub login" |
Match format to intent. If top 10 results are all listicles, write a listicle. If they're all tutorials, write a tutorial. Fighting the SERP format loses.
# Step 1: See what currently ranks
infsh app run tavily/search-assistant --input '{
"query": "[your target keyword]"
}'
# Step 2: Analyze top-ranking content
infsh app run tavily/extract --input '{
"urls": ["https://top-result-1.com/article", "https://top-result-2.com/article"]
}'
# Step 3: Find related questions (People Also Ask)
infsh app run tavily/search-assistant --input '{
"query": "[keyword] questions people ask FAQ"
}'
# Step 4: Find content gaps
infsh app run exa/search --input '{
"query": "[keyword] [subtopic competitors miss]"
}'
| Data Point | Why |
|---|---|
| Word count | Sets your minimum (match or exceed top 3) |
| Heading structure | Shows what Google considers complete coverage |
| Topics covered | Every topic they cover, you must cover |
| Topics missed | Your opportunity to be more comprehensive |
| Content format | Listicle, guide, tutorial, comparison |
| Media used | Images, videos, tables, infographics |
| Internal/external links | Reference quality signals |
| Metric | What It Means | Target |
|---|---|---|
| Search volume | Monthly searches | Depends on niche (100+ for long-tail) |
| Keyword difficulty | Competition level | < 30 for new sites, < 50 for established |
| CPC | What advertisers pay | Higher CPC = more commercial value |
| Search intent | What users want | Must match your content type |
# Seed keyword research
infsh app run tavily/search-assistant --input '{
"query": "project management software long tail keywords related searches"
}'
# Find question-based keywords
infsh app run exa/search --input '{
"query": "questions about project management tools for startups"
}'
# Competitor keyword analysis
infsh app run tavily/search-assistant --input '{
"query": "site:competitor.com/blog top performing pages topics"
}'
Group related keywords into one piece of content:
Primary: "best project management tools for small teams"
Cluster:
- "project management software small business"
- "project management tools comparison"
- "simple project management app"
- "project management for startups"
- "affordable project management software"
One page per keyword cluster. Don't create separate pages for each variation — that's keyword cannibalization.
| Rule | Why |
|---|---|
| One H1 per page | SEO standard, contains primary keyword |
| H2s = main sections | Each should target a secondary keyword or question |
| H3s = subsections | Break up long H2 sections |
| Primary keyword in H1 | Direct ranking signal |
| Secondary keywords in H2s | Topical coverage signal |
| Question format for some H2s | Targets "People Also Ask" |
| Logical hierarchy | Never skip levels (H1 → H3 without H2) |
H1: Best Project Management Tools for Small Teams (2025)
H2: How We Evaluated These Tools
H2: Top 10 Project Management Tools Compared
H3: 1. Tool A — Best for [use case]
H3: 2. Tool B — Best for [use case]
...
H2: Feature Comparison Table
H2: How to Choose the Right Tool for Your Team
H3: Team Size Considerations
H3: Budget Considerations
H2: Frequently Asked Questions
H3: What is the easiest project management tool?
H3: Do small teams need project management software?
H2: Conclusion
| Content Type | Word Count | When |
|---|---|---|
| Short-form blog | 800-1,200 | News, updates, opinions |
| Standard blog | 1,500-2,000 | How-tos, tutorials |
| Long-form guide | 2,500-4,000 | Comprehensive guides, comparisons |
| Pillar content | 4,000-7,000 | Definitive guides, hub pages |
| Glossary/definition | 300-800 | Quick reference terms |
Rule: match or exceed the average word count of the top 3 ranking results. Don't pad — every word should add value.
| Element | Rule |
|---|---|
| Title tag | Primary keyword + compelling hook, 50-60 characters |
| Meta description | Includes keyword, 150-160 characters, includes CTA |
| URL slug | Short, keyword-rich: /best-project-management-tools |
| H1 | Primary keyword, matches search intent |
| First 100 words | Include primary keyword naturally |
| Image alt text | Descriptive, includes keyword where natural |
| Internal links | 3-5 links to related content |
| External links | 2-3 authoritative sources |
| Schema markup | FAQ, HowTo, or Article schema where applicable |
| Angle | Example |
|---|---|
| Original data | "We surveyed 500 PMs — here's what they use" |
| Expert quotes | Interview practitioners for original insights |
| Real examples | Screenshots, case studies, not just descriptions |
| More comprehensive | Cover subtopics competitors skip |
| More current | Updated data, newer tools, recent changes |
| Better visuals | Comparison tables, infographics, decision trees |
# Generate comparison infographic
infsh app run infsh/html-to-image --input '{
"html": "<div style=\"width:1200px;height:800px;background:white;padding:40px;font-family:system-ui\"><h2 style=\"font-size:28px;color:#1e293b;text-align:center;margin-bottom:30px\">Project Management Tools Comparison</h2><table style=\"width:100%;border-collapse:collapse;font-size:16px\"><tr style=\"background:#f1f5f9\"><th style=\"padding:12px;text-align:left;border-bottom:2px solid #cbd5e1\">Feature</th><th style=\"padding:12px;text-align:center;border-bottom:2px solid #cbd5e1\">Tool A</th><th style=\"padding:12px;text-align:center;border-bottom:2px solid #cbd5e1\">Tool B</th><th style=\"padding:12px;text-align:center;border-bottom:2px solid #cbd5e1\">Tool C</th></tr><tr><td style=\"padding:12px;border-bottom:1px solid #e2e8f0\">Free tier</td><td style=\"padding:12px;text-align:center;border-bottom:1px solid #e2e8f0\">✅</td><td style=\"padding:12px;text-align:center;border-bottom:1px solid #e2e8f0\">✅</td><td style=\"padding:12px;text-align:center;border-bottom:1px solid #e2e8f0\">❌</td></tr></table></div>"
}'
| Type | Purpose |
|---|---|
| Hub → Spoke | Pillar page links to all subtopic articles |
| Spoke → Hub | Subtopic articles link back to pillar page |
| Spoke → Spoke | Related articles cross-link to each other |
| Contextual | Natural in-text links where topic is mentioned |
| Mistake | Problem | Fix |
|---|---|---|
| No SERP analysis | Writing blind, wrong format | Always analyze top 3-5 before writing |
| Wrong intent match | Guide when they want comparison, or vice versa | Match SERP format exactly |
| Keyword stuffing | Penalized, reads poorly | Use naturally, 1-2% density max |
| Ignoring "People Also Ask" | Missing easy ranking opportunities | Answer PAA questions in your content |
| Too short | Can't compete with comprehensive results | Match or exceed top 3 word count |
| No unique angle | Just another "me too" article | Original data, expert quotes, better visuals |
| Keyword cannibalization | Multiple pages competing | One page per keyword cluster |
| No internal links | Wasted link equity, poor site structure | 3-5 internal links per article |
| Missing meta description |
npx skills add inference-sh/skills@seo
npx skills add inference-sh/skills@technical-blog-writing
npx skills add inference-sh/skills@web-search
Browse all apps: infsh app list
Weekly Installs
7.0K
Repository
GitHub Stars
182
First Seen
12 days ago
Security Audits
Gen Agent Trust HubPassSocketWarnSnykWarn
Installed on
claude-code5.5K
gemini-cli5.0K
codex5.0K
opencode5.0K
amp5.0K
github-copilot5.0K
48,100 周安装
| Google generates one (often poorly) |
| Write compelling meta with keyword + CTA |