Agent skill

Blog Post Writing

by seb1n in seb1n/awesome-ai-agent-skills

Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action.

MITAuto-check passedWriting & Content

Install Blog Post Writing

skills CLI
$ npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install seb1n/awesome-ai-agent-skills blog-post-writing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/writing-and-content/blog-post-writing .claude/skills/blog-post-writing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
blog-post-writing
GitHub stars
206
Token cost
~2.5k tokens
SKILL.md length
1,408 words
Files
1
Skills in repo
101
Repo updated
First seen
Licence
MIT

At a glance

Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action.

  • Works in 6 steps: Research the Topic and Keywords → Choose the Content Format → Build the Outline → …
  • The user requests blog post writing
  • SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Blog Post Writing is an agent skill from seb1n/awesome-ai-agent-skills. Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action. Use when the user requests blog post writing or provides relevant inputs for this workflow.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Blog and article writing and Technical writing. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.

When your agent uses it

  • The user requests blog post writing
  • Provides relevant inputs for this workflow

Example prompts

  • “/blog-post-writing”

Requirements

  • Python 3
  • Docker

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Research the Topic and Keywords
  2. Choose the Content Format
  3. Build the Outline
  4. Write the Draft
  5. Optimize for SEO
  6. Review and Polish

What it can do on your machine

Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Blog Post Writing loads about 2.5k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 1,408 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 1,408 words, ~2,474 tokens.

Download SKILL.mdSave it as .claude/skills/blog-post-writing/SKILL.md (or your agent's skills folder).
name
blog-post-writing
description
Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action. Use when the user requests blog post writing or provides relevant inputs for this workflow.
license
MIT
metadata.author
awesome-ai-agent-skills
metadata.version
1.0.0

Blog Post Writing

This skill enables an AI agent to write well-structured, engaging, and SEO-optimized blog posts across multiple content types — how-to guides, listicles, opinion pieces, case studies, and thought leadership articles. The agent handles the full lifecycle from topic research and outlining through drafting, SEO optimization, and final review, producing publish-ready content tailored to the target audience and brand voice.

Workflow

  1. Research the Topic and Keywords Investigate the topic to understand its scope, current discourse, and search intent. Identify a primary keyword and 3-5 secondary keywords to target. Analyze the top-ranking content for the primary keyword to understand what angle, depth, and format performs well. Determine whether the search intent is informational ("how to set up CI/CD"), navigational ("GitHub Actions docs"), or transactional ("best CI/CD tools 2025").

  2. Choose the Content Format Select the blog post format that best matches the topic and search intent. Use a how-to guide for process-oriented queries. Use a listicle for comparison or round-up queries. Use an opinion piece for thought leadership and brand positioning. Use a case study for showcasing results and building credibility. The format determines the structural template for the outline.

  3. Build the Outline Create a detailed outline with the title (including the primary keyword), a hook for the introduction, H2 and H3 subheadings for the body, and a conclusion with a call-to-action. Ensure headings are descriptive and incorporate secondary keywords naturally. Plan where to place supporting elements — code blocks, images, blockquotes, statistics, and internal/external links.

  4. Write the Draft Expand the outline into full prose. Open with a hook that creates curiosity, states a surprising fact, or directly addresses the reader's pain point. Follow with a clear thesis sentence that tells the reader what they will gain from the post. Write body sections in a logical progression, using transitions between sections. Close with a summary of key takeaways and a specific CTA — subscribe, download, try the product, or read a related post.

  5. Optimize for SEO Place the primary keyword in the title, first paragraph, at least one H2, and the meta description. Use secondary keywords in subheadings and body text where they fit naturally — never force them. Write a meta description (150-160 characters) that summarizes the post and includes the primary keyword. Add alt text descriptions for any images. Ensure the URL slug is short and keyword-rich.

  6. Review and Polish Proofread for grammar, spelling, and punctuation. Verify all statistics and claims have credible sources. Check that all links work and point to the correct destinations. Read the post aloud (or simulate doing so) to catch awkward phrasing. Ensure the post meets the target word count and that no section feels thin or padded.

Usage

Provide the agent with:

  • Topic — the subject or working title for the blog post
  • Target keyword — the primary SEO keyword (optional; agent can research)
  • Content format — how-to, listicle, opinion, case study, or let the agent recommend
  • Audience — who will read this (developers, marketers, executives, general public)
  • Tone — professional, casual, conversational, authoritative, witty
  • Word count — target length (e.g., 800, 1500, 2500 words)
  • CTA — what action readers should take after reading

Example prompt: "Write a 1,500-word how-to blog post about setting up a CI/CD pipeline with GitHub Actions. Target keyword: 'GitHub Actions CI/CD tutorial.' Audience: junior developers. Tone: friendly and encouraging."

Examples

Example 1: Complete Blog Post Outline with Filled-In Sections

Input: "Write an outline for a listicle: '7 VS Code Extensions Every Python Developer Needs in 2025.' Audience: intermediate Python developers. Fill in the intro and one list item as examples."

Output:

Title: 7 VS Code Extensions Every Python Developer Needs in 2025

Meta description: Boost your Python workflow with these 7 essential VS Code extensions for linting, testing, debugging, and more. Updated for 2025.

Target keyword: VS Code extensions Python


Introduction (filled in):

Visual Studio Code became the most popular code editor among Python developers for good reason — it is fast, free, and infinitely customizable. But a stock VS Code install only scratches the surface. The right extensions can turn it into a full-featured Python IDE with intelligent autocomplete, real-time linting, one-click debugging, and seamless virtual environment management. Here are seven extensions that will save you real time every single day in 2025.

1. Pylance — Supercharged IntelliSense (filled in):

Pylance replaces the default Python language server with a blazing-fast type checker and autocomplete engine built on Pyright. It catches type errors before you run your code, surfaces inline documentation as you type, and handles complex type annotations that the default extension misses entirely. If you write any amount of typed Python — and you should — Pylance is non-negotiable. Install it once and you will wonder how you ever coded without it.

2. Ruff — Lightning-Fast Linting and Formatting [to be filled]

3. Python Test Explorer — Visual Test Runner [to be filled]

4. GitLens — Git History in Your Editor [to be filled]

5. Docker — Container Management [to be filled]

6. Jupyter — Interactive Notebooks Inside VS Code [to be filled]

7. autoDocstring — One-Click Docstrings [to be filled]

Conclusion: Recap the extensions, emphasize that a well-configured editor is a productivity multiplier, and CTA: "Share your favorite Python extension in the comments."

Show full SKILL.md (554 more words)Show less
Example 2: Writing an Intro Paragraph with a Hook

Input: "Write an intro paragraph for a blog post titled 'Why Your Startup Should Adopt Infrastructure as Code on Day One.' Audience: non-technical startup founders. Hook style: surprising statistic."

Output:

Sixty-eight percent of startups that experience a major infrastructure outage in their first year never fully recover the lost customers. That is not a scare tactic — it is a finding from a 2024 Datadog reliability survey. The irony is that most of these outages trace back to manual server configuration: someone fat-fingered a setting, forgot to open a port, or could not reproduce the production environment when it mattered most. Infrastructure as Code (IaC) eliminates this entire category of risk by treating your servers, networks, and deployments as version-controlled code — code that can be reviewed, tested, and rolled back just like the software it runs. You do not need a dedicated DevOps team to get started, and the earlier you adopt it, the less technical debt you accumulate. In this post, we will break down what IaC actually is, why it matters even at the five-person stage, and how to set it up in a single afternoon.

Best Practices

  • Start with the hook, not the backstory. Readers decide in the first two sentences whether to keep reading. Open with a surprising fact, a provocative question, or a direct statement of the reader's problem. Save the context for the second paragraph.
  • Use descriptive, keyword-rich headings. "Step 3: Configure the Database Connection" is better than "Step 3: Configuration." Headings should be useful on their own when someone skims.
  • Break up long sections. No paragraph should exceed 4-5 sentences in a blog post. Use subheadings, bullet points, code blocks, and pull quotes to create visual rhythm and let readers scan.
  • Link internally and externally. Internal links keep readers on your site and improve SEO. External links to credible sources build trust. Aim for 2-3 internal links and 1-2 external links per 1,000 words.
  • End with a clear CTA. Every blog post should ask the reader to do something: subscribe, try the product, leave a comment, read the next post. A post without a CTA is a missed opportunity.
  • Write for the featured snippet. Structure one section as a concise, direct answer to the primary keyword query. Use a definition paragraph, a numbered list, or a table that Google can pull into a featured snippet.

Edge Cases

  • Topics with no search volume: For thought leadership or opinion pieces targeting niche audiences, SEO optimization is secondary to originality and depth. Focus on unique insights rather than keyword density.
  • Highly competitive keywords: When the top results are all from high-authority domains, target a long-tail variant of the keyword (e.g., "GitHub Actions CI/CD tutorial for monorepos" instead of "CI/CD tutorial") to find a rankable niche.
  • Time-sensitive content: Posts referencing specific tool versions, pricing, or events should include a "Last updated" date and a note that details may have changed. Plan for periodic content refreshes.
  • Multi-author blogs: When writing for a blog with an established voice, review 2-3 recent published posts to match the existing tone, sentence style, and formatting conventions.
  • Very long posts (3,000+ words): Include a table of contents with anchor links at the top. Consider whether the post should be split into a series for better readability and sustained engagement.

© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in writing-and-content/blog-post-writing of seb1n/awesome-ai-agent-skills.

Open the folder on GitHubat commit 75865a5

Compare with similar skills

Blog Post Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Blog Post Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blog Post Writing this skillseb1n/awesome-ai-agent-skills206—~2.5kAutomated safety check: PassMIT
Rnd Technical Writerchendongqi/OPB-Skills126—~2.5kAutomated safety check: PassNone
Dynamo Content DesignerDynamoDS/Dynamo2k—~1.6kAutomated safety check: PassApache-2.0
Voicejvm-skills/jvm-skills139—~592Automated safety check: PassApache-2.0
Domodomo Release Documentationdarknecrocities/DomoDomo---All-in-one-Tool239—~17kAutomated safety check: PassNone
Reading Levelthedaviddias/Front-End-Checklist74k—~613Automated safety check: PassMIT

Similar skills

  • Rnd Technical Writer

    chendongqi/OPB-Skills

    Technical article writing assistant. An agent skill from chendongqi/OPB-Skills.

    126 GitHub stars~2.5k tokensUpdated 8 mo ago
    Writing & ContentAuto-check passed
  • Technical writing specialist for Dynamo product documentation, blog posts, tutorials, and educational content.

    2k GitHub stars~1.6k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Voice

    jvm-skills/jvm-skills

    Make prose sound like Thomas, not like a generic technical writer.

    139 GitHub stars~592 tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Domodomo Release Documentation

    darknecrocities/DomoDomo---All-in-one-Tool

    Maintain DomoDomo product documentation, technical tool records, About metrics, blog posts, SEO metadata, sitemap generation, release communication, and contributor guidance.

    239 GitHub stars~17k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Reading Level

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing content pages for user experience and SEO.

    74k GitHub stars~613 tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • How To Tutorial Writer

    Affitor/affiliate-skills

    Write how-to guides and tutorials that naturally integrate affiliate product recommendations.

    701 GitHub stars~3.6k tokensUpdated 26 days ago
    Writing & ContentAuto-check passed

More from seb1n/awesome-ai-agent-skills

All 101 skills in this repo
  • Agent Red Teaming

    seb1n/awesome-ai-agent-skills

    Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.

    206 GitHub stars~2.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Eu AI Act Readiness

    seb1n/awesome-ai-agent-skills

    Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…

    206 GitHub stars~3.3k tokensUpdated 2 mo ago
    Auto-check passed
  • Human In The Loop

    seb1n/awesome-ai-agent-skills

    Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.

    206 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • MCP Server Building

    seb1n/awesome-ai-agent-skills

    Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.

    206 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • PDF Processing

    seb1n/awesome-ai-agent-skills

    Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.

    206 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed
  • Skill Supply Chain Audit

    seb1n/awesome-ai-agent-skills

    Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.

    206 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Blog Post Writing

What does Blog Post Writing do?

Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action. Blog Post Writing is an agent skill from seb1n/awesome-ai-agent-skills. Write high-quality, SEO-optimized blog posts in multiple formats including how-to guides, listicles, opinion pieces, and case studies, with structured outlines, hooks, and calls-to-action.

When should I use Blog Post Writing?

Blog Post Writing fits situations like: the user requests blog post writing; provides relevant inputs for this workflow.

How do I install Blog Post Writing in Claude Code?

Run `npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a claude-code`. Or copy the skill folder (writing-and-content/blog-post-writing in seb1n/awesome-ai-agent-skills) into .claude/skills/blog-post-writing in your project. Claude Code loads it when a task matches its description.

How do I install Blog Post Writing in Codex?

Run `npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a codex`. Or copy the skill folder (writing-and-content/blog-post-writing in seb1n/awesome-ai-agent-skills) into .agents/skills/blog-post-writing in your project. Codex loads it when a task matches its description.

Can I use Blog Post Writing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill blog-post-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-post-writing, .gemini/skills/blog-post-writing, .github/skills/blog-post-writing and .opencode/skills/blog-post-writing in your project.

What does Blog Post Writing need to run?

SKILL.md names no scripts, command-line tools or credentials: Blog Post Writing is instructions for the agent only. Our summary lists: Python 3; Docker.

Does Blog Post Writing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Blog Post Writing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Blog Post Writing use?

Blog Post Writing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blog Post Writing use?

About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Blog Post Writing?

Skills that share tags, products or a category with Blog Post Writing: Rnd Technical Writer (chendongqi/OPB-Skills, 126 stars), Dynamo Content Designer (DynamoDS/Dynamo, 2k stars), Voice (jvm-skills/jvm-skills, 139 stars) and Domodomo Release Documentation (darknecrocities/DomoDomo---All-in-one-Tool, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blog Post Writing?

seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.

Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.