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 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
Version History
- e0220ca Current 2026-07-05 23:51
