跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

blog-post

Use when the user wants to write a blog post about a feature, product change, PR, git diff, or any technical topic - accepts marketing briefs, PRs, git refs, codebase paths, or freeform descriptions as input

AlemTuzlak · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add AlemTuzlak/skills --skill blog-post

技能说明


name: blog-post description: Use when the user wants to write a blog post about a feature, product change, PR, git diff, or any technical topic - accepts marketing briefs, PRs, git refs, codebase paths, or freeform descriptions as input

Blog Post Writer

Write high-quality blog posts from code changes, marketing briefs, or feature descriptions. Handles SEO, structure, tone matching, and visual content.

Writing rule (non-negotiable): never use em-dashes (— or –). Use a hyphen - instead. Applies to every line of generated copy.

Input Resolution

Resolve the argument (if provided) in this order:

  1. Path to an existing marketing brief file (.md containing "Executive Summary" or "Key Messages") → marketing brief
  2. Matches GitHub URL or #\d+ pattern → PR
  3. Contains ... or .. → git ref range
  4. Resolves to existing file/directory → codebase feature
  5. Otherwise → freeform text

If no argument is provided, ask: "What should I write about? You can provide a marketing brief path, PR URL/number, git ref range (e.g. v1.0...v2.0), file/directory path, or just describe the topic."

If multiple interpretations match, confirm with the user.

Process Flow

digraph blog_post {
    rankdir=TB;
    "Resolve input" [shape=box];
    "Phase 1: Discovery" [shape=box];
    "Phase 2: Research" [shape=box];
    "Phase 3: Configure" [shape=box];
    "Phase 4: Outline" [shape=box];
    "Outline approved?" [shape=diamond];
    "Phase 5: Write" [shape=box];
    "Phase 6: Output" [shape=box];

    "Resolve input" -> "Phase 1: Discovery";
    "Phase 1: Discovery" -> "Phase 2: Research";
    "Phase 2: Research" -> "Phase 3: Configure";
    "Phase 3: Configure" -> "Phase 4: Outline";
    "Phase 4: Outline" -> "Outline approved?";
    "Outline approved?" -> "Phase 4: Outline" [label="no, revise"];
    "Outline approved?" -> "Phase 5: Write" [label="yes"];
    "Phase 5: Write" -> "Phase 6: Output";
}

Do NOT skip phases. Ask questions at a natural pace. Don't overwhelm, but don't artificially slow things down either. If the user answers multiple questions at once, accept their bundled answers and skip ahead.

If the user says "just pick defaults", "you choose", or similar, pick reasonable defaults based on context, state what you chose, and ask for a single confirmation before proceeding.

Never make assumptions without confirming.

Phase 1: Discovery

Step 1 - Analyze the input

Input typeWhat to read
Marketing briefRead the brief - extract problem statement, value prop, audience, key messages, competitive positioning. Still do Step 2 if the brief lacks product context, then proceed to Step 3.
PRDiff, PR description, review comments, commit messages (gh pr view, gh pr diff). For large PRs (20+ files), focus on user-facing changes.
Git refsgit diff and git log between the refs. For large ranges, prioritize commit messages and user-facing changes.
Codebase featureRead the specified files/directories.
Freeform textParse the user's description. If it lacks specifics (no feature name, no value prop, no context), ask the user to provide more detail or point to a specific file/PR. Fall back to open-ended questions only if they can't.

User-facing changes include: new features, UI changes, API changes, performance improvements, bug fixes, and documentation updates. Internal changes include: refactors, test additions, CI changes, and dependency bumps. When uncertain, list what you found and ask the user which are relevant.

Error handling:

  • gh not installed/authenticated → inform user, suggest gh auth login, offer alternative input
  • Invalid PR/ref → tell user, ask to verify
  • File not found → ask for correct path

Step 2 - Read broader product context

Read if they exist: README, docs/, package.json (or equivalent), marketing references.

Goal: understand what the product is, who it's for, what it does.

If nothing found, ask: "I couldn't find product context in the repo. Can you briefly describe the product and who it's for?"

Step 3 - Present understanding

"Here's what I understand:"

  • Feature A - short description
  • Feature B - short description

"Which of these should the blog post cover? Anything to add, remove, or correct?"

Ask as many questions as needed to fully understand the scope. Do NOT proceed until the user confirms.

Step 4 - Flag sensitive items

Scan for: breaking changes, deprecations, security fixes, migration requirements.

If found, flag each and ask how to frame them before proceeding.

Phase 2: Competitive Blog Research

Before configuring the post, search for similar blog posts in the space:

  1. Use WebSearch to find 3-5 existing blog posts covering the same topic, competing products, or similar feature announcements
  2. Analyze what works and what doesn't in those posts - structure, headlines, hooks, SEO keywords, depth
  3. Identify content gaps - what are competitors NOT covering that this post could
  4. Use these findings to inform SEO strategy, headline generation, and content structure

If WebSearch is unavailable, skip this phase and rely on your own knowledge.

Present a brief summary to the user:

"I found some similar posts in the space. Here's what I noticed:"

  • [Key findings about what works]
  • [Content gaps / opportunities]
  • [SEO keyword opportunities]

"I'll use these insights to shape the post."

Phase 3: Configuration

Ask these questions:

Q1 - Audience: "Who is this blog post for?" (developers, end users, technical decision-makers, general audience, other)

Q2 - Tone: Read existing blog posts, README, and docs in the repo to detect the product's voice. Then confirm:

"Based on your existing content, the tone seems [e.g. conversational and developer-friendly]. Should I match that or go a different direction?"

If no existing content to analyze, ask directly what tone the user wants.

阅读完整来源 ↗