agentsclimarketplace
Sign in

Article writing

Skill khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/content-social/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 khanhhuyenngo985-sys/character-scene-design-skills --skill article-writing

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 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

3.1 KB, 583 tokens by cl100k_base, as published. Nobody here has run it

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

  1. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
  2. Explain after the example, not before.
  3. Prefer short, direct sentences over padded ones.
  4. Use specific numbers when available and sourced.
  5. 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

  1. Clarify the audience and purpose.
  2. Build a skeletal outline with one purpose per section.
  3. Start each section with evidence, example, or scene.
  4. Expand only where the next sentence earns its place.
  5. 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

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 583 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

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.