blog-writing
Source of truth: the user's draft
The draft IS the content. Your job is to clean up grammar, tighten prose, and fix awkward phrasing — not to reinterpret, restructure, or "improve" the ideas.
Process
- Read the draft carefully. Understand what each paragraph is saying before touching anything.
- Identify the structure the author chose. Keep it.
- Edit for clarity and grammar only. Fix awkward sentences, but keep the original voice and word choices when they work.
- Flag anything genuinely unclear and ask the author before rewriting it yourself.
Tone
- Like talking to someone over coffee. Natural, not polished.
- Neutral. No hype, no drama, no exaggeration.
- The author's personality and opinions stay. Your job is to make them clearer, not louder or quieter.
Hard rules
- Do not add dramatic qualifiers. If the draft says "copy-pasted code," don't change it to "copy-pasted code in the clumsiest way possible." The draft is already honest — amplifying it makes it sound fake.
- Do not condense the author's points. If they listed four access points, keep all four. If they explained a reasoning chain in three sentences, don't collapse it to one. Specificity and detail are not filler.
- Do not rename or reframe coined terms and frameworks. "Skills-as-a-Software" is a deliberate term — don't change it to "Skills are the new SaaS."
- Do not strip personality. Phrases like "ancient times," parenthetical asides, and informal transitions are intentional.
- Do not abbreviate what the author spelled out. "IP" → keep as "intellectual property" if the author wrote it that way.
- Do not add conclusions or sections the author didn't write. No "Where this is going" or "Final thoughts" if the draft doesn't have them.
- Full sentences for transitions. No fragments like "One model that works:" — write it as a complete thought.
- Address the reader naturally. "If you're a traditional SaaS" is weird. "What does this mean for SaaS companies?" is better.
Quality check
Before delivering, compare every section against the original draft and verify:
- No ideas were dropped or diluted
- No exaggeration was added
- The structure matches the author's intent
- The voice still sounds like the same person wrote it
More from rankearly/rankearly-skills
blog-creator
Umbrella skill for ANY blog-related task — research, outline, write, audit, humanize, illustrate. Use when the user mentions blog posts, outlines, drafts, blog images, or wants to audit/humanize/rewrite blog content.
14blog-title-generator
Generate SEO blog titles, title tags, and H1 variations for an SEO blog. Use when the user wants blog title ideas, headline options, title tag suggestions, H1 variants, or SEO/CTR title optimization for a planned or drafted blog post.
12blog-image
Generate a Nanobanana Pro prompt for blog images - either a scroll-stopping cover or an explanatory in-post illustration. Use when the user asks for a "blog cover", "blog image", "post thumbnail", "illustration for my blog", "header image", or wants to create a visual for a blog post or article section.
11seo-memory
Maintain a project knowledge file for SEO content creation. Use when the user shares critical context about their project — product renames, new/removed features, service changes, subproduct launches, pricing updates, audience shifts, or any factual change that SEO content should reflect. Also triggers on "update seo memory", "remember this for content", "initialize seo memory from domain", or when the user corrects a factual detail about their product/service. Even small updates matter — stale project facts in published content erode trust.
10topic-research
Expand topics into keywords or cluster a keyword library into topics and keyword clusters using RankEarly. Use when the user asks for keyword expansion, topic clustering, content clusters, topic maps, keyword research, or content planning tied to a keyword library.
10serp-gap-analysis
Analyze a live Google SERP for keyword winnability and competitor gaps. Use when the user asks for SERP analysis, real-result keyword difficulty, SEO competitor analysis, content gap analysis, or a brief or content plan for a specific keyword or query.
10