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

blog-rewrite博客重写

Agent Skill

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

总安装

2,375

周安装

102

GitHub Stars

619

下载量

832
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

blog-rewrite 用于重写现有博客文章以提升双平台排名表现,适合在 Codex、Claude、Cursor、Gemini CLI 中需要优化已发布内容时使用。

  • 它保留作者原话的同时强化 E-E-A-T 信号与内部链接策略,兼顾谷歌搜索与 AI 引用平台。
  • 使用时先执行只读审计再生成修改建议,避免破坏原有事实准确性。
  • 安装前建议确认是否修改原始文件及版本控制集成方式。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Blog Rewriter -- Optimize Existing Posts

Rewrites and optimizes existing blog posts for dual ranking: Google search and AI citation platforms. Preserves the author's voice while applying the 6 pillars of optimization.

Key references:

  • 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: Audit (Read-Only)

  1. Read the blog post - Detect format (MDX, markdown, HTML)
  2. Run the quality checklist against references/quality-scoring.md:

- Count fabricated vs sourced statistics - Check answer-first formatting (H2 -> stat in first sentence?) - Count images and charts (type diversity?) - Measure paragraph lengths (any > 150 words?) - Check heading hierarchy (H1 -> H2 -> H3, no skips?) - Look for FAQ schema - Check freshness signals (lastUpdated, dateModified) - Assess self-promotion level - Evaluate citation tier quality

  1. AI content detection scan:

- Burstiness score - Measure sentence length variance across the post. Low variance (most sentences within 3-5 words of each other) is a strong AI signal. Calculate: standard deviation of sentence word counts. Target SD > 6. - Known AI phrase scan - Check for these high-frequency AI phrases: - "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 - Vocabulary diversity - Calculate Type-Token Ratio (TTR): unique words / total words. Low TTR (< 0.40) suggests AI-generated repetitive phrasing. Target TTR > 0.50 for natural prose. - AI content percentage estimate - Based on burstiness, phrase density, and TTR, estimate what percentage of the content reads as AI-generated (0-100%). Report as: "AI content estimate: ~X%"

  1. Video embed check:

- Count existing YouTube embeds in the post - If 0 embeds, flag: "No video embeds. YouTube has the strongest AI visibility correlation (0.737)" - If present, check: lazy loading? aria-labels? noscript fallback? VideoObject schema?

  1. Cannibalization check:

- Identify the post's primary keyword from title, H1, and first paragraph - Search the blog directory for other posts targeting the same keyword: - Grep headings and meta descriptions across all blog posts - Flag any posts with significant keyword overlap - If cannibalization found, report: - Which posts compete for the same keyword - Recommend: merge (combine into one stronger post) or differentiate (shift one post to a related but distinct keyword)

  1. Calculate current score across 5 categories:

- Score across 5 categories (Content Quality 30, SEO Optimization 25, E-E-A-T Signals 15, Technical Elements 15, AI Citation Readiness 15) - Total: 0-100

  1. Present audit summary with specific findings, AI detection results, video status, cannibalization status, and score
  2. Enter plan mode - Present section-by-section optimization plan

Wait for user approval before proceeding.

Phase 2: Research

  1. Identify the blog's core topic from existing content
  2. Find replacement statistics for any fabricated/unsourced data:

- Search: [topic] study 2025 2026 data statistics - Target tier 1-3 sources only

  1. Find images if post has fewer than 3:

- Pixabay: site:pixabay.com [topic keywords] - Unsplash: site:unsplash.com [topic keywords] - Verify each URL returns HTTP 200 - If nanobanana-mcp is configured, offer AI generation for missing/insufficient images via blog-image

  1. Plan charts if post has fewer than 2:

- Identify data suitable for visualization - Select diverse chart types

Phase 3: Chart Generation (Built-In)

When the post needs more visual elements, invoke the blog-chart sub-skill:

  1. Select chart type using the diversity rule (no repeated types per post)
  2. Pass: chart type, title, data values, source, platform format
  3. Embed the returned SVG directly within a <figure> wrapper
  4. Target 2-4 charts per 2,000-word post

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

Phase 4: Content Rewrite

Apply changes in this order:

4a. Preserve What Works

  • Keep the author's voice and unique perspective
  • Preserve original insights and first-hand experience
  • Keep existing quality images and charts
  • Maintain internal links

4b. Fix Frontmatter

  • Add lastUpdated: "YYYY-MM-DD" (today's date)
  • Keep original date unchanged
  • Fix meta description: fact-dense, 150-160 chars, includes 1 statistic
  • Add coverImage + coverImageAlt + ogImage if missing

- Search Pixabay/Unsplash/Pexels for wide hero image (1200x630) - Or generate custom SVG cover via blog-chart (text-on-gradient with key stat) - Or generate custom AI image via blog-image sub-skill (if nanobanana-mcp configured)

  • Verify tags/categories are appropriate

4c. Apply Answer-First Formatting

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

4d. Replace Fabricated Statistics

  • Search for patterns: "X% of...", "X out of Y...", unsourced claims
  • Replace with real data from tier 1-3 sources
  • Always include inline attribution: ([Source Name](url), year)

4e. Improve Headings

  • Convert statement headings to questions where natural (60-70% target)
  • Keep 2-3 statement headings for variety
  • Ensure keyword appears in 2-3 headings naturally

4f. Fix Paragraph Length

  • Split any paragraph > 150 words
  • Target 40-80 words per paragraph
  • Ensure each paragraph starts with its most important sentence

4g. Add Visual Elements

  • Embed new images after H2 headings, spaced evenly
  • Embed charts within relevant sections
  • If nanobanana-mcp configured: generate custom images for sections lacking good stock matches (invoke blog-image sub-skill via Task)
  • Adapt embed format to detected platform (MDX vs markdown vs HTML)

4h. Add Video Embeds

If the post lacks YouTube video embeds:

  • Search 2-3 relevant videos using quality criteria from references/video-embeds.md
  • Embed using platform-appropriate format (srcdoc lazy loading)
  • Place: 1 after introduction, 1-2 in mid-article sections
  • Include noscript fallback for AI crawlers

4i. Add/Improve FAQ

  • If no FAQ exists, add one (3-5 questions)
  • If FAQ exists, ensure answers are 40-60 words with statistics
  • Add FAQ schema markup appropriate to platform

4j. Reduce Self-Promotion

  • Max 1 brand mention (author bio context only)
  • Remove "At [Company], we..." patterns
  • Convert promotional sections to educational content

4k. Citation Capsule Injection

For each H2 section, generate (or improve existing) a citation capsule:

  • 40-60 word self-contained passage per H2
  • Contains: one specific claim + one data point + source attribution
  • Written in a declarative style so an AI system could extract and quote it directly
  • Placed naturally within the section body, not as a separate callout

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" category (15 points) in references/quality-scoring.md.

4l. Anti-AI-Detection Patterns

Apply these transformations to reduce AI-detectable writing patterns:

  • Eliminate em dashes - Replace every em dash (-) with a comma, hyphen (-), colon, or period. Split sentences if needed. Em dashes are an AI writing tell.
  • Replace flagged phrases - Swap every detected AI phrase (from the scan in Phase 1 step 3) with a natural alternative. Examples:

- "it's important to note" -> "worth noting" or "keep in mind" - "in today's digital landscape" -> "right now" or "in [specific year]" - "leverage" -> "use", "apply", "take advantage of" - "delve" -> "look at", "explore", "dig into" - "robust" -> "strong", "solid", "reliable" - "crucial" -> "key", "essential", "critical" (or restructure the sentence)

  • Vary sentence length deliberately - After rewriting, scan each paragraph. Inject short punchy sentences (5-10 words) between longer ones (18-25 words). Target: no more than 3 consecutive sentences within 5 words of each other's length.
  • Inject rhetorical questions - Add at least one rhetorical question every 200-300 words to break up declarative monotony.
  • Use contractions naturally - Replace formal constructions with contractions where they sound natural: "it is" -> "it's", "we have" -> "we've", "do not" -> "don't", "is not" -> "isn't".
  • Include hedging language - Sprinkle first-person hedges that signal real experience: "in our experience", "we've found that", "from what we've seen", "this tends to", "it depends on".

4m. Summary Box (Key Takeaways)

If the post lacks a summary box, add one immediately after the introduction:

> **Key Takeaways**
> - [Core finding with statistic and source]
> - [Second key insight or recommendation]
> - [Third actionable takeaway]
> (3-5 bullets, 40-60 words combined. Self-contained - reader gets
> the core value without reading the full article.)

Default label is "Key Takeaways", but this is configurable per persona or brand voice (e.g., "The Bottom Line", "Quick Summary", "What You Need to Know").

If an existing TL;DR box is present, convert it to the bullet-point Key Takeaways format. Verify it meets the 40-60 word requirement and contains at least one statistic with source attribution.

4n. Information Gain Marker Injection

Review the post for original value and tag it:

  • [ORIGINAL DATA] - Any proprietary data, survey results, experiments, or case study metrics the author collected first-hand
  • [PERSONAL EXPERIENCE] - First-hand observations, lessons learned
  • [UNIQUE INSIGHT] - Novel analysis, contrarian perspectives backed by data

If the post lacks original value markers:

  • Ask the author for first-hand data or experience to include
  • At minimum, add analytical insights that connect existing research in new ways
  • Target: at least 2-3 markers per post

Use HTML comments (<!-- [ORIGINAL DATA] -->) or visible callouts depending on the post's style.

Phase 5: Verification

After rewriting, verify all quality gates pass:

Core Quality Gates

  1. Every H2 opens with a statistic + source
  2. No paragraph exceeds 150 words
  3. Zero fabricated statistics
  4. Heading hierarchy is clean
  5. FAQ section present with schema
  6. Images have descriptive alt text
  7. Cover image present in frontmatter (coverImage + ogImage)
  8. If MDX: build the project to verify no compilation errors

New Element Verification

  1. TL;DR box present after introduction (40-60 words, contains statistic)
  2. At least 2-3 information gain markers present
  3. Citation capsules in major H2 sections (40-60 words, self-contained)
  4. Internal linking zones marked or actual links present (5-10 per 2,000 words)
  5. No AI-detectable phrases remain from banned list

Burstiness and Naturalness Check

  1. Sentence length variance: SD > 6 (mix of short and long sentences)
  2. Contractions used naturally throughout
  3. Rhetorical questions present (1 per 200-300 words)
  4. AI content estimate reduced from audit baseline
  5. Score improved across all 5 categories vs Phase 1 audit
  6. YouTube video embeds present with lazy loading, aria-labels, and noscript fallback

Phase 6: Summary

## Blog Optimization Complete: [Title]

### Score Change
- Before: [X]/100 ([Rating])
  - Content Quality: [X]/30
  - SEO Optimization: [X]/25
  - E-E-A-T Signals: [X]/15
  - Technical Elements: [X]/15
  - AI Citation Readiness: [X]/15
- After: [Y]/100 ([Rating])
  - Content Quality: [Y]/30
  - SEO Optimization: [Y]/25
  - E-E-A-T Signals: [Y]/15
  - Technical Elements: [Y]/15
  - AI Citation Readiness: [Y]/15

### AI Detection
- Before: ~[X]% AI-detected content
- After: ~[Y]% AI-detected content
- Phrases replaced: [N]
- Burstiness improved: [before SD] -> [after SD]

### Cannibalization
- [Status: none found / flagged N posts / resolved]

### Changes Made
- [X] statistics replaced with sourced data
- [X] SVG charts added (types: ...)
- [X] images added from Pixabay/Unsplash
- Answer-first formatting applied to [N] H2 sections
- FAQ schema injected with [N] questions
- TL;DR box: [added/updated]
- Information gain markers: [N] ([types])
- Citation capsules: [N] across H2 sections
- AI phrases replaced: [N]
- lastUpdated set to [date]
- Self-promotion reduced to [N] mentions

### Visual Elements
- Charts: [count] ([types])
- Images: [count]
- YouTube videos: [count] ([titles])

### Ready for
- `/blog analyze <file>` to verify final score
- Publishing / deploying

Update Mode

When invoked as /blog update <file>, focus on freshness:

  1. Update statistics to latest available data (2025-2026)
  2. Add new developments since last update
  3. Refresh images if older than 1 year
  4. Update lastUpdated in frontmatter
  5. Preserve the existing structure - minimize rewrites
  6. Target: at least 30% content change to register as "fresh" for AI crawlers

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

40.21%
按下载量换算335

Claude

28.97%
按下载量换算241

Cursor

19.15%
按下载量换算159

Gemini CLI

9.6%
按下载量换算80

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

来源信息

继续浏览同类 Skills