Agent Skills
› NeverSight/learn-skills.dev
› article-writing
article-writing
GitHub用于撰写博客、教程等长文，确保内容具鲜明人设与观点。遵循‘先例后释’、用事实说话原则，禁止空洞套话。支持品牌语气匹配，提供技术指南、评论及通讯等不同结构模板，保障文章逻辑严密、可信且高质量。
Trigger Scenarios
用户需要撰写博客文章、操作指南或新闻通讯
需要将笔记或研究资料转化为正式长文
要求保持特定品牌或个人写作风格
Install
npx skills add NeverSight/learn-skills.dev --skill article-writing -g -y
SKILL.md
Frontmatter
{
"name": "article-writing",
"origin": "ECC",
"description": "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."
}
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
- Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
- Explain after the example, not before.
- Keep sentences tight unless the source voice is intentionally expansive.
- Use proof instead of adjectives.
- 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
- Clarify the audience and purpose.
- Build a hard outline with one job per section.
- Start sections with proof, artifact, conflict, or example.
- Expand only where the next sentence earns space.
- 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
Version History
- e0220ca Current 2026-07-05 23:38
