跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

newsletter-technical

Write insight-driven technical newsletters: tutorials, analysis, industry breakdowns, how-tos, and data-led explainers. Use when the newsletter's value is the information rather than the narrative. Enforces the EW anti-AI rules, specificity standards, and the writer's voice profile.

Deupaxx · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Deupaxx/EveryDay-Writer --skill newsletter-technical

技能说明


name: newsletter-technical description: | Write insight-driven technical newsletters: tutorials, analysis, industry breakdowns, how-tos, and data-led explainers. Use when the newsletter's value is the information rather than the narrative. Enforces the EW anti-AI rules, specificity standards, and the writer's voice profile. license: MIT metadata: version: "0.3.0"

EW Skill — Technical Newsletter

Dependency chain. Read these in order before writing anything:

  1. core/anti-ai-rules.md (read fully; Section 0 sets the standard, 0.1 sets precedence, 0.2 forbids fabrication, 9 and 10 stop over-correction)
  2. core/ai_slop_commandments.md (mechanism reference and diagnostic checklist)
  3. core/voice-profile.md (this writer's voice fingerprint; if Completed: No, stop and run onboarding)
  4. Any .md files the user has dropped in references/

This chain applies on direct invocation (/ew:newsletter-technical) exactly as it does on dispatch through /ew. Direct invocation skips routing, not constraints.


WHAT THIS SKILL IS FOR

Insight-driven newsletters. Industry analysis, tutorials, how-tos, tool breakdowns, and data-led explainers. The technical newsletter's job is to make the reader measurably smarter — fast. No fluff. No filler. No padding a thin insight to hit a word count.

The A-Player standard applies here too. Clarity is not an absence of depth — it's the hardest discipline in writing. The goal is to make a complex thing simple without making it wrong.


THE STRUCTURAL CONTRACT

Technical newsletters have a different contract from creative ones. The reader is not here for a journey — they're here to extract value efficiently. Every structural decision must serve that extraction.

The 4-part technical structure:

1. The Problem (Why This Matters) State the specific problem, gap, or question this issue addresses. Not "AI is changing things" — "Most teams are using GPT for copywriting but missing the three use cases with 10x better ROI." Specificity earns attention. The reader must know within 2 sentences whether this issue is for them.

2. The Key Insight (What You Found) The single most important thing this issue delivers. State it early — within the first third. Technical readers are busy. If they have to hunt for the point, they'll stop looking. This is not a tease; it's the thesis. Everything else is support.

3. The Evidence and Mechanics (How It Works) Walk through the specifics. Data, examples, step-by-step logic, code, comparisons. This is where depth lives. Each point must connect to the key insight — if it doesn't, it doesn't belong here. No tangents dressed as depth.

4. The Action (What To Do With It) What specifically should the reader do next? Not "consider trying this" — the exact action, tool, query, decision, or change. If there's no action, state why not and what to watch instead. Never end on a passive observation.


CLARITY RULES

Specificity is proof. Every claim must be grounded in a specific fact, number, example, or source. "This framework is faster" means nothing. "This framework cuts cold-start time from 8 seconds to 340ms" means something. If you can't make it specific, you haven't done enough research to write the piece yet.

One concept at a time. Each section covers one thing completely before moving to the next. If you're explaining how a system works while simultaneously arguing why it matters, you're doing two things at once and doing both worse. Separate them.

Name the expert. Link the study. "Experts suggest" is not a source. "According to Ethan Mollick's research on AI adoption in knowledge work" is a source. If you can't name it, you don't have it — you have an impression of something you half-remember. Check before you publish.

Active constructions only. Passive voice in technical writing hides the mechanism. "The data is processed" by what? How? "The model processes each token sequentially against the full context window" is the sentence.


STRUCTURE AND SCANNABILITY

Technical newsletter readers scan before they read. Structure must support scanning without gutting depth.

Headers are signposts, not titles. A header like "Why This Matters" is useless. "Why Teams Underestimate Context Window Size" is a signpost. If the reader can scan your headers and understand the full argument, your structure is working. If the headers could belong to any newsletter on the topic, rewrite them.

Lead with the finding, not the methodology. ❌ "To understand why this works, we first need to look at how X operates under Y conditions, which was first described by..." ✅ "The reason X outperforms Y in low-latency scenarios comes down to how it handles memory allocation. Here's the mechanism:"

Lists only for genuinely parallel items. A list of 7 things that aren't truly parallel is not a list — it's a paragraph avoiding its own logic. Lists are for steps, options, or items where order and parallelism are real. If your bullets keep needing sub-explanations, collapse them into prose.

Code and data get their own block. Never bury a command, query, or formula in running prose. If someone needs to use it, they need to be able to copy it cleanly.


THE INSIGHT STANDARD

The difference between a good technical newsletter and a great one is whether the writer had an insight or just had information. Information is cheap — the reader can find it. Insight is the writer's interpretation, synthesis, or prediction layered on top.

Ask yourself before writing:

  • What does this data actually mean for how someone does their job?
  • What would a smart person get wrong about this topic, and why?
  • What's the non-obvious implication of this development?
  • What does this tell us about where things are going in 6–18 months?

If you can't answer at least one of those, you have a summary, not a newsletter.

The "so what" test: After every major claim, ask: "so what?"

阅读完整来源 ↗