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

blog-brief博客简介

Agent Skill

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

总安装

2,375

周安装

97

GitHub Stars

619

下载量

768
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

用于生成面向搜索引擎优化的内容简报,指导文章结构与分发策略。

  • 适合市场团队规划选题方向或内容创作者快速对齐目标读者需求。
  • 结合意图分类与竞争分析,输出带内部链接建议的传播蓝图。
  • 安装方式:GitHub 仓库,使用 npx skills add 命令添加;需提供关键词与受众画像。
  • 注意:简报仅为起点,实际写作仍需深入调研与个性化调整。

SKILL.md

Blog Brief Generator -- Content Planning

Generates comprehensive content briefs that guide blog writing for maximum impact on both Google rankings and AI citation platforms.

Reference documents:

  • references/content-templates.md -- template selection criteria
  • references/distribution-playbook.md -- channel-specific distribution tactics
  • references/internal-linking.md -- link architecture patterns

Workflow

Step 1: Topic Intake

Gather from the user:

  1. Topic or keyword (required)
  2. Target audience (who reads this?)
  3. Search intent -- Informational, commercial, transactional, navigational
  4. Business context -- What does the company do? What's the CTA?

If only a topic is given, infer the rest from context.

Step 2: Keyword Research

Using WebSearch:

  1. Search for the target keyword -- analyze what currently ranks
  2. Identify primary keyword (exact match target)
  3. Identify 3-5 secondary keywords (related terms, long-tail)
  4. Identify 3-5 question queries (People Also Ask style)
  5. Note the search intent -- what do searchers actually want?

Step 2.5: Template Recommendation

Analyze the topic, search intent, and competitive landscape to recommend one of 12 content templates. Load references/content-templates.md for selection criteria.

Available templates:

TemplateBest For
how-to-guideStep-by-step instructional content
listicleCurated lists, ranked items, resource roundups
case-studyIn-depth analysis of a specific example or result
comparisonSide-by-side evaluation of 2+ options
pillar-pageComprehensive topic hub linking to cluster content
product-reviewDetailed evaluation with pros/cons/verdict
thought-leadershipExpert opinion, industry trends, predictions
roundupExpert quotes, tool collections, best-of lists
tutorialTechnical walkthrough with code/config examples
news-analysisTimely coverage with expert commentary
data-researchOriginal data, survey results, benchmark findings
faq-knowledgeQuestion-driven reference content

Selection process:

  1. Match search intent to template strength
  2. Check what format top-ranking competitors use
  3. Consider the user's available assets (data, expertise, tools)
  4. Load the matching template file from templates/[type].md
  5. Include the template name in the brief output

Step 3: Competitive Analysis

Analyze the top 3-5 ranking pages for the target keyword:

  1. Content length -- What's the average word count?
  2. Heading structure -- How many H2s? What topics do they cover?
  3. Visual elements -- Do competitors use charts, images, videos?
  4. Content gaps -- What do all competitors miss?
  5. Freshness -- How recently were they updated?
  6. Schema -- Do they use FAQ or other rich results? (Note: HowTo deprecated Sept 2023)
  7. Template pattern -- What content format do top results use?

Step 4: Statistics Research

Find 8-12 statistics the article should include:

  1. Search: [topic] study 2025 2026 data statistics research
  2. Prioritize tier 1-3 sources
  3. For each stat, record: value, source, URL, date, methodology
  4. Identify 2-4 stats suitable for chart visualization
  5. Identify 1-2 stats suitable for TL;DR and social sharing

Step 5: Generate the Brief

Output format:

# Content Brief: [Title Suggestion]

## Template
**Recommended**: [template-name] -- [1-sentence rationale]
**Template file**: `templates/[type].md`

## Target Keywords
- **Primary**: [keyword] -- [estimated monthly search volume if available]
- **Secondary**: [keyword 1], [keyword 2], [keyword 3]
- **Questions**: [question 1], [question 2], [question 3]

## Search Intent
[Informational/Commercial/Transactional] -- [1-2 sentence explanation of
what the searcher wants]

## Content Parameters
- **Word count**: [2,000-2,500] words
- **Reading level**: Flesch 60-70 (expert-accessible)
- **Format**: [Markdown/MDX/HTML]
- **H2 sections**: [6-8]
- **Images**: 3-5 from Pixabay/Unsplash
- **Charts**: 2-4 via built-in blog-chart (diverse types)
- **FAQ items**: 3-5

## Recommended Title
[Question-format title including primary keyword, under 60 chars]

Alternative titles:
1. [Option 2]
2. [Option 3]

## Meta Description
[150-160 chars, fact-dense, includes 1 statistic, ends with value proposition]

## TL;DR Draft
> **TL;DR:** [40-60 word summary with key finding + 1 statistic + source.
> Should be self-contained -- a reader who only reads this box gets the
> core value of the article.]

## Information Gain Opportunities
- **[ORIGINAL DATA]**: [Suggestion for proprietary data, survey, experiment,
  or benchmark the author can produce to differentiate this post]
- **[PERSONAL EXPERIENCE]**: [Suggestion for first-hand observation, test
  result, or case study to include -- "When we tested X, we found Y"]
- **[UNIQUE INSIGHT]**: [Suggestion for contrarian take, novel analysis,
  or non-obvious connection that competitors have not covered]

## Content Outline

### Introduction (100-150 words)
- Hook: [Surprising statistic to open with]
- Problem: [What challenge does the reader face?]
- Promise: [What will they learn?]
- TL;DR box placement (after hook, before first H2)

### H2: [Question Format] (300-400 words)
- **Answer-first**: Open with [specific stat + source]
- Cover: [subtopic 1], [subtopic 2]
- **Image**: [Description of recommended image]
- **Key stat**: [Specific statistic to include]

### H2: [Question Format] (300-400 words)
- **Answer-first**: Open with [specific stat + source]
- Cover: [subtopic 1], [subtopic 2]
- **Chart**: [Type] showing [data description]
- **Key stat**: [Specific statistic to include]

[... repeat for 6-8 sections ...]

### FAQ Section (3-5 items)
1. [Question] -- Answer with [stat + source]
2. [Question] -- Answer with [stat + source]
3. [Question] -- Answer with [stat + source]

### Conclusion (100-150 words)
- Key takeaways (bulleted)
- Call to action: [What should the reader do next?]

## Statistics to Include

| # | Statistic | Source | Year | Section |
|---|-----------|--------|------|---------|
| 1 | [stat] | [source + URL] | 2025 | H2: Section 1 |
| 2 | [stat] | [source + URL] | 2026 | H2: Section 2 |
| ... | ... | ... | ... | ... |

## Citation Capsule Plan
For each H2, plan a 40-60 word self-contained passage optimized for AI
extraction. Each capsule should include a stat, its source, and a clear
claim that can stand alone when quoted.

| Section | Capsule Focus | Key Stat | Source |
|---------|--------------|----------|--------|
| H2: [Section 1] | [Core claim this section makes] | [stat] | [source] |
| H2: [Section 2] | [Core claim this section makes] | [stat] | [source] |
| H2: [Section 3] | [Core claim this section makes] | [stat] | [source] |
| ... | ... | ... | ... |

## Cover Image

| Option | Details |
|--------|---------|
| Photo cover | [Pixabay/Unsplash/Pexels search terms for wide hero image] |
| Generated SVG | [Text-on-gradient concept with key stat, if data-heavy topic] |
| Dimensions | 1200x630 (OG-compatible) |

## Visual Element Plan

| # | Type | Data | Section |
|---|------|------|---------|
| 1 | [Bar chart] | [Data description] | H2: Section 2 |
| 2 | [Donut chart] | [Data description] | H2: Section 4 |
| 3 | [Image: Pixabay] | [Search terms] | H2: Section 1 |
| 4 | [Image: Pixabay] | [Search terms] | H2: Section 3 |

## Competitive Gaps to Exploit
1. [What competitors miss that we should cover]
2. [Unique angle or original data we can provide]
3. [Format advantage -- charts/visuals competitors lack]

## Internal Link Architecture
- **Link TO** (from this new post to existing pages):
  1. [Page title/URL] -- anchor text: "[descriptive anchor]"
  2. [Page title/URL] -- anchor text: "[descriptive anchor]"
  3. [Page title/URL] -- anchor text: "[descriptive anchor]"
  4. [Page title/URL] -- anchor text: "[descriptive anchor]"
  5. [Page title/URL] -- anchor text: "[descriptive anchor]"
- **Link FROM** (update these existing pages to link to this new post):
  1. [Page title/URL] -- anchor text: "[descriptive anchor]"
  2. [Page title/URL] -- anchor text: "[descriptive anchor]"
  3. [Page title/URL] -- anchor text: "[descriptive anchor]"
  4. [Page title/URL] -- anchor text: "[descriptive anchor]"
  5. [Page title/URL] -- anchor text: "[descriptive anchor]"
- **Pillar connection**: [Which pillar page this belongs to, if applicable]
- **Cluster position**: [Hub / Spoke / Standalone]

## E-E-A-T Signals to Include
- **Experience**: [First-hand insight, case study, or test result]
- **Expertise**: [Author credentials relevant to topic]
- **Authority**: [Industry recognition, citations, partnerships]
- **Trust**: [Transparency, sourced data, no self-promotion]

## Distribution Plan
- **Reddit**: [Specific subreddits (r/sub1, r/sub2), posting approach (value-first
  comment vs. link post), authentic participation strategy, timing]
- **YouTube**: [Video companion concept, estimated length, key visuals from the
  post to reuse, thumbnail idea]
- **LinkedIn**: [Article excerpt angle, target audience segment, best posting
  time for the niche, engagement hook]
- **Email**: [Newsletter excerpt (2-3 sentences), subject line suggestion,
  CTA linking back to the full post]
- **Twitter/X**: [Thread hook (first tweet), 3-5 key tweet ideas built from
  statistics in the post, hashtag suggestions]

Step 6: Save the Brief

Save to the user's project as briefs/[slug]-brief.md or to a location they specify. Confirm the brief is ready for /blog write.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.57%
按下载量换算258

Claude

28.22%
按下载量换算217

Cursor

19.88%
按下载量换算153

Gemini CLI

10.32%
按下载量换算79

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills