article-writing

Name: article-writing
Author: affaan-m

232kstars35kforks

How to install article-writing?

affaan-m/ecc/article-writing

$npx -y skills add affaan-m/ECC --skill article-writing

Installs into the current project.

Summary

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, stru

Files · 1

View on GitHub

SKILL.md

1	# Article Writing
2
3	Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.
4
5	## When to Activate
6
7	- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
8	- turning notes, transcripts, or research into polished articles
9	- matching an existing founder, operator, or brand voice from examples
10	- tightening structure, pacing, and evidence in already-written long-form copy
11
12	## Core Rules
13
14	1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
15	2. Explain after the example, not before.
16	3. Keep sentences tight unless the source voice is intentionally expansive.
17	4. Use proof instead of adjectives.
18	5. Never invent facts, credibility, or customer evidence.
19
20	## Voice Handling
21
22	If the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.
23	Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
24
25	If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
26
27	## Banned Patterns
28
29	Delete and rewrite any of these:
30	- "In today's rapidly evolving landscape"
31	- "game-changer", "cutting-edge", "revolutionary"
32	- "here's why this matters" as a standalone bridge
33	- fake vulnerability arcs
34	- a closing question added only to juice engagement
35	- biography padding that does not move the argument
36	- generic AI throat-clearing that delays the point
37
38	## Writing Process
39
40	1. Clarify the audience and purpose.
41	2. Build a hard outline with one job per section.
42	3. Start sections with proof, artifact, conflict, or example.
43	4. Expand only where the next sentence earns space.
44	5. Cut anything that sounds templated, overexplained, or self-congratulatory.
45
46	## Structure Guidance
47
48	### Technical Guides
49
50	- open with what the reader gets
51	- use code, commands, screenshots, or concrete output in major sections
52	- end with actionable takeaways, not a soft recap
53
54	### Essays / Opinion
55
56	- start with tension, contradiction, or a specific observation
57	- keep one argument thread per section
58	- make opinions answer to evidence
59
60	### Newsletters
61
62	- keep the first screen doing real work
63	- do not front-load diary filler
64	- use section labels only when they improve scanability
65
66	## Quality Gate
67
68	Before delivering:
69	- factual claims are backed by provided sources
70	- generic AI transitions are gone
71	- the voice matches the supplied examples or the agreed `VOICE PROFILE`
72	- every section adds something new
73	- formatting matches the intended medium

People who liked this also viewed

6 picks

Type

article-writing

232kstars35kforks

View on GitHub

How to install article-writing?

affaan-m/ecc/article-writing

$npx -y skills add affaan-m/ECC --skill article-writing

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Article Writing
2
3	Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.
4
5	## When to Activate
6
7	- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
8	- turning notes, transcripts, or research into polished articles
9	- matching an existing founder, operator, or brand voice from examples
10	- tightening structure, pacing, and evidence in already-written long-form copy
11
12	## Core Rules
13
14	1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
15	2. Explain after the example, not before.
16	3. Keep sentences tight unless the source voice is intentionally expansive.
17	4. Use proof instead of adjectives.
18	5. Never invent facts, credibility, or customer evidence.
19
20	## Voice Handling
21
22	If the user wants a specific voice, run `brand-voice` first and reuse its `VOICE PROFILE`.
23	Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
24
25	If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
26
27	## Banned Patterns
28
29	Delete and rewrite any of these:
30	- "In today's rapidly evolving landscape"
31	- "game-changer", "cutting-edge", "revolutionary"
32	- "here's why this matters" as a standalone bridge
33	- fake vulnerability arcs
34	- a closing question added only to juice engagement
35	- biography padding that does not move the argument
36	- generic AI throat-clearing that delays the point
37
38	## Writing Process
39
40	1. Clarify the audience and purpose.
41	2. Build a hard outline with one job per section.
42	3. Start sections with proof, artifact, conflict, or example.
43	4. Expand only where the next sentence earns space.
44	5. Cut anything that sounds templated, overexplained, or self-congratulatory.
45
46	## Structure Guidance
47
48	### Technical Guides
49
50	- open with what the reader gets
51	- use code, commands, screenshots, or concrete output in major sections
52	- end with actionable takeaways, not a soft recap
53
54	### Essays / Opinion
55
56	- start with tension, contradiction, or a specific observation
57	- keep one argument thread per section
58	- make opinions answer to evidence
59
60	### Newsletters
61
62	- keep the first screen doing real work
63	- do not front-load diary filler
64	- use section labels only when they improve scanability
65
66	## Quality Gate
67
68	Before delivering:
69	- factual claims are backed by provided sources
70	- generic AI transitions are gone
71	- the voice matches the supplied examples or the agreed `VOICE PROFILE`
72	- every section adds something new
73	- formatting matches the intended medium

People who liked this also viewed

6 picks

Type