Claude Skill

blog-writer

Produce structured, documented, readable long-form articles - tutorials, opinion pieces, industry analyses. Use for editorial content beyond pure SEO pieces.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_blog-writer-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/blog-writer
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Blog Writer

Overview

Write articles people finish. Structure, evidence, and voice - with sources when facts are claimed.

Article types

Type Skeleton
Tutorial / how-to problem → prerequisites → numbered steps → pitfalls → result
Opinion / essay claim → strongest counterargument → evidence → implications
Analysis question → data/sources → findings → so-what
Listicle (sparingly) promise → items with real substance each → verdict
Case study narrative see case-study-writer

Workflow

  1. Angle first: what does this article say that the 10 existing ones don't?
  2. Research with web_search/web_fetch; collect quotes, numbers, source URLs.
  3. Outline: title, hook, H2 skeleton, conclusion - validate with the user for long pieces.
  4. Draft: hook in 3 sentences, subheads that tell the story alone, examples in every section.
  5. Edit pass: cut intro throat-clearing, verify each fact (fact-checker), run proofreader.
  6. Ship with metadata via seo-content-writer rules if it targets search.

Readability bar

  • Paragraphs ≤ 4 lines; a visual break (list, quote, image note) every ~300 words
  • No section without a concrete example or number
  • Conclusion says what to do next, never "in conclusion, we saw that…"

Rules

  • Sources linked inline; no orphan claims.
  • Write in the user's brand voice; French content uses French typography (espaces insécables, guillemets).
Files (navin)
  • SKILL.md 1.7 KB
    ---
    name: blog-writer
    description: Produce structured, documented, readable long-form articles - tutorials, opinion pieces, industry analyses. Use for editorial content beyond pure SEO pieces.
    metadata: {"navin":{"emoji":"📝","category":"writing"}}
    ---
    
    # Blog Writer
    
    ## Overview
    
    Write articles people finish. Structure, evidence, and voice - with sources when facts are claimed.
    
    ## Article types
    
    | Type | Skeleton |
    |------|----------|
    | Tutorial / how-to | problem → prerequisites → numbered steps → pitfalls → result |
    | Opinion / essay | claim → strongest counterargument → evidence → implications |
    | Analysis | question → data/sources → findings → so-what |
    | Listicle (sparingly) | promise → items with real substance each → verdict |
    | Case study narrative | see `case-study-writer` |
    
    ## Workflow
    
    1. Angle first: what does this article say that the 10 existing ones don't?
    2. Research with `web_search`/`web_fetch`; collect quotes, numbers, source URLs.
    3. Outline: title, hook, H2 skeleton, conclusion - validate with the user for long pieces.
    4. Draft: hook in 3 sentences, subheads that tell the story alone, examples in every section.
    5. Edit pass: cut intro throat-clearing, verify each fact (`fact-checker`), run `proofreader`.
    6. Ship with metadata via `seo-content-writer` rules if it targets search.
    
    ## Readability bar
    
    - Paragraphs ≤ 4 lines; a visual break (list, quote, image note) every ~300 words
    - No section without a concrete example or number
    - Conclusion says what to do next, never "in conclusion, we saw that…"
    
    ## Rules
    
    - Sources linked inline; no orphan claims.
    - Write in the user's brand voice; French content uses French typography (espaces insécables, guillemets).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related