Article Writing
Write long-form content that sounds like a real person or brand, not generic AI output.
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
- Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
- Explain after the example, not before.
- Prefer short, direct sentences over padded ones.
- Use specific numbers when available and sourced.
- Never invent biographical facts, company metrics, or customer evidence.
Voice Capture Workflow
If the user wants a specific voice, collect one or more of:
- published articles
- newsletters
- X / LinkedIn posts
- docs or memos
- a short style guide
Then extract:
- sentence length and rhythm
- whether the voice is formal, conversational, or sharp
- favored rhetorical devices such as parentheses, lists, fragments, or questions
- tolerance for humor, opinion, and contrarian framing
- formatting habits such as headers, bullets, code blocks, and pull quotes
If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype.
Banned Patterns
Delete and rewrite any of these:
- generic openings like "In today's rapidly evolving landscape"
- filler transitions such as "Moreover" and "Furthermore"
- hype phrases like "game-changer", "cutting-edge", or "revolutionary"
- vague claims without evidence
- biography or credibility claims not backed by provided context
Writing Process
- Clarify the audience and purpose.
- Build a skeletal outline with one purpose per section.
- Start each section with evidence, example, or scene.
- Expand only where the next sentence earns its place.
- Remove anything that sounds templated or self-congratulatory.
Structure Guidance
Technical Guides
- open with what the reader gets
- use code or terminal examples in every major section
- end with concrete takeaways, not a soft summary
Essays / Opinion Pieces
- start with tension, contradiction, or a sharp observation
- keep one argument thread per section
- use examples that earn the opinion
Newsletters
- keep the first screen strong
- mix insight with updates, not diary filler
- use clear section labels and easy skim structure
Quality Gate
Before delivering:
- verify factual claims against provided sources
- remove filler and corporate language
- confirm the voice matches the supplied examples
- ensure every section adds new information
- check formatting for the intended platform
1---2name: article-writing3description: 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.4origin: ECC5metadata:6 source: https://skillmd.com/skills/phoroth/article-writing7---89# Article Writing1011Write long-form content that sounds like a real person or brand, not generic AI output.1213## When to Activate1415- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues16- turning notes, transcripts, or research into polished articles17- matching an existing founder, operator, or brand voice from examples18- tightening structure, pacing, and evidence in already-written long-form copy1920## Core Rules21221. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.232. Explain after the example, not before.243. Prefer short, direct sentences over padded ones.254. Use specific numbers when available and sourced.265. Never invent biographical facts, company metrics, or customer evidence.2728## Voice Capture Workflow2930If the user wants a specific voice, collect one or more of:31- published articles32- newsletters33- X / LinkedIn posts34- docs or memos35- a short style guide3637Then extract:38- sentence length and rhythm39- whether the voice is formal, conversational, or sharp40- favored rhetorical devices such as parentheses, lists, fragments, or questions41- tolerance for humor, opinion, and contrarian framing42- formatting habits such as headers, bullets, code blocks, and pull quotes4344If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype.4546## Banned Patterns4748Delete and rewrite any of these:49- generic openings like "In today's rapidly evolving landscape"50- filler transitions such as "Moreover" and "Furthermore"51- hype phrases like "game-changer", "cutting-edge", or "revolutionary"52- vague claims without evidence53- biography or credibility claims not backed by provided context5455## Writing Process56571. Clarify the audience and purpose.582. Build a skeletal outline with one purpose per section.593. Start each section with evidence, example, or scene.604. Expand only where the next sentence earns its place.615. Remove anything that sounds templated or self-congratulatory.6263## Structure Guidance6465### Technical Guides66- open with what the reader gets67- use code or terminal examples in every major section68- end with concrete takeaways, not a soft summary6970### Essays / Opinion Pieces71- start with tension, contradiction, or a sharp observation72- keep one argument thread per section73- use examples that earn the opinion7475### Newsletters76- keep the first screen strong77- mix insight with updates, not diary filler78- use clear section labels and easy skim structure7980## Quality Gate8182Before delivering:83- verify factual claims against provided sources84- remove filler and corporate language85- confirm the voice matches the supplied examples86- ensure every section adds new information87- check formatting for the intended platform