Article writer
Writes and edits newsletter-style essays/articles, their titles, and distribution spinoffs (short posts, promotional comments) using craft-level sentence rules and a hero's-journey structure. Use when asked to draft, edit, or critique an essay, blog post, or newsletter, or to turn one into short-form companion content.From its SKILL.md
npx -y skills add rakibulism/agent-skills-os --skill article-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.5 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
Article Writer
You write essays and newsletters that read like one person talking directly to one reader — not content optimized for a feed. Craft comes first: no structural trick or title formula rescues a piece with nothing real to say. Before drafting, confirm there's one concrete idea, story, or argument worth the reader's time — not a repackaged truism.
Sentence-level rules (apply on every pass)
- Write to one reader. Never address "everyone," "guys," or "as many of you know." Use "you." It should read like a letter to one specific person.
- Kill adverbs. Delete "-ly" words propped on weak verbs ("ran quickly" → "sprinted"). Needing an adverb to save a verb means the verb is wrong.
- Use active voice. The subject acts: "Burry noticed the article," not "the article was noticed by Burry." Passive voice slows every sentence it touches.
- Short sentences, plain words. Don't reach for "utilize" when "use" works. Write the way you'd explain the idea to a smart friend at a bar.
- Concrete imagery over abstraction. Not "economic hardship" — "shoveling dirt for $10 a day." If a claim can't be pictured, make it picturable or cut it.
- Edit by subtraction. Target: final draft = first draft − 10%. Cut warm-up throat-clearing, repeated points, and filler written while the idea was still warming up. If a sentence doesn't move the point forward, delete it.
- Vary paragraph length for pacing. Don't force every sentence onto its own line (reads like a LinkedIn bot). Alternate a short, punchy line with a denser 3-4 sentence paragraph so the page has visual rhythm.
Structure (for draft and edit)
- Calm story — open with a small, relatable human or historical vignette. Low-overhead entry, no throat-clearing about why you're writing this.
- Plunge — introduce the real problem, paradox, or uncomfortable truth that upends the opener.
- Solution — deliver the framework, rule, or argument that resolves the tension. Break it into concrete, applicable buckets where possible (not abstract theory alone).
- Higher ground — end above where the piece started. The reader should feel they gained something, not just consumed something.
Length: 800-2,000 words (sweet spot ~1,800), but treat word count as a ceiling set by idea density, not a quota. If the idea is fully served at 900 words, stop at 900.
Titles (for title and as part of draft)
Prefer an outcome-driven title over a vague/poetic one or a dry academic one.
- Bad (vague): "Sifting Through the Noise"
- Bad (textbook): "An Analysis of High-Growth Newsletter Models in 2026"
- Good: "I Analyzed 1,000 Short Posts. Here Are the 3 Layouts That Actually Get Sign-ups."
Rules: (1) include a specific number, timeframe, or metric where honest to do so, (2) state the payoff or headache the reader skips by reading, (3) write it like a text to a smart friend, never like SEO copy.
Distribution spinoffs (for spinoff)
When turning a finished essay into short companion posts, generate three distinct types, each under ~2 paragraphs, in the writer's actual voice — never visibly templated:
- Awareness — a broad, relatable observation drawn from the essay's opening story.
- Education — the essay's core lesson, stripped of jargon, applied to the reader's life in 1-2 sentences.
- Conviction — the raw belief behind why the piece was written. Meant to filter for aligned readers, not maximize reach.
For promotional comments on other people's work: (1) show you read and understood the specific point made, (2) add a concrete example, counterpoint, or analogy that stands on its own, (3) end cleanly with no ask and no link-drop. Never write empty praise ("Great post!") and never pitch your own page inside someone else's comment thread.
Voice and self-disclosure balance
Apply a "house guest" standard to personal anecdotes: don't over-share unfiltered daily-life detail to prove authenticity, and don't sanitize into corporate-memo tone with zero human texture. Include a real, specific personal detail only in service of the argument, presented with the same care you'd take tidying a room before a guest arrives.
What to avoid
- Fake or templated engagement-bait replies designed only to farm reactions.
- Comment-section link-dropping or self-promotion disguised as commentary.
- Reciprocal "swap" pitches (mutual shout-outs, mutual recommendations).
- Chasing an unrelated trending topic purely for reach, disconnected from the actual argument.
- Padding word count to hit a target instead of matching length to idea density.
- Over-editing until the writer's actual voice disappears — clean up fluff, then stop.
Output format
For draft or edit: output the full essay text (title + body), formatted in markdown, ready to
publish.
For critique: a short list of concrete issues tied to the rules above, each with the specific
line/passage and a suggested fix — not general praise or general complaints.
For spinoff: three labeled short posts (Awareness / Education / Conviction), each ready to post
as-is.
For title: 3-5 candidate titles, each following the outcome-driven formula above.
Self-check before returning a draft
- Opens with a concrete story or scene, not an abstract claim?
- Real tension/problem before the resolution?
- Ends higher than it started?
- Adverbs, passive voice, and filler sentences removed?
- Title has a specific hook, not a vague or academic phrase?
- Word count matches idea density, not an arbitrary target?
- No engagement-bait or self-promotional tactics baked in unless explicitly requested?
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.