Agent skill

Blog Post Writer

by Microck in Microck/ordinary-claude-skills

Transform brain dumps into polished blog posts in Nick Nisi's voice.

Custom licenceAuto-check passedWriting & Content

Install Blog Post Writer

skills CLI
$ npx skills add Microck/ordinary-claude-skills --skill blog-post-writer -a claude-code

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

GitHub CLI
$ gh skill install Microck/ordinary-claude-skills blog-post-writer --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/Microck/ordinary-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_all/blog-post-writer .claude/skills/blog-post-writer && 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-writer
GitHub stars
403
Used in
1 other repo
Token cost
~1.3k tokens
SKILL.md length
516 words
Files
2
Skills in repo
91
Repo updated
First seen
Licence
Custom licence

At a glance

Transform brain dumps into polished blog posts in Nick Nisi's voice.

  • Works in 6 steps: Receive the Brain Dump → Read Voice and Tone → Check for Story Potential → …
  • The user wants to write a blog post with scattered ideas
  • SKILL.md covers Process, Voice Guidelines, Example Patterns and Bundled Resources, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Blog Post Writer is an agent skill from Microck/ordinary-claude-skills. Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).

It sits in Writing & Content, covering Blog and article writing. The repository describes itself as: An unappealing collection of Claude Skills and resources.

When your agent uses it

  • The user wants to write a blog post with scattered ideas
  • Conclusions that need organization into a cohesive narrative with Nicks conversational
  • Thoughtful tone

Example prompts

  • “/blog-post-writer”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Receive the Brain Dump
  2. Read Voice and Tone
  3. Check for Story Potential
  4. Organize Content
  5. Write in Nick's Voice
  6. Review and Refine

What it can do on your machine

Read from SKILL.md and the folder at commit 1056d29. 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 (its code samples are markdown).

    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 Writer loads about 1.3k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 516 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 516 words (~1,319 tokens).

“Transform unstructured brain dumps into polished blog posts that sound like Nick Nisi.”

— opening of SKILL.md by Microck, Custom licence
name
blog-post-writer

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in skills_all/blog-post-writer of Microck/ordinary-claude-skills.

  • SKILL.md
  • metadata.json

Open the folder on GitHubat commit 1056d29

Used in 1 other repository

We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Microck/ordinary-claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Blog Post Writer 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 Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blog Post Writer this skillMicrock/ordinary-claude-skills4031 repos~1.3kAutomated safety check: PassCustom licence
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k2 repos~2.9kAutomated safety check: PassMIT
Figurevectorize-io/hindsight47k—~1.9kAutomated safety check: PassMIT
SepiaNanako0129/sepia3k—~3.6kAutomated safety check: PassMIT
Blog Post Draftingluongnv89/claude-howto42k—~2.1kAutomated safety check: PassMIT
Notion To Blogwasp-lang/wasp19k—~922Automated safety check: PassMIT

Similar skills

  • Khazix WeChat Article Writer

    KKKKhazix/khazix-skills

    Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.

    21k GitHub starsUsed in 2 repos~2.9k tokens
    Writing & ContentAuto-check passed
  • Figure

    vectorize-io/hindsight

    Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.

    47k GitHub stars~1.9k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3k GitHub stars~3.6k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Post Drafting

    luongnv89/claude-howto

    Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.

    42k GitHub stars~2.1k tokensUpdated 8 days ago
    Writing & ContentAuto-check passed
  • Notion To Blog

    wasp-lang/wasp

    Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.

    19k GitHub stars~922 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Blog Post

    nteract/semiotic

    Author a new entry for the Semiotic blog. An agent skill from nteract/semiotic.

    2.7k GitHub stars~3.4k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

More from Microck/ordinary-claude-skills

All 91 skills in this repo
  • Every Style Editor

    Microck/ordinary-claude-skills

    This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide.

    403 GitHub starsUsed in 3 repos~1.2k tokens
    Auto-check passed
  • Gemini Imagegen

    Microck/ordinary-claude-skills

    Generate and edit images using the Gemini API (Nano Banana Pro).

    403 GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed
  • Andrew Kane Gem Writer

    Microck/ordinary-claude-skills

    Write Ruby gems following Andrew Kane's proven patterns and philosophy.

    403 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Codex

    Microck/ordinary-claude-skills

    Execute Codex CLI for code analysis, refactoring, and automated code changes.

    403 GitHub starsUsed in 2 repos~2.8k tokens
    Auto-check passed
  • Docs Review

    Microck/ordinary-claude-skills

    Review documentation changes for compliance with the Metabase writing style guide.

    403 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check: notes
  • File Todos

    Microck/ordinary-claude-skills

    This skill should be used when managing the file-based todo tracking system in the todos/ directory.

    403 GitHub starsUsed in 2 repos~1.9k tokens
    Auto-check passed

Questions about Blog Post Writer

What does Blog Post Writer do?

Transform brain dumps into polished blog posts in Nick Nisi's voice. Blog Post Writer is an agent skill from Microck/ordinary-claude-skills. Transform brain dumps into polished blog posts in Nick Nisi's voice.

When should I use Blog Post Writer?

Blog Post Writer fits situations like: the user wants to write a blog post with scattered ideas; conclusions that need organization into a cohesive narrative with Nicks conversational; thoughtful tone.

How do I install Blog Post Writer in Claude Code?

Run `npx skills add Microck/ordinary-claude-skills --skill blog-post-writer -a claude-code`. Or copy the skill folder (skills_all/blog-post-writer in Microck/ordinary-claude-skills) into .claude/skills/blog-post-writer in your project. Claude Code loads it when a task matches its description.

How do I install Blog Post Writer in Codex?

Run `npx skills add Microck/ordinary-claude-skills --skill blog-post-writer -a codex`. Or copy the skill folder (skills_all/blog-post-writer in Microck/ordinary-claude-skills) into .agents/skills/blog-post-writer in your project. Codex loads it when a task matches its description.

Can I use Blog Post Writer 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 Microck/ordinary-claude-skills --skill blog-post-writer -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-writer, .gemini/skills/blog-post-writer, .github/skills/blog-post-writer and .opencode/skills/blog-post-writer in your project.

What does Blog Post Writer need to run?

SKILL.md names no scripts, command-line tools or credentials: Blog Post Writer is instructions for the agent only.

Does Blog Post Writer 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 Writer 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 Writer use?

Blog Post Writer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Blog Post Writer use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 Writer?

Skills that share tags, products or a category with Blog Post Writer: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 47k stars), Sepia (Nanako0129/sepia, 3k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blog Post Writer?

Microck (a GitHub user) maintains it in Microck/ordinary-claude-skills, which has 403 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on September 6, 2026.

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