Token导航 LogoToken导航

Agent Skill · 研究检索

blog-write(博客写)

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

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

总安装 2,328周安装 99GitHub Stars 619下载 816核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

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

blog-write 用于从零开始撰写完整博客文章,适合在 Codex、Claude、Cursor、Gemini CLI 中需要高质量原创内容产出时使用。它遵循双平台优化六支柱原则,融合 E-E-A-T 信号与视觉媒体规范。使用时提供主题或提纲即可生成带内部链接与结构化数据的成品文件。

安装前建议确认是否引用外部参考资料库及版权声明嵌入机制。blog-write 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

blog-write 怎么安装?

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

blog-write 支持哪些 AI 工具?

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

blog-write 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/agricidaniel/claude-blog --skill blog-write 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

blog-write 是免费的吗?

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

blog-write 用的人多吗?

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

blog-write 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
blog-write

博客写 · 本页

2,328619执行命令未明确有提醒

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

SKILL.md 原文

Blog Writer -- New Article Generation

Writes complete blog articles from a topic, brief, or outline. Every article follows the 6 pillars of dual optimization (Google rankings + AI citations).

Key references:

  • references/content-templates.md - Template selection guide and usage
  • references/quality-scoring.md - 5-category scoring (Content 30, SEO 25, E-E-A-T 15, Technical 15, AI Citation 15)
  • references/eeat-signals.md - Experience, expertise, authority, trust markers
  • references/internal-linking.md - Linking strategy and anchor text rules
  • references/visual-media.md - Image sourcing and chart styling

Workflow

Phase 1: Topic Understanding

  1. Clarify the topic - If the user provides just a topic, ask:

- Target audience (who is this for?) - Primary keyword / search intent - Desired word count (default: 2,000-2,500 words) - Platform/format (MDX, markdown, HTML - auto-detect if in a project)

  1. If a brief exists - Load it and skip to Phase 1.5

Phase 1.5: Template Selection

Select the appropriate content template from the 12 templates in templates/.

  1. Auto-detect content type from the topic and search intent: Signal Template "How to...", process, steps how-to-guide "Best X", "Top N", list format listicle Client result, before/after, metrics case-study "X vs Y", comparison, alternatives comparison Broad topic, comprehensive guide pillar-page "Is X worth it", product evaluation product-review Opinion, prediction, industry take thought-leadership Expert quotes, multi-source collection roundup Code walkthrough, tool demo, technical tutorial Breaking news, algorithm update, event news-analysis Survey results, experiment, original data data-research Q&A, knowledge base, "What is X" faq-knowledge
  2. Load the matching template - Read from templates/<type>.md
  3. Adapt the outline - Use the template's section structure, heading patterns, and word count guidance to shape Phase 3's outline
  4. Fallback - If no template clearly fits, use the generic outline structure in Phase 3 below. Inform the user which template was selected (or that none matched).

See references/content-templates.md for detailed selection criteria and intent mapping.

Phase 2: Research

Spawn a blog-researcher agent (or do inline research with WebSearch):

  1. Find 8-12 current statistics (2025-2026 data preferred)

- Search: [topic] study 2025 2026 data statistics - Prioritize tier 1-3 sources (see references/quality-scoring.md) - Record: statistic, source name, URL, date, methodology

  1. Find a cover image (wide, high-quality, topic-relevant):

- Search: site:pixabay.com [topic] wide banner (preferred) - Alternative: site:unsplash.com [topic] wide - Fallback: site:pexels.com [topic] wide banner - Target dimensions: 1200x630 (OG-compatible) or 1920x1080 - Or generate a custom SVG cover via blog-chart (text-on-gradient with key stat) - Or generate a custom AI image via blog-image sub-skill (if nanobanana-mcp configured) - See references/visual-media.md for cover image sizing details

  1. Find 3-5 inline images from open-source platforms:

- Pixabay (preferred): Search site:pixabay.com [topic keywords] - Extract image URL from page - Direct URLs: https://cdn.pixabay.com/photo/YYYY/MM/DD/HH/MM/filename.jpg - Verify with curl -sI "<url>" | head -1 returns HTTP 200 - Unsplash (alternative): Search site:unsplash.com [topic keywords] - Build URL: https://images.unsplash.com/photo-<id>?w=1200&h=630&fit=crop&q=80 - Pexels (fallback): Search site:pexels.com [topic keywords]

  1. Plan 2-4 data visualizations from researched statistics

- Select diverse chart types (see references/visual-media.md) - Map data points to chart formats

  1. AI image generation (optional, if nanobanana-mcp configured):

- If stock photo results are insufficient (< 3 good matches) or topic is too niche - Generate custom hero image and/or inline illustrations via blog-image sub-skill - Stock photos remain default - AI generation supplements, never replaces

  1. NotebookLM research (optional, if user has relevant notebooks):

- If the user mentions a NotebookLM notebook or the topic aligns with a configured notebook - Query via blog-notebooklm for source-grounded data from user-uploaded documents - Treat NotebookLM responses as Tier 1 sources (user's own primary documents) - Falls back silently if not configured or not authenticated

  1. Find relevant YouTube videos (2-3 per post):

- Use blog-google youtube command or WebSearch site:youtube.com [topic] [year] - Apply quality criteria from references/video-embeds.md (min score 50/100) - Select 2-3 best videos. Falls back silently if none found.

Phase 3: Outline Generation

Create a structured outline before writing. If a template was loaded in Phase 1.5, adapt this skeleton to match the template's section structure:

# [Title as Question - Include Primary Keyword]

## Introduction (100-150 words)
- Hook with surprising statistic
- Problem/opportunity statement
- What the reader will learn

> **Key Takeaways**
> - [Core finding with statistic and source]
> - [Second key insight or recommendation]
> - [Third actionable takeaway]
> (3-5 bullets, 40-60 words combined)

## H2: [Question Format] (300-400 words)
- Answer-first paragraph (40-60 words with stat + source)
- Supporting evidence
- [Image placement]
- Practical advice
- [CITATION CAPSULE placeholder]
- [INTERNAL-LINK: anchor text → target description]

## H2: [Question Format] (300-400 words)
- Answer-first paragraph
- [Chart: type + data description]
- Analysis and implications
- [CITATION CAPSULE placeholder]
- [INTERNAL-LINK: anchor text → target description]

## H2: [Statement for Variety] (300-400 words)
- Answer-first paragraph
- Real-world example or case study
- [Image placement]
- [CITATION CAPSULE placeholder]

## H2: [Question Format] (300-400 words)
- Answer-first paragraph
- [Chart: type + data description]
- Step-by-step guidance
- [CITATION CAPSULE placeholder]
- [INTERNAL-LINK: anchor text → target description]

## H2: [Question Format] (200-300 words)
- Answer-first paragraph
- Forward-looking analysis

## [CTA Section or Inline Placement]
- See `references/cta-placement.md` for placement rules by content type
- Place CTA after value delivery, not at arbitrary positions
- Single focused CTA per post (266% more conversions)
- [CTA: contextual call-to-action matching article topic]

## FAQ Section (3-5 questions, 40-60 words each answer)
- [INTERNAL-LINK: anchor text → detailed content]

## Conclusion (100-150 words)
- Key takeaways (bulleted)
- Call to action
- [INTERNAL-LINK: anchor text → next logical content]

Present the outline to the user for approval before writing.

Visual element pacing: Insert [IMAGE], [CHART], [VIDEO], or [CALLOUT] markers every 300-500 words. Alternate types (no consecutive same-type). See references/content-rules.md Visual Rhythm section and references/cta-placement.md for CTA positioning.

Phase 4: Chart Generation (Built-In)

When the researcher identifies chart-worthy data (3+ comparable metrics, trend data, before/after comparisons):

  1. Select chart type using the diversity rule (no repeated types per post)
  2. Invoke blog-chart sub-skill with: chart type, title, data values, source, platform format
  3. Embed the returned SVG directly in the post within a <figure> wrapper
  4. Target 2-4 charts per 2,000-word post
  5. Distribute charts evenly - never cluster them

See references/visual-media.md for chart type selection and styling rules.

Phase 5: Content Writing

Write the full article following these rules:

5a. Frontmatter
---
title: "[Question-format title with primary keyword]"
description: "[Fact-dense, 150-160 chars, includes 1 statistic]"
coverImage: "[URL from Pixabay/Unsplash/Pexels or generated SVG path]"
coverImageAlt: "[Descriptive sentence about the cover image]"
ogImage: "[Same as coverImage, or custom OG image URL]"
date: "YYYY-MM-DD"
lastUpdated: "YYYY-MM-DD"
author: "[Author name]"
tags: ["keyword1", "keyword2", "keyword3"]
---

If the platform uses a different field name (e.g., image, hero, thumbnail), adapt to match the project's existing frontmatter convention.

5b. Summary Box (Key Takeaways)

Immediately after the introduction (before the first H2 body section), add a summary box:

> **Key Takeaways**
> - [Core finding with statistic] ([Source], year)
> - [Second key insight or recommendation]
> - [Third actionable takeaway]

Requirements:

  • 3-5 bullet points, 40-60 words combined
  • Must be self-contained - understandable without reading the article
  • Include 1 specific statistic with source name
  • State the key finding, recommendation, or answer
  • Default label: "Key Takeaways". If a persona is active, use the persona's summary_label
  • Backward compatible: accept existing TL;DR boxes during rewrites
5c. Answer-First Formatting (Critical)

Every H2 section MUST open with a 40-60 word paragraph containing:

  • At least one specific statistic with source attribution
  • A direct answer to the heading's implicit question

Pattern:

## How Does X Impact Y in 2026?

[Stat from source] ([Source Name](url), year). [Direct answer to the heading
question in 1-2 more sentences, explaining the implication and what this means
for the reader.]
5d. Information Gain Markers

Distribute at least 2-3 information gain markers throughout the article. These signal to search engines and AI systems that the content contains original value not available elsewhere.

Tag each with a comment or visible marker:

  • [ORIGINAL DATA] - Proprietary surveys, experiments, A/B test results, case study metrics the author collected first-hand
  • [PERSONAL EXPERIENCE] - First-hand observations, lessons learned from direct involvement, "when we tried X, Y happened" narratives
  • [UNIQUE INSIGHT] - Analysis others haven't made, contrarian perspectives backed by data, novel connections between existing research

Placement:

  • Weave into the body text naturally
  • Use as inline comments: <!-- [ORIGINAL DATA] --> before the relevant paragraph
  • Or as visible callouts if the format supports it: > **Our finding:** [original observation backed by specific data]
  • Minimum 2 per post, target 3 for comprehensive articles

These markers map directly to the "Originality/unique value markers" criterion in the Content Quality scoring category (see references/quality-scoring.md).

5e. Citation Capsules

For each major H2 section, generate a citation capsule - a 40-60 word self-contained passage designed so AI systems can extract and quote it directly.

Requirements per capsule:

  • 40-60 words, self-contained (makes sense in isolation)
  • Contains: one specific claim + one data point + source attribution
  • Written in a declarative, quotable style
  • Placed within the H2 section body (not as a separate block)

Example:

According to a 2026 Gartner study, 58% of enterprise buyers now consult AI
assistants before contacting a vendor ([Gartner](https://www.gartner.com), 2026).
This shift means B2B content must answer specific questions concisely enough
for AI systems to extract and cite in their responses.

Capsules map to the "AI Citation Readiness" scoring category (15 points) in references/quality-scoring.md.

5f. Internal Linking Zones

Mark internal linking opportunities throughout the article using placeholder notation. The user (or a follow-up pass) will resolve these to actual URLs.

Zone placement:

  • Introduction - Link to related pillar content or topic hub
  • Each H2 section - Link to supporting articles, deeper dives, related tools
  • FAQ section - Link answers to detailed content that expands on the answer
  • Conclusion - Link to the next logical piece of content the reader should consume

Format:

[INTERNAL-LINK: anchor text → target description]

Example:

For a deeper dive into keyword clustering, see our
[INTERNAL-LINK: complete guide to keyword clustering → pillar page on keyword research methodology].

Target 5-10 internal link zones per 2,000-word post. Use descriptive anchor text (never "click here" or "read more"). See references/internal-linking.md for anchor text rules and linking strategy.

5g. Paragraph Rules
  • Every paragraph: 40-80 words (never exceed 150)
  • Every sentence: max 15-20 words
  • Start each paragraph with the most important information
  • Target Flesch Reading Ease: 60-70
5h. Heading Rules
  • One H1 (title only)
  • H2s for main sections (60-70% as questions)
  • H3s for subsections only - never skip levels
  • Include primary keyword naturally in 2-3 headings
5i. Image Embedding

Standard markdown:

![Descriptive alt text - topic keywords naturally](https://cdn.pixabay.com/photo/...)

MDX with Next.js Image (if detected):

![Descriptive alt text - topic keywords naturally](https://cdn.pixabay.com/photo/...)
  • Place images after H2 headings, before body text
  • Space evenly throughout the post (not clustered)
  • Alt text should be a full descriptive sentence
5j. Chart Embedding

Standard markdown/HTML:

<figure>
  <svg viewBox="0 0 560 380" ...>...</svg>
  <figcaption>Source: [Source Name], [Year]</figcaption>
</figure>

MDX format:

<figure className="chart-container" style={{margin: '2.5rem 0', textAlign: 'center', padding: '1.5rem', borderRadius: '12px'}}>
  <svg viewBox="0 0 560 380" ...>...</svg>
</figure>
5k. Video Embedding

Embed YouTube videos using srcdoc lazy-loading pattern from references/video-embeds.md. Include aria-label, noscript fallback for AI crawlers. Place after relevant H2, 500+ words apart.

5l. Citation Format

Inline attribution (always):

Organic CTR declined 61% with AI Overviews ([Seer Interactive](https://www.seerinteractive.com/), 2025).
5m. FAQ Section

Add 3-5 FAQ items with 40-60 word answers. Each answer must contain a statistic.

For MDX with FAQSchema component:

<FAQSchema faqs={[
  { question: "Question?", answer: "40-60 word answer with statistic and source." },
]} />

For standard markdown:

## Frequently Asked Questions

### Question text here?

Answer with statistic and source attribution (40-60 words).
5n. Internal Linking
  • 5-10 internal links per 2,000-word post
  • Link to relevant existing content naturally
  • Use descriptive anchor text (not "click here")

Phase 6: Quality Check

Before delivering, verify:

Structure and Content
  1. Every H2 opens with a statistic + source
  2. No paragraph exceeds 150 words
  3. All statistics have named tier 1-3 sources
  4. 2-4 charts with type diversity
  5. 3-5 inline images with descriptive alt text
  6. Cover image present in frontmatter (coverImage + ogImage)
  7. FAQ section present with 3-5 items
  8. Heading hierarchy is clean (H1 -> H2 -> H3)
  9. Meta description is 150-160 chars with a stat
New Element Verification
  1. TL;DR box present after introduction (40-60 words, contains statistic + source)
  2. At least 2-3 information gain markers ([ORIGINAL DATA], [PERSONAL EXPERIENCE], or [UNIQUE INSIGHT])
  3. Citation capsules present in major H2 sections (40-60 words, self-contained, quotable)
  4. Internal linking zones marked in introduction, H2 sections, FAQ, and conclusion
  5. No AI-detectable phrases from banned list (see agents/blog-writer.md)
Burstiness and Naturalness Check
  1. Sentence length variance - Verify a mix of short (8-word) and long (25-word) sentences. Uniform sentence length signals AI authorship.
  2. Banned AI phrase scan - Check for and remove:

- "in today's digital landscape", "it's important to note", "dive into" - "game-changer", "navigate the landscape", "revolutionize", "seamlessly" - "cutting-edge", "harness the power of", "leverage" (as verb) - "delve", "crucial", "elevate", "foster", "landscape" (overused) - "multifaceted", "robust", "tapestry", "embark" - Full list in agents/blog-writer.md

  1. Contractions - Verify natural use of contractions ("it's", "we've", "don't", "isn't"). Formal AI prose avoids contractions; natural writing uses them.
  2. Rhetorical questions - Verify at least one rhetorical question every 200-300 words to break up declarative patterns.
  3. YouTube videos - 2-3 embeds with lazy loading, aria-labels, and noscript fallback (see references/video-embeds.md)

Phase 7: Delivery

Present the completed article with a summary:

## Blog Post Complete: [Title]

### Template Used
- [Template name] (or "generic outline - no template matched")

### Statistics
- [N] sourced statistics from tier 1-3 sources
- [N] unique sources cited

### Visual Elements
- Cover image: [source - Pixabay/Unsplash/Pexels or generated SVG]
- [N] inline images (Pixabay/Unsplash/Pexels)
- [N] SVG charts (types: bar, lollipop, donut, line)
- [N] YouTube video embeds (titles: ...)

### Dual-Optimization Elements
- TL;DR box: present (N words)
- Information gain markers: [N] ([types used])
- Citation capsules: [N] across H2 sections
- Internal linking zones: [N] marked

### Structure
- [N] H2 sections with answer-first formatting
- [N] FAQ items with schema
- Word count: ~[N] words
- Estimated reading time: [N] min

### Naturalness
- Sentence length variance: [pass/fail]
- AI phrase scan: [pass/fail]
- Contractions used: [yes/no]
- Rhetorical questions: [N] (target: 1 per 200-300 words)

### Next Steps
- Review and customize for your brand voice
- Resolve [INTERNAL-LINK] placeholders with actual URLs
- Add internal links to your existing content
- Run `/blog analyze <file>` to verify quality score
- Generate VideoObject schema: `/blog schema <file>` (includes video markup)
- Generate audio narration: `/blog audio generate <file>` (optional)

平台分布

Codex

36%
按下载量换算294

Claude

30.71%
按下载量换算251

Cursor

19%
按下载量换算155

Gemini CLI

10.46%
按下载量换算85

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/agricidaniel/claude-blog --skill blog-write 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills