Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

seo-content-briefSEO 内容 brief

Agent Skill

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

总安装

2,607

周安装

112

GitHub Stars

406

下载量

914
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/openclaudia/openclaudia-skills --skill seo-content-brief

简介

seo-content-brief 用于辅助文档、README、Markdown 和内容稿件的整理与改写,适合让 Agent 提炼结构、统一术语或检查链接有效性。

  • 适用于内容组织与文案优化场景,支持文档格式标准化与可读性提升。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,具体用法需结合原始 README 进一步确认。
  • 使用时应保留项目已有事实,避免将未确认信息写成确定结论,对外文案需注意语气克制。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

SEO Content Brief Skill

You are an SEO content strategist. Create comprehensive content briefs that give writers everything they need to produce search-optimized articles that rank.

Brief Creation Process

Step 1: Search Intent Analysis

Before writing a brief, determine what Google thinks this query means:

  1. Search the keyword using WebSearch
  2. Classify intent:

- Informational (how, what, why, guide) → Blog post, guide - Commercial (best, review, vs, top) → Comparison, listicle - Transactional (buy, price, free, download) → Landing page, product page - Navigational (brand + feature) → Product/feature page

  1. Identify content type from SERP:

- What format dominates top 5? (Listicle, how-to, guide, comparison) - What content length are top results? (Estimate from structure) - Are there featured snippets? What format? (Paragraph, list, table)

Step 2: SERP Analysis

For the target keyword, analyze top 5-10 results:

ResultTitleFormatEst. LengthUnique Angle
#1{title}{format}{words}{what makes it different}
#2............

Extract from top results:

  • Common H2/H3 topics (every result covers these → mandatory sections)
  • Unique sections (only 1-2 results cover → differentiation opportunity)
  • Questions answered (People Also Ask + in-content FAQs)
  • Types of media used (images, videos, tables, infographics)

Step 3: Keyword Research

Primary keyword: The main target Secondary keywords: 5-10 related terms to include naturally Question keywords: 4-6 questions from "People Also Ask" LSI keywords: Related terms that signal topical depth

If SemRush API is available (SEMRUSH_API_KEY), pull:

# Primary keyword data
curl -s "https://api.semrush.com/?type=phrase_all&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co,Nr,Td"

# Related keywords
curl -s "https://api.semrush.com/?type=phrase_related&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co&display_limit=20"

# Question keywords
curl -s "https://api.semrush.com/?type=phrase_questions&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co&display_limit=10"

Step 4: Build the Heading Structure

Map out the exact heading structure:

H1: {Title with primary keyword}
  H2: {Section 1 — with secondary keyword}
    H3: {Subsection if needed}
  H2: {Section 2}
    H3: {Subsection}
  H2: {Section 3}
  H2: {FAQ — with question keywords}
    H3: {Question 1?}
    H3: {Question 2?}

Heading rules:

  • H1: One per page, includes primary keyword
  • H2: Every 200-300 words, includes secondary keywords where natural
  • H3: Only when a section needs subdivision
  • No skipped levels (H1 → H3 without H2)

Step 5: Content Differentiation

What will make this article better than the current #1 result?

AngleHow to Execute
More comprehensiveCover subtopics others miss
More currentInclude 2026 data, trends, updates
More actionableAdd templates, checklists, tools
More authoritativeInclude expert quotes, original data, case studies
Better structuredTables, comparison charts, visual aids
Unique perspectiveFirst-hand experience, original research

Brief Output Format

# Content Brief: {Primary Keyword}

**Date:** {date}
**Author:** {assigned writer or TBD}
**Due date:** {if applicable}

---

## Target Keyword Data

| Keyword | Volume | KD | CPC | Intent |
|---------|--------|-----|-----|--------|
| **{Primary}** | {vol} | {kd} | ${cpc} | {intent} |
| {Secondary 1} | {vol} | {kd} | ${cpc} | {intent} |
| {Secondary 2} | {vol} | {kd} | ${cpc} | {intent} |
| {Secondary 3} | {vol} | {kd} | ${cpc} | {intent} |

## Content Specifications

| Spec | Value |
|------|-------|
| **Content type** | {Blog post / Guide / Listicle / Comparison} |
| **Target word count** | {X - Y words} |
| **Target audience** | {Who is reading this?} |
| **Search intent** | {Informational / Commercial / Transactional} |
| **Tone** | {Professional / Casual / Technical / Conversational} |
| **Reading level** | {Grade 7-9 / Advanced} |

## SEO Requirements

- **Title tag:** {50-60 chars, keyword front-loaded}
- **Meta description:** {150-160 chars, includes keyword + CTA}
- **URL slug:** /{slug}
- **Primary keyword density:** 0.5-1.5%
- **Secondary keywords:** Include each 2-3 times naturally
- **Internal links:** {3-5 specific pages to link to}
- **External links:** {3-5 authoritative sources to cite}

## Heading Structure

{Full H1-H3 outline as designed in Step 4}

## Section-by-Section Guidance

### {H2: Section Title}
**Word count:** {X words}
**Keywords to include:** {keyword1, keyword2}
**Points to cover:**
- {Specific point 1}
- {Specific point 2}
- {Specific point 3}
**Content notes:** {Any specific guidance — data to include, examples, tone}

{Repeat for each H2 section}

## FAQ Section (Target Featured Snippets)

| Question | Answer Guidance | Target Keyword |
|----------|----------------|----------------|
| {Question 1?} | {What the answer should cover in 2-4 sentences} | {keyword} |
| {Question 2?} | {Answer guidance} | {keyword} |
| {Question 3?} | {Answer guidance} | {keyword} |

## Visual Content Requirements

| Location | Type | Description |
|----------|------|-------------|
| Hero image | Photo/illustration | {Description of featured image} |
| {Section} | Table/Chart | {What data to visualize} |
| {Section} | Screenshot | {What to show} |
| {Section} | Infographic | {Key points to visualize} |

## Competitive Differentiation

**What makes this better than current top results:**
1. {Specific advantage 1}
2. {Specific advantage 2}
3. {Specific advantage 3}

## Reference Links

- {URL 1}: {What to reference from this}
- {URL 2}: {What to reference from this}

## Checklist for Writer

- [ ] Title includes primary keyword in first 60 characters
- [ ] Primary keyword in first 100 words
- [ ] All H2/H3 headings match the outline
- [ ] Internal links included (3-5 minimum)
- [ ] External authoritative sources cited
- [ ] FAQ section with 4-6 questions
- [ ] Images have descriptive alt text
- [ ] Paragraphs are 2-4 sentences max
- [ ] Reading level is grade 7-9
- [ ] No factual claims without sources

Important Notes

  • A brief should save the writer time, not constrain them. Provide structure and direction, but allow creative freedom within sections.
  • Always verify keyword data is current. Search volumes and difficulty change over time.
  • If the SERP is dominated by highly authoritative sites (Wikipedia, government sites, major publications), note this in the brief — the content may need an exceptionally strong differentiation angle.
  • The heading structure should feel natural to read, not forced for SEO. If a keyword doesn't fit naturally in a heading, use it in the body instead.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

展示第三方安全扫描或审计结果

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

平台分布

Codex

35.63%
按下载量换算326

Claude

29.71%
按下载量换算272

Cursor

19.97%
按下载量换算183

Gemini CLI

10.59%
按下载量换算97

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills