agentsclimarketplace
Sign in

Article writing

Skill mturac/everything-openai-codex/skills/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.From its SKILL.md

Install
npx -y skills add mturac/everything-openai-codex --skill article-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.8 KB, 544 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most marketing audience skills give in 544 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • Start sections with proof or example
  • Cut anything that sounds templated
  • Back factual claims with provided sources
  • Match formatting to the intended medium

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.