Token导航 LogoToken导航TokenDH.com
待分类external-servicegithub未标认证来源可访问许可证需确认审计提醒

blog-title-generator博客标题生成器

Agent Skill

blog-title-generator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

216

周安装

9

GitHub Stars

公开资料未说明

下载量

72
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/rankearly/rankearly-skills --skill blog-title-generator

简介

blog-title-generator 用于生成 10 个博客标题变体及其标签,适合在 Codex、Claude、Cursor、Gemini CLI 中需要创意标题构思时使用。

  • 每个标题附带 H1 与五维评分解释,强调转化潜力与 SEO 友好度。
  • 使用时必须基于完整博客草稿或明确主题,不接受孤立关键词输入。
  • 安装前建议确认是否依赖外部评分模型及本地化适配能力。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Blog Title Generator

Generate 10 blog title variations, each with a title tag and H1, scored across 5 dimensions with a short explanation of why it works.

Shared Input Handling

Assume the user has a blog draft, blog file, or at least a blog idea. Do not generate titles from a bare keyword alone.

  • If the user provides a blog file such as abc.md, read it and use it as the primary context
  • If the user provides a blog draft, outline, idea, or blog URL, use that as the content context
  • If the user provides only a keyword or short query, do not continue yet; ask what blog they plan to write so you have the actual post context

Only continue into a mode after blog context is available.

Phase 0: Choose Mode

Ask the user (AskUserQuestion): "Want SERP-grounded titles first? That requires authenticating RankEarly MCP and may consume RankEarly credits. Or I can generate quick titles right away without analyzing SERP."

  • If the user wants SERP analysis -> read references/serp-mode.md and follow it, then return here for Phase 1
  • If the user wants quick titles -> read references/quick-mode.md and follow it, then return here for Phase 1

Phase 1: Score, Annotate, and Present

After generating 10 title variations (from either mode), apply the following to each title.

Dual output per variation

For each of the 10 variations, produce:

  • Title Tag — CTR-optimized for SERP display. Usually aim for 50-65 characters, but go longer when clarity wins. Front-load the primary phrase when possible.
  • H1 — Reader-optimized for on-page experience. No character cap. Can be more conversational, descriptive, or provocative.

In SERP mode, optimize each title around the confirmed keyword and the blog context. In quick mode, optimize around the user's blog context.

Score each title

Evaluate each title tag across 5 dimensions using qualitative labels (not numeric scores — labels are immediately actionable):

DimensionWhat to evaluateLabels
Primary Phrase PlacementIs the chosen keyword for that title (SERP mode) or main topic phrase (quick mode) in the first 3 words? First half? Second half?Front-loaded / Mid-placed / Buried
Character LengthCharacter count relative to the usual 50-65 char target rangeStrong (50-65) / Acceptable (40-49 or 66-75) / Long (76+)
Power WordsProven engagement words: definitive, proven, free, steal, easy, fast, etc.Strong (2+) / Present (1) / None
SpecificityNumbers, percentages, timeframes, platform names, audience qualifiersHigh / Moderate / Low
Emotional SentimentWhat emotion does the title trigger?Positive / Negative / Neutral — plus the specific emotion (curiosity, fear, aspiration, urgency)

Also show:

  • Exact character count for the title tag
  • Note when the title tag is longer than 65 characters

Annotate each title

Add a 1-2 sentence annotation explaining the copywriting technique and why it works. Be specific about the effect; avoid generic comments like "uses a number and a power word."

Per-title output format

### Title [N]: [Format Type]

**Title Tag** (XX chars): [title tag version]
**H1**: [H1 version]

**Scores:**
- Primary Phrase Placement: [label]
- Character Length: [label] — XX chars
- Power Words: [label] — [list the power words]
- Specificity: [label] — [what elements]
- Sentiment: [label] — [specific emotion]

**Why this works:** [1-2 sentence annotation]

Recommendations

Close with 3-5 sentences highlighting:

  • Which 2-3 titles are strongest and why
  • Any trade-offs the user should consider

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.65%
按下载量换算24

Claude

27.75%
按下载量换算20

Cursor

19.54%
按下载量换算14

Gemini CLI

9.11%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

external-service

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

安装前确认

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

来源信息

继续浏览同类 Skills