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

seo-content-engineSEO 内容引擎

Agent Skill

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

总安装

259

周安装

11

GitHub Stars

607

下载量

91
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/athina-ai/goose-skills --skill seo-content-engine

简介

构建持续产出的 SEO 内容体系,从审计到排期再到草稿撰写一体化完成。

  • 结合品牌语调与客户定位,生成符合搜索意图的长尾内容方案。
  • 输出包含关键词架构与发布日历的可执行路线图。
  • 需客户提供网站 URL 与业务背景文档作为输入依据。
  • seo-content-engine 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

SEO Content Engine

Build a compounding SEO content engine for a client: audit → gap analysis → keyword architecture → content calendar → content drafting → publishing pipeline.

When to Use

  • "Build an SEO content strategy for [client]"
  • "Create a content engine for [company]"
  • "What content should [company] be publishing?"

Prerequisites

  • Client website URL
  • Client context.md with ICP, value props, positioning
  • Top competitors identified (from intelligence package or manually)

Steps

1. Audit Current State

Skill: seo-content-audit (orchestrates site-content-catalog + seo-domain-analyzer + brand-voice-extractor)

Run the full SEO audit to understand:

  • Current content inventory (what exists, by type and topic)
  • Domain authority, organic traffic, keyword rankings
  • Competitive gap matrix (what competitors rank for that the client doesn't)
  • Brand voice profile (writing style to match)

Skill: aeo-visibility

Test AI answer engine visibility for key queries.

Output: Complete picture of where the client stands in search.

2. Identify Content Gaps

From the audit, identify:

Competitive gaps: Keywords competitors rank for that the client doesn't Funnel gaps: Missing content at TOFU, MOFU, or BOFU stages Topic gaps: Industry/vertical content that doesn't exist Comparison gaps: Missing "vs" pages and "alternatives" pages

Prioritize by: search volume x commercial intent x competitive difficulty.

3. Build Keyword Architecture

Organize target keywords by funnel stage:

  • TOFU (awareness): "what is [category]", "[category] use cases", "how to [solve problem]"
  • MOFU (evaluation): "[category] comparison", "how to choose [solution]", "[compliance/technical] requirements"
  • BOFU (decision): "[Company] vs [Competitor]", "[Competitor] alternatives", pricing guides, migration guides

Map each keyword cluster to a content type (blog post, landing page, guide, comparison page).

4. Create Content Calendar

Build a prioritized content calendar:

  1. Week 1-2: Highest-urgency BOFU pages (comparison pages, especially if competitors are publishing attack content)
  2. Week 2-4: Core MOFU guides and evaluation content
  3. Week 4-8: TOFU awareness content and programmatic SEO templates
  4. Ongoing: 2-3 editorial pieces per week

5. Draft Content

Skill: content-asset-creator (for landing pages, reports, one-pagers) Method: AI-assisted drafting with brand voice matching (from brand-voice-extractor output)

For each content piece:

  • Match the client's brand voice and style
  • Include target keywords naturally
  • Build internal linking to related content
  • Include clear CTAs
  • Add structured data / schema markup recommendations

6. Build Internal Linking Architecture

Design the linking structure:

  • TOFU pages link to related MOFU pages
  • MOFU pages link to BOFU pages (comparison, pricing)
  • BOFU pages link to product/signup
  • All pages link to relevant pillar content

7. Publish & Monitor

  • Publish on client's blog/site (or provide drafts for client to publish)
  • Track: organic traffic by page/cluster, rankings by keyword, content-to-signup conversion
  • Monthly: Review which content is ranking, which needs updates

Ongoing Cadence

  • Weekly: Publish 2-3 pieces, monitor rankings
  • Monthly: Review content performance, update calendar, refresh underperforming pages
  • Quarterly: Re-run seo-content-audit to measure progress and identify new gaps

Human Checkpoints

  • After Step 2: Review gap analysis and priority recommendations
  • After Step 4: Review content calendar before drafting
  • After Step 5: Review content drafts before publishing

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

39.75%
按下载量换算36

Claude

28.73%
按下载量换算26

Cursor

19.43%
按下载量换算18

Gemini CLI

9.49%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills