Token导航 LogoToken导航

Agent Skill · 研究检索

seo-product-blog-writer(SEO product 博客写作)

seo-product-blog-writer 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

seo-product-blog-writer 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 38,307。

总安装 1,576周安装 65GitHub Stars 公开资料未说明下载 515核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:seo-product-blog-writer(SEO product 博客写作)
来源仓库:https://github.com/harrylabsj/seo-product-blog-writer
安装命令:
openclaw skills install seo-product-blog-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install seo-product-blog-writer

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

起草基于事实的 SEO 产品博客、购买指南,并与结构化大纲、常见问题解答和内部链接进行比较,以支持明智的购买决策。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install seo-product-blog-writer;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

seo-product-blog-writer 怎么安装?

在终端执行 openclaw skills install seo-product-blog-writer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

seo-product-blog-writer 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

seo-product-blog-writer 需要什么权限?

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

seo-product-blog-writer 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

seo-product-blog-writer 用的人多吗?

公开数据是累计安装 1,576 次,近一周安装 65 次,下载 515 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

seo-product-blog-writer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
seo-product-blog-writer

SEO product 博客写作 · 本页

1,576—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

SEO Product Blog Writer

Purpose

This skill drafts product-led SEO articles, buying guides, and category explainers that rank for commercial and informational search intent — while staying grounded in verified facts. Unlike generic blog writers that churn out thin content, it builds articles that genuinely help readers make informed purchase decisions, with structured outlines, FAQ sections, internal linking strategies, and a claim review system. Built for ecommerce teams, DTC brands, and marketplace sellers investing in content-led acquisition.

Triggers

  • "Write an SEO blog post about this product category"
  • "Draft a buying guide for [category]"
  • "Create a product education blog article"
  • "Turn product facts into a search-intent blog"
  • "Write a comparison guide that's fair to alternatives"
  • "Build an SEO content outline for our products"

Workflow

  1. Topic & intent capture — Gather target keyword/topic, primary search intent (informational: "what is X," "how to choose X" | commercial: "best X for Y," "X vs Y"), product facts, target audience, and content depth (quick guide vs. comprehensive resource).
  2. Search intent brief — Define the article's job: who is searching this, what do they actually need to know, what should they do after reading? Map primary and secondary intents to article sections.
  3. Outline construction — Build a hierarchical outline: H1 (title, primary keyword), H2s (major sections addressing intent stages), H3s (supporting details). Include FAQ section targeting "People Also Ask" queries where appropriate.
  4. Fact-grounded drafting — Draft each section anchored to verified product facts, not marketing fluff. Where the product genuinely excels, state it factually. Where it has limitations, either omit or note honestly — but never fabricate strengths.
  5. Product integration — Weave product mentions naturally at relevance points, not as forced pitch breaks. Include contextual CTAs ("See our full range of [category]" not "BUY NOW!!!").
  6. FAQ & internal linking — Generate an FAQ section addressing common buyer questions, plus internal link suggestions to related product pages, category pages, and other blog content.
  7. Claim review — Flag any statement that overstates product capability, makes unverifiable comparisons, or could be read as medical/financial/legal advice.

Prompt Templates

1. Full Article Generator (full_article)

Purpose: Generate a complete SEO blog post from topic and product facts.

Input:

  • ${primary_keyword} — Target keyword/phrase
  • ${search_intent} — Informational or commercial investigation
  • ${topic} — Article topic
  • ${product_facts} — Verified product details relevant to the topic
  • ${audience} — Target reader description
  • ${depth} — Quick guide (800–1200 words) or comprehensive (2000+)
  • ${cta_goal} — Browse category, view product, sign up, learn more

Output: Complete article with outline, draft body, FAQ, internal link suggestions, and claim review notes.

2. Buying Guide Builder (buying_guide)

Purpose: Create a structured buying guide for a product category.

Input:

  • ${category} — Product category
  • ${buyer_persona} — Who is buying and what matters to them
  • ${key_considerations} — 3–5 factors buyers should evaluate
  • ${product_lineup} — (Optional) your products that fit different buyer needs

Output: Buying guide with evaluation framework, "how to choose" section, product-fit map, and FAQ.

3. Comparison Article Writer (comparison_article)

Purpose: Write a fair comparison article between product types or approaches.

Input:

  • ${option_a} — First option description
  • ${option_b} — Second option description
  • ${comparison_dimensions} — Dimensions to compare (price, quality, use case, longevity, etc.)
  • ${neutral_stance} — Must this be neutral, or is it openly "why we do X differently"?

Output: Comparison table, pros/cons per option, "best for" recommendations, and disclaimer if bias exists.

4. Outline Optimizer (outline_optimize)

Purpose: Optimize an existing article outline for search intent coverage.

Input:

  • ${existing_outline} — Current outline
  • ${target_keyword} — Primary keyword
  • ${competitor_gaps} — (Optional) topics competitors cover that this outline misses

Output: Improved outline with section priority (must-have, should-have, nice-to-have), suggested headers, and missing intent coverage notes.

Output Format

## SEO Article: [Title]
**Primary Keyword:** [Keyword] | **Intent:** [Informational/Commercial] | **Depth:** [N words]

### Search Intent Brief
- **Who:** [Reader persona]
- **What they need:** [Core information need]
- **What they should do next:** [Desired action]

### Article Outline
## H1: [Title]
### H2: [Section 1] — addresses [intent stage]
#### H3: [Sub-point]
### H2: [Section 2]
...
### H2: Frequently Asked Questions
...

### Draft Article
[Full article body, scannable with short paragraphs and bullet points where helpful]

### FAQ
**Q:** [Common question]
**A:** [Honest, helpful answer]

### Internal Link Suggestions
- Link from "[phrase]" → [target page URL slug]
- Link to: [related blog post]
- Link to: [category page]

### Claim Review
- ✅ [Claim] — supported by [evidence]
- ⚠️ [Claim] — needs [source]; consider: [safer alt]

Safety Rules

  • NEVER provide medical, financial, legal, or investment advice — label any topic-adjacent content with "this is not professional advice" disclaimers
  • NEVER disparage competitors by name or imply inferiority without verifiable, side-by-side evidence
  • ALWAYS disclose commercial interest when recommending your own products in an "educational" article
  • ALWAYS label opinions, predictions, and subjective assessments clearly — separate fact from perspective
  • NEVER fabricate data points, study results, or statistics to support product claims
  • NEVER write content that could be interpreted as a guaranteed outcome ("using X will save you $Y/month")

Examples

Example 1: Skincare — Buying Guide (Comprehensive)

Input: Primary Keyword="how to choose a vitamin C serum", Topic="Vitamin C Serum Buying Guide", Product Facts="15% L-ascorbic acid, vitamin E + ferulic acid, airless pump, dermatologist-tested", Audience="Skincare beginners to intermediate", Depth="comprehensive (2000+ words)"

Output: Article structure: What vitamin C does for skin (informational) → Types of vitamin C in skincare (educational backbone) → What to look for in a serum (concentration, packaging, companion ingredients) → Why packaging matters (airless pump explained) → How to layer vitamin C in a routine → FAQ (can I use it with retinol? morning or night? how long to see results?) → Natural product mention at relevance points → Internal links to related skincare education posts.

Example 2: Kitchen Gadget — Comparison Article

Input: Option A="Silicone Baking Mats (reusable)", Option B="Parchment Paper (disposable)", Comparison Dimensions="Cost over time, environmental impact, convenience, baking results, cleanup", Neutral Stance="openly pro-reusable but honest about trade-offs"

Output: Article acknowledging parchment paper's convenience for certain tasks while honestly comparing cost-per-use, waste reduction, and results. Includes "when to use each" section and FAQ addressing "do silicone mats affect baking results?" Transparency: states this is from a brand that sells mats, but facts are independently verifiable.

Related Skills

平台分布

OpenClaw

75.15%
按下载量换算387

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills