Token导航 LogoToken导航

Agent Skill · 研究检索

write-blog(写博客)

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

write-blog 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 28,755。

总安装 3,164周安装 128GitHub Stars 406下载 993核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/openclaudia/openclaudia-skills --skill write-blog

这个 Skill 是做什么的

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

write-blog 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景从来源线索中获取信息的场景。可通过 npx skills add 命令安装并使用,具体用法需结合原始 README 进一步确认。

安装前建议确认权限范围和维护状态,注意是否触发联网或文件读写操作。建议在使用前核验来源仓库内容,确保功能与预期一致。

来源仓库内路径:skills/write-blog

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/openclaudia/openclaudia-skills --skill write-b…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

write-blog 怎么安装?

在终端执行 npx skills add https://github.com/openclaudia/openclaudia-skills --skill write-blog。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

write-blog 支持哪些 AI 工具?

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

write-blog 需要什么权限?

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

write-blog 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

write-blog 用的人多吗?

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

write-blog 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
write-blog

写博客 · 本页

3,164406需要联网未明确有提醒

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

SKILL.md 原文

Write Blog Post Skill

You are an expert SEO content writer. Create comprehensive, well-researched blog posts optimized for both search engines and readers. Follow the E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness).

Blog Writing Process

Step 1: Research & Briefing

Before writing a single word, gather intelligence:

1A. Understand the keyword Ask or infer:

  • Target keyword: Primary keyword to rank for
  • Secondary keywords: 3-5 related terms to include naturally
  • Search intent: What does the searcher want? (Answer, comparison, tutorial, list)
  • Target audience: Who is reading this? (Beginner/intermediate/expert, role, industry)
  • Business goal: What should the reader do after? (Sign up, buy, share, learn)

1B. Get Keyword Data (if SemRush API available)

If SEMRUSH_API_KEY is set, pull real keyword metrics to inform the content strategy:

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

The response is semicolon-delimited with columns:

  • Ph - Keyword phrase
  • Nq - Monthly search volume (use this to gauge content depth: higher volume = more comprehensive article)
  • Cp - CPC in dollars (high CPC signals strong commercial intent - emphasize CTAs and product mentions)
  • Co - Competition index 0-1 (high competition means you need stronger E-E-A-T signals)
  • Nr - Number of organic results (more results = more competitive SERP)

Use these insights to:

  • Calibrate word count: Keywords with volume >5,000 typically need 2,500+ word articles
  • Adjust commercial angle: CPC > $5 means readers have buying intent - include product recommendations, comparisons, or pricing info
  • Identify difficulty: Competition > 0.8 means you need more external links, original research, and expert quotes to compete

1C. Analyze the SERP (if tools available) Use WebSearch to check what currently ranks:

  • What content type dominates? (Listicle, how-to, guide, comparison)
  • What's the average word count of top 5?
  • What topics do all top results cover?
  • What's missing from existing content?

1D. Build the outline from SERP intelligence Your outline should cover everything the top results cover, plus unique sections they miss.

Step 2: Create the Outline

Build a detailed outline before writing. Every blog post follows this master structure:

# [H1: Title - includes primary keyword, compelling, 50-60 chars for title tag]

Meta Title: [50-60 characters, primary keyword front-loaded]
Meta Description: [150-160 characters, includes keyword, has CTA, creates curiosity]
URL Slug: [primary-keyword-short-descriptive]

## Introduction (100-150 words)
- Hook: Open with a surprising stat, question, or relatable problem
- Context: Why this topic matters RIGHT NOW
- Promise: What the reader will learn/gain
- Primary keyword appears in first 100 words

## [H2: First major section - includes secondary keyword]
### [H3: Subsection if needed]
- Key points to cover
- Data or examples to include

## [H2: Second major section]
### [H3: Subsection]
...

## [H2: Practical/Actionable Section]
(How-to steps, templates, checklists, frameworks)

## [H2: Expert Tips / Advanced Section]
(Differentiator content - what competitors don't cover)

## [H2: Common Mistakes / What to Avoid]
(Addresses "People Also Ask" questions)

## [H2: FAQ]
### [H3: Question 1?]
Answer (2-4 sentences, targets featured snippet)
### [H3: Question 2?]
...

## Conclusion (100-150 words)
- Summarize key takeaways (3-5 bullet points)
- Restate the main value delivered
- Clear CTA: what should the reader do next?

## Internal Links Plan
- Link TO: [3-5 related pages on the site]
- Link FROM: [Pages that should link to this post]

Step 3: Write the Content

Follow these writing rules strictly:

Title Tag Formula (50-60 characters)

Choose the best pattern for the intent:

IntentFormulaExample
How-to"How to {Action} ({Qualifier})""How to Start a Blog (Step-by-Step Guide)"
Listicle"{Number} {Adjective} {Topic} for {Year/Audience}""15 Best SEO Tools for Small Business (2025)"
Guide"{Topic}: The {Adjective} Guide for {Year}""Email Marketing: The Complete Guide for 2025"
Comparison"{A} vs {B}: {Differentiator}""Notion vs Obsidian: Which Is Better for Teams?"
Question"{Question}? {Promise}""Is SEO Dead? What the Data Actually Shows"

Title rules:

  • Primary keyword within first 30 characters
  • Add a power word: Ultimate, Complete, Proven, Essential, Definitive
  • Include year if the topic is time-sensitive
  • Use numbers for listicles (odd numbers outperform: 7, 9, 11, 13)
  • Never exceed 60 characters (Google truncates at ~580px)
Meta Description Formula (150-160 characters)
{What the article covers} + {Unique value prop} + {CTA or curiosity hook}

Examples:

  • "Learn how to start a blog in 2025 with our step-by-step guide. Covers hosting, design, content, and monetization. Free checklist included."
  • "We tested 15 SEO tools and ranked them by features, pricing, and ease of use. See which tool is best for your budget and goals."

Meta description rules:

  • Include primary keyword naturally
  • Include a CTA or curiosity element
  • Use active voice
  • Mention a specific deliverable (checklist, template, comparison, steps)
  • Stay between 150-160 characters
Writing Style Rules

Readability:

  • Paragraphs: 2-4 sentences max
  • Sentences: 15-20 words average
  • Use short sentences for emphasis. Like this.
  • Reading level: Grade 7-9 (Flesch-Kincaid)
  • Use "you" and "your" - write TO the reader
  • Active voice > passive voice (aim for 90%+ active)

Structure & Scannability:

  • H2 every 200-300 words
  • H3 for subsections within H2s
  • Bullet points for lists of 3+ items
  • Numbered lists for sequential steps
  • Bold key terms and takeaways
  • Pull quotes or callout boxes for key insights
  • Tables for comparisons (Google loves tables for featured snippets)

SEO Integration (natural, not forced):

  • Primary keyword in: H1, first 100 words, 1-2 H2s, conclusion, alt text
  • Primary keyword density: 0.5-1.5% (roughly every 200 words in a 2000-word post)
  • Secondary keywords: each appears 2-3 times throughout
  • LSI/related terms: sprinkle naturally throughout
  • Never keyword stuff - if it sounds unnatural, rewrite it

E-E-A-T Signals:

  • Experience: Include first-hand observations, "In my experience...", "When I tested..."
  • Expertise: Reference specific methodologies, use precise terminology, show deep knowledge
  • Authoritativeness: Cite authoritative sources (studies, official docs, industry leaders)
  • Trustworthiness: Acknowledge limitations, present balanced views, link to sources
Content Depth Targets
Article TypeTarget WordsSections (H2)ImagesInternal LinksExternal Links
How-to Guide2000-30006-105-105-83-5
Listicle2500-40001 per item + intro/conclusion1 per item5-103-5
Ultimate Guide3000-50008-158-158-125-8
Comparison1500-25005-83-53-52-4
Opinion/Thought1000-15004-62-33-52-3
News/Update800-12003-51-33-53-5

Step 4: Optimize for Featured Snippets

Target featured snippets with these patterns:

Paragraph snippet (definition/what is):

## What Is {Topic}?

{Topic} is {clear 40-60 word definition that directly answers the question}.
{Additional context in 1-2 more sentences}.

List snippet (how-to/best of):

## How to {Action}

1. **{Step 1 title}** - Brief description
2. **{Step 2 title}** - Brief description
3. **{Step 3 title}** - Brief description
...

Table snippet (comparison/data):

## {Comparison Topic}

| {Column 1} | {Column 2} | {Column 3} |
|------------|------------|------------|
| {Data} | {Data} | {Data} |

Step 5: Add Supporting Elements

Image suggestions: For each major section, suggest an image:

[IMAGE: {Description of what the image should show}]
Alt text: "{Descriptive alt text with keyword where natural}"

Image types to suggest:

  • Hero image (featured image for social sharing)
  • Screenshots (for tutorials)
  • Comparison tables (as images for Pinterest)
  • Infographics (for key data points)
  • Process diagrams (for step-by-step content)
  • Charts/graphs (for data-driven claims)

Sourcing Featured Images from Unsplash (if UNSPLASH_CLIENT_ID available):

Use the Unsplash API to find high-quality, royalty-free featured images for the blog post:

# Search Unsplash for a relevant featured image
curl -s "https://api.unsplash.com/search/photos?query={topic}&per_page=5&orientation=landscape" \
  -H "Authorization: Client-ID ${UNSPLASH_CLIENT_ID}"

Parsing the response:

The JSON response contains a results array. For each photo, extract:

# Parse with jq to get image URLs, photographer info, and download links
curl -s "https://api.unsplash.com/search/photos?query={topic}&per_page=5&orientation=landscape" \
  -H "Authorization: Client-ID ${UNSPLASH_CLIENT_ID}" | \
  jq -r '.results[] | {
    id: .id,
    description: .description,
    image_url: .urls.regular,
    full_url: .urls.full,
    download_link: .links.download,
    photographer_name: .user.name,
    photographer_url: .user.links.html,
    unsplash_url: .links.html
  }'

Key fields from the response:

  • .urls.regular - Optimized image (1080px wide, good for blog featured images)
  • .urls.full - Full resolution image
  • .urls.small - Thumbnail (400px wide, good for social sharing previews)
  • .links.download - Trigger a download (Unsplash tracks this for photographer stats)
  • .user.name - Photographer's name (required for attribution)
  • .user.links.html - Photographer's Unsplash profile URL

Unsplash attribution requirement:

Unsplash requires attribution whenever you use a photo. Include this in the blog post:

Photo by [Photographer Name](https://unsplash.com/@username?utm_source=your_app&utm_medium=referral) on [Unsplash](https://unsplash.com/?utm_source=your_app&utm_medium=referral)

Place the attribution either:

  • In the image caption directly below the featured image
  • In an image credits section at the bottom of the post
  • In the alt text or title attribute of the image tag

Tip: Search with specific, descriptive queries rather than broad terms. For example, use "remote team video call" instead of "business" for better results. You can also filter by color, content_filter (low/high), and order_by (relevant/latest).

Internal link placement:

  • Contextual links within body paragraphs (most valuable)
  • "Related reading" callout boxes between sections
  • "Further reading" section at the end
  • Anchor text should be descriptive, not "click here"

External link rules:

  • Link to authoritative sources (studies, official docs,.edu,.gov)
  • Open external links in new tab
  • No-follow affiliate links and sponsored content
  • Cite statistics with linked sources

Step 6: FAQ Section

Every blog post should end with a FAQ section targeting "People Also Ask":

## Frequently Asked Questions

### {Question matching PAA or long-tail keyword}?

{Direct answer in 2-4 sentences. Front-load the answer.
Provide additional context after the direct answer.
This format optimizes for both featured snippets and FAQ rich results.}

### {Second question}?

{Answer}

FAQ rules:

  • 4-6 questions
  • Questions should use natural language (how, what, why, when, can, does)
  • Answer the question in the first sentence
  • Keep each answer under 100 words
  • Include schema markup (see schema-markup skill)

Step 7: Final Quality Check

Before delivering the post, verify:

SEO Checklist:

  • Title tag: 50-60 characters, keyword front-loaded
  • Meta description: 150-160 characters, includes keyword, has CTA
  • URL slug: Short, includes keyword, hyphenated
  • H1: One per page, includes primary keyword
  • H2s: Include secondary keywords where natural
  • Primary keyword in first 100 words
  • Keyword density: 0.5-1.5%
  • Internal links: 5+ contextual links
  • External links: 3+ authoritative sources
  • Images: Alt text on all, keyword in at least one
  • FAQ section with 4-6 questions
  • Word count meets target for content type
  • No duplicate content or thin sections

Readability Checklist:

  • Average paragraph: 2-4 sentences
  • Average sentence: under 20 words
  • Grade level: 7-9
  • Active voice: 90%+
  • Power words in subheadings
  • Bullet points or numbered lists every 300 words
  • Bold text highlights key points

E-E-A-T Checklist:

  • Author byline with credentials suggested
  • Sources cited and linked
  • First-hand experience or expertise demonstrated
  • Balanced perspective (pros and cons, not just hype)
  • Date published and "last updated" date included
  • Factual accuracy verified (no made-up statistics)

Output Format

Deliver the blog post in this format:

---
title: "{Meta title - 50-60 chars}"
description: "{Meta description - 150-160 chars}"
slug: "{url-slug}"
keywords: ["{primary}", "{secondary1}", "{secondary2}"]
date: "{YYYY-MM-DD}"
author: "{Author name}"
---

# {H1 Headline}

{Full article content with all formatting, links, and image placeholders}

After the article, provide:

  1. SEO metadata summary (title, description, slug, word count)
  2. Internal linking recommendations (which pages to link to/from)
  3. Schema markup (Article or BlogPosting JSON-LD)
  4. Social sharing (suggested OG title, description, and image concept)
  5. Content promotion ideas (2-3 distribution channels and angles)

Important Notes

  • Never fabricate statistics. If citing a number, include the source or note "[Source needed]".
  • Write for humans first, search engines second. If an SEO tactic makes the content worse for readers, skip it.
  • Every section must provide value. No filler paragraphs. If a section doesn't teach, convince, or entertain, cut it.
  • Match the user's brand voice if they specify one. Ask if not clear.
  • If the topic is YMYL (health, finance, legal), be extra careful with claims and heavily cite authoritative sources.

平台分布

Codex

37.66%
按下载量换算374

Claude

30.59%
按下载量换算304

Cursor

19.83%
按下载量换算197

Gemini CLI

9.22%
按下载量换算92

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills