SkillHub

Skills affaan-m ecc

article-writing

Use it when:
You want a blog post, guide, tutorial, essay, launch post or newsletter longer than a paragraph.
It does:
Outlines with one job per section, opens each section with proof or an example, and deletes banned AI phrases.
You get:
A draft whose claims rest on the sources you gave, in your voice or, by default, a sharp, concrete operator voice.
Needs:
ECC's brand-voice skill only to match a specific voice from examples.

To match a specific voice, it first runs ECC's separate brand-voice skill and reuses its voice profile.

TL;DR

A short long-form writing skill from ECC. Its five rules: lead with the concrete thing (an artifact, number, anecdote or code), explain after the example, keep sentences tight, use proof instead of adjectives, and never invent facts or customer evidence. It bans phrases such as "in today's rapidly evolving landscape" and "game-changer", fake vulnerability arcs, closing questions added only for engagement and generic AI throat-clearing. The process is to clarify the audience and purpose, build an outline with one job per section, start sections with proof, conflict or an example, expand only where a sentence earns its space, and cut anything templated. It gives structures for technical guides, which open with what the reader gets and end with takeaways, for essays, which start from a tension and keep one argument per section, and for newsletters, whose first screen must do real work. A final check confirms claims are backed by sources and the voice matches the examples or the voice profile.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill article-writing

skills.sh pageSource on GitHubAll skills from affaan-m/ecc

Total Downloads
6,200 on skills.sh, Nov 9, 2026
Repo stars
299,776 affaan-m/ecc
First seen
May 19, 2026 on skills.sh
Weekly Downloads
475
+62% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21294
Sep 28203
Oct 5169
Oct 12263
Oct 19463
Oct 26454
Nov 2522
Nov 9475
Category
category:writing

Articles, docs, internal comms, research write-ups and prose that doesn't read as generated.
Type
type:workflow

A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:community

Everyone else. Unverified vendor claims default to community.
Topics
writinganti-slop

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: article-writing
description: 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.
metadata:
  origin: ECC

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