Article writing

Skill bg-szy/TOP-SKILLS/skills/awesome-skills/article-writing

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-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.
4 stars4 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.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.1 KB, 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

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