blog-writer
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
Blog post creation covering outlines, SEO-optimized headlines, meta descriptions, content structures, and publication-ready drafting. This skill should be used when Cline needs to create blog posts from scratch — from outlining and headline generation through to full draft production with proper structure, SEO elements, and formatting.
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 31 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Create SEO-optimized headlines with multiple approaches:
- Distinctive: line 155
Write following the outline with proper formatting:
- Distinctive: line 282
Insufficient word count: Add examples, expand explanations, include a practical exercise
- Distinctive: line 285
Missing voice: Ask for existing writing samples.
- Distinctive: line 300
Save versions: Keep outline, draft-v1, and final as separate files
- Distinctive: line 301
Match existing voice: If the user has a blog, read existing posts to match their style
- Distinctive: line 307
No external dependencies required.
“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blog Writer
This skill creates structured, publication-ready blog posts from scratch. It handles the full writing workflow: topic development, SEO headline generation, outline creation, meta description writing, section drafting, and final polish. Every output is optimized for readability, engagement, and search visibility.
When to Use This Skill
- Writing a complete blog post from a topic or brief
- Creating blog post outlines with logical structure
- Generating SEO-optimized headlines and title variants
- Writing meta descriptions for search and social sharing
- Drafting long-form content with proper section hierarchy
- Creating listicles, how-to guides, comparisons, and opinion pieces
- Repurposing existing content into blog format
- Adding internal linking suggestions and call-to-action placement
What This Skill Does
- Outline Generation: Creates structured outlines with logical flow and section depth
- Headline Crafting: Produces SEO-optimized, compelling headline variants
- Meta Description Writing: Writes search-optimized summaries under 160 characters
- Full Draft Production: Writes complete posts with proper formatting and structure
- SEO Integration: Incorporates keyword targeting, header hierarchy, and readability optimization
Process
Step 1: Define the Blog Post
Gather requirements before writing:
## Blog Post Brief
- **Topic**: [Main subject]
- **Target audience**: [Who is this for?]
- **Primary keyword**: [Main SEO target]
- **Secondary keywords**: [Related terms to include]
- **Post type**: [How-to / Listicle / Opinion / Comparison / Case Study / News]
- **Target length**: [Word count goal]
- **Tone**: [Professional / Conversational / Technical / Friendly / Authoritative]
- **CTA**: [What should the reader do after?]
- **Competitor references**: [Similar posts to differentiate from]
- **Unique angle**: [What makes this post different?]Step 2: Generate Headline Variants
Create SEO-optimized headlines with multiple approaches:
## Headline Options
### SEO-Focused (keyword-forward)
1. [Primary Keyword]: [Benefit/Promise]
2. How to [Achieve Outcome] with [Primary Keyword]
3. [Number] [Primary Keyword] Strategies for [Audience]
### Engagement-Focused (curiosity/emotion)
4. Why [Common Belief] About [Topic] Is Wrong
5. The [Topic] Mistake That's Costing You [Outcome]
6. What Nobody Tells You About [Primary Keyword]
### Listicle Format
7. [Number] [Primary Keyword] Tips That Actually Work ([Year])
8. [Number] Ways to [Achieve Outcome] with [Primary Keyword]
### Comparison/Contrast
9. [Option A] vs [Option B]: Which Is Better for [Use Case]?
10. [Topic]: [Conventional Approach] vs [Better Approach]
**Selection criteria**:
- Primary keyword within first 60 characters
- Clear value proposition for the reader
- Specific over vague ("7 Strategies" > "Some Strategies")
- Honest — don't overpromiseStep 3: Create the Outline
Structure with proper hierarchy and word count allocation:
# Outline: [Selected Headline]
**Target**: ~1,500 words | **Type**: How-to Guide
## Introduction (~150 words)
- Hook: [Surprising stat / relatable problem / bold claim]
- Problem statement
- What this post covers
- Who should read this
## Section 1: [First Major Point] (~300 words)
### What is [Concept]?
- Definition in plain language
- Why it matters for [audience]
- Common misconception
### How to [First Step]
- Step-by-step instructions
- Example or case study
- Common pitfall to avoid
## Section 2: [Second Major Point] (~300 words)
- Builds on Section 1
- Introduces [next concept]
- Practical application
## Section 3: [Third Major Point] (~300 words)
- Advanced or nuanced aspect
- Data/evidence supporting this point
- Actionable takeaway
## Pro Tips / Best Practices (~200 words)
- 3-5 quick actionable tips
- Bonus advice from experience
## Conclusion (~150 words)
- Summarize key takeaways (2-3 bullet points)
- Reiterate main benefit
- Call to action
## SEO Elements
- **Primary keyword**: [keyword] — used in H1, first paragraph, 2-3 more times
- **Secondary keywords**: [list] — naturally distributed
- **Internal link suggestions**: [related content to link to]
- **Image/visual suggestions**: [what diagrams or images would help]Step 4: Write Meta Description
## Meta Description Options
**Option 1** (Benefit-focused):
Learn [what/why/how] with [approach]. Discover [outcomes] in this [post type] covering [key topics]. [CTA implication].
**Option 2** (Problem-focused):
Struggling with [common problem]? This guide covers [solutions] to help you [achieve outcome]. [CTA implication].
**Selection rules**:
- Under 155 characters for full SERP display
- Include primary keyword near the start
- Include a reason to click (benefit, curiosity, urgency)
- Match the tone of the post
- No clickbait — deliver on the promiseStep 5: Draft the Post
Write following the outline with proper formatting:
# [Headline]
[Meta: meta-description-text]
[Target keyword: primary-keyword]
---
[Introduction — hook, problem, promise, roadmap]
## [Section 1 H2]
[Content with short paragraphs (2-3 sentences max for web readability)]
[Use **bold** for key terms, not excessive emphasis]
> Pull quote for key insight or statistic — breaks up text visually
### [Subsection H3]
[Bullet points for lists — scannable content:]
- Point one with brief explanation
- Point two with brief explanation
- Point three with brief explanation
[Code blocks for technical content:]
```python
# Example code if applicable[Transition to next section — connect the dots]
[Section 2 H2]
[Continue pattern: short paragraphs, varied formatting, visual breaks]
| Column A | Column B | Column C |
| Data | Comparison | Table |
[Section N H2]
[Final substantive section before conclusion]
Key Takeaways
- [Takeaway 1]: [Brief explanation]
- [Takeaway 2]: [Brief explanation]
- [Takeaway 3]: [Brief explanation]
Ready to [Take Action]?
[Call to action — what should the reader do next?]
[Link to relevant resource, product, or next steps]
### Step 6: Polish and Optimize
Review checklist before publishing:
```markdown
## Pre-Publish Checklist
### SEO
- [ ] Primary keyword in H1, first paragraph, and 2-3 additional times
- [ ] Secondary keywords distributed naturally throughout
- [ ] Meta description under 155 characters with primary keyword
- [ ] Header hierarchy correct (H1 → H2 → H3, no skipped levels)
- [ ] Image alt text suggestions provided
- [ ] Internal linking opportunities identified
### Readability
- [ ] Paragraphs are 2-3 sentences for web scanning
- [ ] No walls of text — visual variety (lists, quotes, tables, code)
- [ ] Transitions between sections are smooth
- [ ] Jargon explained or linked
- [ ] Active voice preferred over passive
### Content Quality
- [ ] Opening hook creates curiosity or resonance
- [ ] Each section delivers on the headline's promise
- [ ] Examples and evidence support claims
- [ ] No filler — every paragraph earns its place
- [ ] CTA is clear and relevant
### Technical
- [ ] Word count within 10% of target
- [ ] No broken markdown formatting
- [ ] Links are described (not "click here")
- [ ] Consistent formatting throughoutBlog Post Types
How-To Guide
Structure: Problem → Prerequisites → Steps → Verification → Troubleshooting Tone: Instructional, encouraging Length: 1,500-2,500 words
Listicle
Structure: Intro → Numbered items with consistent depth → Summary Tone: Scannable, varied (mix serious and fun items) Length: 1,000-2,000 words (50-150 words per item)
Opinion / Thought Leadership
Structure: Bold thesis → Supporting arguments → Counter-argument → Conclusion Tone: Confident, thoughtful, slightly provocative Length: 800-1,500 words
Comparison
Structure: Context → Criteria → Side-by-side analysis → Verdict Tone: Objective, fair, decisive Length: 1,500-2,500 words
Case Study
Structure: Challenge → Approach → Results → Lessons learned Tone: Factual, evidence-based, specific Length: 1,000-2,000 words
Error Handling
- Topic too broad: Narrow scope to one specific angle; suggest breaking into series
- Insufficient word count: Add examples, expand explanations, include a practical exercise
- Keyword stuffing detected: Re-write with natural language; keywords should feel organic
- Weak conclusion: End with actionable takeaways, not a generic summary
- Missing voice: Ask for existing writing samples; match tone rather than defaulting to generic
Common Pitfalls
- ❌ Writing for search engines instead of humans — read it aloud; if it sounds robotic, rewrite
- ❌ Burying the lede — the key point must appear in the first 2 paragraphs
- ❌ Overusing subheadings — H2s every 200-300 words is plenty
- ❌ Forgetting the CTA — every blog post should lead somewhere
- ❌ Generic stock advice — be specific with examples, data, and real scenarios
Cline Workflow Notes
- Install location: Copy this skill directory to
.cline/skills/blog-writer/(project-level) or~/.cline/skills/blog-writer/(global) - Always start with a brief: Even a minimal brief produces better results than no brief
- Headlines first: Generate headline options before writing — the headline shapes everything
- Save versions: Keep outline, draft-v1, and final as separate files
- Match existing voice: If the user has a blog, read existing posts to match their style
- SEO awareness: Include keyword and meta elements, but never sacrifice readability for SEO
- Content over format: The writing quality matters more than template perfection
Dependencies
No external dependencies required. This skill uses Cline's native writing capabilities.
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- google/adk-recipes★ 11ksame name
- google/adk-samples★ 11ksame name
- microsoft/vscode-docs★ 6.7ksame name
- cosZone/astro-koharu★ 445same name
- KonghaYao/peri★ 247same name
- eunomia-bpf/eunomia.dev★ 239same name
- getnao/sylph★ 195same name
- travsteward/openwriter★ 36same name
- nimbalyst/skills★ 28same name
- maroffo/claude-forge★ 17same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use aminer-data-search, auto-target-tracker and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dav-niu474Skillaminer-data-search
使用 AMiner 开放平台 API 进行学术数据查询与分析。当用户需要查询学者信息、论文详情、机构数据、期刊内容或专利信息时使用此 skill。 触发场景:提到 AMiner、学术数据查询、查论文/学者/机构/期刊/专利、学术问答搜索、引用分析、科研机构分析、学者画像、论文引用链、期刊投稿分析等。 支持 6 大组合工作流(学者全景分析、论文深度挖掘、机构研究力分析、期刊论文监控、学术智能问答、专利链分析)以及 28 个独立 API 的直接调用。 即使用户只说"帮我查一下 XXX 学者"或"找找关于 XXX 的论文",也应主动使用此 skill。
Also in 4 projects that use this
dav-niu474Skillauto-target-tracker
自动目标进度追踪器。在对话中检测到目标相关图片(笔记、进度、截图、记录)时,自动调用 VLM 识别关键信息并记录到目标日记。适用于学习管理、健身追踪、工作进度、习惯养成、创作记录等所有目标管理场景。
Also in 4 projects that use this
garri333Skillmarketing-mode
23 frameworks de marketing combinados — estrategia, psicología, contenido, SEO, CRO y growth. Usa cuando necesites crear estrategias de marketing, copys de alta conversión o planes de crecimiento.
Also in 4 projects that use this
- +9 more from dav-niu474
In this repository49 other files it gives its agents.
- a-b-testingSkill
- api-devSkill
- article-extractorSkill
- audio-genSkill
- brainstormingSkill
- brand-guidelinesSkill
- canvas-designSkill
- changelog-generatorSkill
- code-refactorerSkill
- competitive-ads-extractorSkill
- content-research-writerSkill
- database-managerSkill
- docker-deploySkill
- docxSkill
- domain-name-brainstormerSkill
- email-campaignsSkill
- finishing-a-development-branchSkill
- game-devSkill
- git-pushingSkill
- git-workflowSkill
- godot-helperSkill
- image-enhancerSkill
- ios-simulator-skillSkill
- langsmith-fetchSkill
- lead-research-assistantSkill
- lean-ctxSkill
- mcp-builderSkill
- meeting-insights-analyzerSkill
- pdfSkill
- playwright-skillSkill
- pptxSkill
- react-nextjs-builderSkill
- review-implementingSkill
- seo-optimizerSkill
- ship-learn-nextSkill
- skill-creatorSkill
- skill-builderSkill
- social-media-managerSkill
- staff-engineer-reviewSkill
- tailored-resume-generatorSkill
- test-driven-developmentSkill
- test-fixingSkill
- twitter-algorithm-optimizerSkill
- using-git-worktreesSkill
- video-framesSkill
- webapp-testingSkill
- xlsxSkill
- youtube-transcriptSkill
- your-skill-nameSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

