菜单
Write a newsletter issue in Anuj's voice — register between LinkedIn-sharp and Medium-measured, 300-600 words, subject line plus preheader plus scannable body, plain-text-readable, no engagement-bait.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hwj123hwj/custom-skills --skill newsletter-write命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Ask which skill or flow fits your situation. A router over the skills in this repo.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
基于 SOC 职业分类
正在显示 SKILL.md
| name | newsletter-write |
| description | Write a newsletter issue in Anuj's voice — register between LinkedIn-sharp and Medium-measured, 300-600 words, subject line plus preheader plus scannable body, plain-text-readable, no engagement-bait. |
Drafting a newsletter issue for Anuj Sadani. Newsletter sits between sharp and measured — direct, scannable, but with room for one real argument rather than a one-liner. Optimized for email clients: plain-text-readable, no required images, scannable in 60 seconds.
Read these files:
shared/voice-rules.mdshared/voice-samples.mdshared/pet-peeves.mdshared/topic-modes.mdshared/platform-styles.mdApply topic-modes.md.
Then apply the newsletter row from shared/platform-styles.md: technical depth 2–3 (at most one short explained snippet), headline aggressiveness 3 (clear-benefit subject, deliverability-safe — not clickbait), density 2–3 (scannable, short sections). Honor the precedence rules in that file — voice-rules.md/pet-peeves.md are absolute, and topic mode can raise (never lower) substance.
Default outline (300-600 words, 2-3 min read):
voice-samples.md.shared/voice-rules.md. Default level is low — newsletters should rarely contain emoji. Override only if the user explicitly says "use medium emoji" / "no emoji" etc.shared/pet-peeves.md. Any hit → rewrite.shared/platform-styles.md (topic-mode overrides may raise depth).Save to file. Derive a kebab-case topic slug. Get today's date in YYYY-MM-DD form. Save subject + preheader + body to:
./drafts/<YYYY-MM-DD>-<topic-slug>/newsletter.md
Format the file as:
# Subject: <subject line>
Preheader: <preheader>
---
<body>
If the file already exists, suffix with -v2, etc. Create directories as needed.
Also print in chat:
─── SUBJECT ───
<≤8 words>
─── PREHEADER ───
<≤120 chars, complements subject>
─── BODY ───
<300-600 word post>
─── META ───
words: <N>
reading time: <N> min
topic mode: <security | architecture-agents | leadership | cost-infra>
emoji level: <none | low | medium | high>
saved to: <path>
User copies to whichever newsletter platform they use (typically pastes into the compose window). Do not auto-send.