Skip to content

bakrsabeeh/article-writing-skill

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Professional Article Writing Skill (v2.0)

The most comprehensive skill framework for writing distinctive, evidence-backed long-form content.

Master the craft of writing blog posts, guides, tutorials, newsletters, case studies, and thought leadership pieces that convert readers into customers, advocates, and collaborators.


What's Inside

This enhanced skill framework provides everything you need to write high-impact articles:

Core Framework

  • 7 Core Writing Rules — The fundamentals that separate good writing from great
  • 5 Content Format Profiles — Blog posts, tutorials, newsletters, case studies, research reports
  • 5 Voice Variations — From sharp operator to storyteller
  • 5 Audience Profiles — Tailor your writing to developers, founders, designers, executives, enterprise

Planning & Research

  • Voice Extraction Process — How to analyze and extract voice from examples
  • Research Methodology — How to back claims with real evidence
  • Writing Process — 6-stage detailed process from clarification to quality gate
  • SEO & Performance Optimization — Headline formulas, keyword strategy, readability, links, CTAs

Quality & Delivery

  • Revision Checklist — 50+ checkpoint quality gate
  • Quality Scoring Rubric — Know when your piece is ready to publish (1-5 scale)
  • Common Pitfalls Table — 10 frequent problems with specific solutions
  • Templates by Format — Copy-paste starting points for every format

Distribution

  • Call-to-Action Framework — Types, placement, best practices
  • Distribution Strategy — Channel-specific promotion for each format
  • Social Media Optimization — Tips for Twitter, LinkedIn, Email, Slack

Quick Start

The Seven Core Rules

  1. Lead with the concrete thing — artifact, example, output, anecdote, number, screenshot, code
  2. Explain after the example — Show first, then explain why it works
  3. Keep sentences tight — Aim for 12-18 words unless intentionally expansive
  4. Use proof instead of adjectives — Replace "incredibly powerful" with "40% faster"
  5. Never invent facts — Back every claim with sources or direct experience
  6. Voice is earned through specificity — Let personality emerge from choices, not announcement
  7. Match audience expectations — Developers want code, founders want strategy, execs want ROI

The Core Mistakes (and Fixes)

Mistake Fix
Buried lead Start with concrete outcome. Cut everything before it.
Too much background Assume reader is intelligent. Explain jargon, not context.
Empty superlatives Replace with metrics: "incredibly powerful" → "30% faster"
Fake vulnerability Skip the self-deprecation. Lead with earned credibility.
No clear CTA Always include one: "Try this", "Get the template", "Book a demo"
Passive voice Search for "is", "was", "been" — rewrite to active.
Vague examples Be specific: name the company, metric, deadline.
Too many ideas Pick one thread. Save the rest for part 2.
Weak headline Use formula: [benefit] + [method] + [context].
Unfinished thought Every section needs closure.

Content Formats (Choose Your Template)

Blog Post / Essay

  • Purpose: Share insight, build audience, establish authority
  • Length: 1,200-2,500 words (5-8 min read)
  • Structure: Hook → Problem → Insight → Why It Matters → Next Steps
  • Opening Formula: "[Observation]. I used to [assumption]. Then [event]. Now [understanding]."
  • Tone: Sharp, unsentimental, useful

Technical Tutorial / How-To

  • Purpose: Teach a specific skill; get reader to working result
  • Length: 1,500-3,000 words (15-45 min to complete)
  • Opening: Show what they'll build (screenshot or demo)
  • Structure: Prerequisites → Steps → Troubleshooting → Extensions
  • Tone: Patient, precise, concrete

Newsletter / Email Issue

  • Purpose: Build habit, deliver value, move toward action
  • Length: 500-1,200 words (3-5 min read)
  • Opening: First screen must deliver value on its own
  • Structure: Hook → One main idea → What to do → CTA
  • Subject Line Formula: "[Hook] + [Specific benefit]" (50 chars)

Case Study

  • Purpose: Prove your approach works; build trust through specificity
  • Length: 2,000-4,000 words (8-12 min read)
  • Structure: Customer → Approach → Results → Lessons → Replication
  • Key: Specific metrics, what didn't work, honest constraints

Research Report / Whitepaper

  • Purpose: Establish authority; provide citable data
  • Length: 3,000-8,000 words (15-25 min read)
  • Structure: Executive Summary → Methodology → Findings → Analysis → Recommendations
  • Key: Clear methodology, primary research, acknowledge limitations

Audience Profiles

Write for your specific audience:

Audience Cares About Hates Format CTA
Developer Working code, time saved Hand-waving, untested claims Code-heavy, interactive "Try it (5 min)"
Founder Strategic insights, competitive edge Consultancy speak Narratives, frameworks "Get playbook"
Designer User insight, craft Trends, dogma Case studies, research "See how we built"
Operations ROI, team velocity Complexity Data, playbooks, templates "Get template"
Enterprise Risk reduction, compliance Unproven ideas Whitepapers, guides "Download guide"

Voice Handling

Default: Sharp Operator Voice

If no examples are given, use this:

  • Concrete, unsentimental, useful
  • Short sentences; minimal adjectives
  • Examples over abstractions
  • What works, not what sounds good

Voice Extraction Process

If you supply examples:

  1. Identify patterns (sentence length, adjective density, example style)
  2. Document the VOICE PROFILE (don't reanalyze later)
  3. Reuse this profile throughout all writing

Voice Variations

  • Technical Expert: Precise, shows trade-offs, demonstrates working
  • Founder/Thought Leader: Personal journey, strong POV, candid
  • Storyteller: Narrative arc, sensory details, emotional truth
  • Educational: Step-by-step, anticipates confusion, encourages questions

SEO Quick Reference

Headline Formula

[Specific result] + [method] + [context]

Examples:

  • "We Ship 40% Faster With Smaller Pull Request Reviews"
  • "Why Unit Economics Matter More Than Growth Rate"
  • "How We Reduced Hiring Time From 6 Weeks to 2"

Keyword Optimization

  • Primary keyword in: Title, first 100 words, at least one H2
  • Aim for 1-2% keyword density (don't stuff)
  • Use variations and synonyms naturally throughout
  • Include long-tail keywords ("how to", "why matters")

Readability

  • Target 10th-grade reading level
  • Short paragraphs (3-5 sentences max)
  • Images, code blocks, or visualizations every 300 words
  • White space and short sentences

Meta Description (150-160 chars)

Lead with benefit + keyword + promise/CTA

"Learn the exact framework we used to ship 40% faster. Includes templates and mistakes to avoid."

Quality Scoring

Before publishing, score your piece (1-5 on each):

  • Clarity: Does reader know what they'll get in first 30 seconds?
  • Evidence: Is every claim backed by data or example?
  • Voice: Does it sound like a real person (not generic AI)?
  • Structure: Each section have one job? Can any be deleted?
  • SEO: Headline + keyword + compelling meta + visuals?
  • CTA: Specific, relevant, clear what happens next?

Scoring:

  • 27-30 = Ready to publish
  • 21-26 = One more revision pass
  • 15-20 = Significant work needed
  • <15 = Start over

Banned Patterns (Delete Immediately)

❌ "In today's rapidly evolving landscape"
❌ "Game-changer", "cutting-edge", "revolutionary"
❌ "As a scrappy founder, I'm not an expert, but..."
❌ "This will blow your mind"
❌ "What's your favorite X? Let me know in comments!"
❌ "I'm incredibly passionate about this"
❌ "I would argue that..."

Replace with: Specific observations and evidence


Writing Process (6 Stages)

  1. Clarify: Audience? Purpose? Success metric? Format?
  2. Outline: One job per section. Proof point per section.
  3. Research: Find sources, gather proof, collect examples
  4. Draft: Write 150-200% of final length without editing
  5. Tighten: Voice check, cut filler, replace adjectives
  6. Quality Gate: 50+ checkpoints before publishing

Distribution Strategy

Blog: Own site → Email → Twitter/LinkedIn (multiple times) → Collaborators → Aggregators

Newsletter: Email → Social → Tease next → Encourage forwards

Tutorial: Own site + docs → Communities (Reddit, Dev.to, HN) → Video → Update 6-12 months

Case Study: Landing pages → LinkedIn → Webinar → Update annually

Report: Email gate → Publications → Blog summary → Social highlights


Key Improvements Over v1.0

Content Format Profiles — Detailed structure, length, tone for 5 major formats
Audience Profiles — 5 specific audience types with preferences and CTAs
Voice Extraction — Process to analyze and document voice from examples
SEO & Performance — Headline formulas, keyword strategy, readability, CTAs
Research Methodology — How to back claims with real evidence
Distribution Strategy — Channel-specific promotion for each format
Quality Scoring Rubric — Objective scoring system (1-5 scale)
Advanced Techniques — Data narratives, contrast reveals, framework contextualization
7 Core Rules (was 5) — Added specificity + voice + audience match
50+ Checkpoints — Comprehensive revision checklist
10 Pitfalls — Common problems with solutions
5 Templates — Copy-paste starting points for each format


Using This Skill

For Writing

  1. Pick your format (blog, tutorial, newsletter, case study, report)
  2. Choose your audience
  3. Follow the relevant template
  4. Write draft (150-200% of final)
  5. Use revision checklist
  6. Score using rubric
  7. Publish when 27+

For Teaching

Share this framework with your team. Use templates and rubric to establish consistent quality standards.

For Your Process

Adopt the 7 core rules, create format templates, use revision checklist as your quality gate, build audience profiles for your readers.


Contributing

Improvements welcome. This framework gets better with real-world usage and feedback.

  • Found a better technique?
  • Discovered a pitfall we missed?
  • Have a better example?
  • Want to add a format or audience profile?

Open an issue or PR.


License

MIT License — Use, modify, share freely with attribution.


Version History

v2.0 (Current) - Enhanced with audience profiles, SEO, distribution, quality scoring, research methodology v1.0 - Original article-writing skill by ECC (5 rules, 3 formats, basic quality gate)


Resources


Good writing is proof + clarity + voice.

Write for someone real. Give them proof. Let them decide.

About

The most comprehensive skill framework for writing distinctive, evidence-backed long-form content. Master the craft of writing blog posts, guides, tutorials, newsletters, case studies, and thought leadership pieces that convert readers into customers, advocates, and collaborators.

Resources

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors