affaan-m/ECC

article-writing

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

70Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/article-writing"
Automated source guideContent productionStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded content guide: article-writing

Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.

npx skills add https://github.com/affaan-m/ECC --skill "skills/article-writing"
Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

361 source words · 10 usable sections

Best fit

  • Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

Content workflow

Read article-writing through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Writing Process

1. Clarify the audience and purpose. 2. Build a hard outline with one job per section. 3. Start sections with proof, artifact, conflict, or example. 4. Expand only where the next sentence earns space. 5. Cut anything that sounds templated, overexplained, or self-congratulatory.

SKILL.md · Writing Process
Clarify the audience and purpose.Build a hard outline with one job per section.Start sections with proof, artifact, conflict, or example.
02

When to Activate

drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues

SKILL.md · When to Activate
drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issuesturning notes, transcripts, or research into polished articlesmatching an existing founder, operator, or brand voice from examples
03

Core Rules

1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code. 2. Explain after the example, not before. 3. Keep sentences tight unless the source voice is intentionally expansive. 4. Use proof instead of adjectives. 5. Never invent facts, cre…

SKILL.md · Core Rules
Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.Explain after the example, not before.Keep sentences tight unless the source voice is intentionally expansive.
04

Voice Handling

If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE. Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.

SKILL.md · Voice Handling
If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE. Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.

Content checklist

Verify each item before delivery

The source section “Writing Process” has been checked.

The source section “When to Activate” has been checked.

The source section “Core Rules” has been checked.

The source section “Voice Handling” has been checked.

Choose a different workflow

When another Skill is the better fit

FAQ

What does the article-writing source document cover?

Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.

How do I install article-writing?

The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/article-writing". Inspect the command and pinned source before running it.

Repository stars
234,327
Repository forks
35,711
Quality
70/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

70/100
Documentation22/30
Specificity11/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min

Article Writing

Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.

When to Activate

  • drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
  • turning notes, transcripts, or research into polished articles
  • matching an existing founder, operator, or brand voice from examples
  • tightening structure, pacing, and evidence in already-written long-form copy

Core Rules

  1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
  2. Explain after the example, not before.
  3. Keep sentences tight unless the source voice is intentionally expansive.
  4. Use proof instead of adjectives.
  5. Never invent facts, credibility, or customer evidence.

Voice Handling

If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE. Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.

If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.

Banned Patterns

Delete and rewrite any of these:

  • "In today's rapidly evolving landscape"
  • "game-changer", "cutting-edge", "revolutionary"
  • "here's why this matters" as a standalone bridge
  • fake vulnerability arcs
  • a closing question added only to juice engagement
  • biography padding that does not move the argument
  • generic AI throat-clearing that delays the point

Writing Process

  1. Clarify the audience and purpose.
  2. Build a hard outline with one job per section.
  3. Start sections with proof, artifact, conflict, or example.
  4. Expand only where the next sentence earns space.
  5. Cut anything that sounds templated, overexplained, or self-congratulatory.

Structure Guidance

Technical Guides

  • open with what the reader gets
  • use code, commands, screenshots, or concrete output in major sections
  • end with actionable takeaways, not a soft recap

Essays / Opinion

  • start with tension, contradiction, or a specific observation
  • keep one argument thread per section
  • make opinions answer to evidence

Newsletters

  • keep the first screen doing real work
  • do not front-load diary filler
  • use section labels only when they improve scanability

Quality Gate

Before delivering:

  • factual claims are backed by provided sources
  • generic AI transitions are gone
  • the voice matches the supplied examples or the agreed VOICE PROFILE
  • every section adds something new
  • formatting matches the intended medium
Source repo
affaan-m/ECC
Skill path
skills/article-writing/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected