Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问clear审计未展示

seo-content-briefSEO 内容 brief

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

8,836

周安装

393

GitHub Stars

公开资料未说明

下载量

2,850
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:seo-content-brief(SEO 内容 brief)
来源仓库:https://github.com/inf-sh/skills
仓库路径:skills/seo-content-brief
安装命令:
npx skills add inf-sh/skills --skill "seo-content-brief"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add inf-sh/skills --skill "seo-content-brief"

简介

SEO 内容简介包括关键词研究、搜索意图分析和内容结构。涵盖 SERP 分析、标题层次结构、字数目标和内部链接策略。用于:内容简介、SEO 写作、博客策略、内容规划、关键词定位。触发器: seo 内容简介、内容简介、seo 简介、关键词研究、搜索意图、内容策略、博客简介、seo 写作、内容规划、关键词定位、serp 分析、内容大纲、seo 文章、博客 seo

SKILL.md

name
seo-content-brief
description
SEO content brief creation with keyword research, search intent analysis, and content structure. Covers SERP analysis, heading hierarchy, word count targets, and internal linking strategy. Use for: content briefs, SEO writing, blog strategy, content planning, keyword targeting. Triggers: seo content brief, content brief, seo brief, keyword research, search intent, content strategy, blog brief, seo writing, content planning, keyword targeting, serp analysis, content outline, seo article, blog seo
allowed-tools
Bash(infsh *)

SEO Content Brief

Create data-driven content briefs via inference.sh CLI.

Quick Start

curl -fsSL https://cli.inference.sh | sh && 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"
}'

Content Brief Template

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]

Search Intent Types

IntentWhat Searcher WantsContent FormatExample Query
InformationalLearn somethingGuide, tutorial, explainer"what is CI/CD"
CommercialCompare before buyingComparison, listicle, review"best CI/CD tools 2024"
TransactionalBuy/sign upProduct page, pricing page"GitHub Actions pricing"
NavigationalFind 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.

SERP Analysis Process

# 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]"
}'

What to Extract from Top Results

Data PointWhy
Word countSets your minimum (match or exceed top 3)
Heading structureShows what Google considers complete coverage
Topics coveredEvery topic they cover, you must cover
Topics missedYour opportunity to be more comprehensive
Content formatListicle, guide, tutorial, comparison
Media usedImages, videos, tables, infographics
Internal/external linksReference quality signals

Keyword Research

Keyword Metrics

MetricWhat It MeansTarget
Search volumeMonthly searchesDepends on niche (100+ for long-tail)
Keyword difficultyCompetition level< 30 for new sites, < 50 for established
CPCWhat advertisers payHigher CPC = more commercial value
Search intentWhat users wantMust match your content type

Finding Keywords

# 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"
}'

Keyword Clustering

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.

Heading Structure

Rules

RuleWhy
One H1 per pageSEO standard, contains primary keyword
H2s = main sectionsEach should target a secondary keyword or question
H3s = subsectionsBreak up long H2 sections
Primary keyword in H1Direct ranking signal
Secondary keywords in H2sTopical coverage signal
Question format for some H2sTargets "People Also Ask"
Logical hierarchyNever skip levels (H1 → H3 without H2)

Example Structure

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

Word Count Targets

Content TypeWord CountWhen
Short-form blog800-1,200News, updates, opinions
Standard blog1,500-2,000How-tos, tutorials
Long-form guide2,500-4,000Comprehensive guides, comparisons
Pillar content4,000-7,000Definitive guides, hub pages
Glossary/definition300-800Quick reference terms

Rule: match or exceed the average word count of the top 3 ranking results. Don't pad — every word should add value.

On-Page SEO Checklist

ElementRule
Title tagPrimary keyword + compelling hook, 50-60 characters
Meta descriptionIncludes keyword, 150-160 characters, includes CTA
URL slugShort, keyword-rich: /best-project-management-tools
H1Primary keyword, matches search intent
First 100 wordsInclude primary keyword naturally
Image alt textDescriptive, includes keyword where natural
Internal links3-5 links to related content
External links2-3 authoritative sources
Schema markupFAQ, HowTo, or Article schema where applicable

Content Differentiation

Unique Angles

AngleExample
Original data"We surveyed 500 PMs — here's what they use"
Expert quotesInterview practitioners for original insights
Real examplesScreenshots, case studies, not just descriptions
More comprehensiveCover subtopics competitors skip
More currentUpdated data, newer tools, recent changes
Better visualsComparison 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>"
}'

Internal Linking Strategy

TypePurpose
Hub → SpokePillar page links to all subtopic articles
Spoke → HubSubtopic articles link back to pillar page
Spoke → SpokeRelated articles cross-link to each other
ContextualNatural in-text links where topic is mentioned

Rules

  • 3-5 internal links minimum per article
  • Anchor text should be descriptive (not "click here")
  • Link to relevant pages, not random ones
  • Update old articles to link to new ones
  • Most important pages should have the most internal links

Common Mistakes

MistakeProblemFix
No SERP analysisWriting blind, wrong formatAlways analyze top 3-5 before writing
Wrong intent matchGuide when they want comparison, or vice versaMatch SERP format exactly
Keyword stuffingPenalized, reads poorlyUse naturally, 1-2% density max
Ignoring "People Also Ask"Missing easy ranking opportunitiesAnswer PAA questions in your content
Too shortCan't compete with comprehensive resultsMatch or exceed top 3 word count
No unique angleJust another "me too" articleOriginal data, expert quotes, better visuals
Keyword cannibalizationMultiple pages competingOne page per keyword cluster
No internal linksWasted link equity, poor site structure3-5 internal links per article
Missing meta descriptionGoogle generates one (often poorly)Write compelling meta with keyword + CTA

Related Skills

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

68.28%
按下载量换算1,946

Cursor

24.36%
按下载量换算694

安全审计

暂无安全审计结果可展示。

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills