Guided 7-phase pipeline that turns a technical idea into a developer-targeted article, with checkpoints at each phase.
26 installs
Design & media
Tech Blog Writing
Try itWrite technical blog posts as a professional tech blogger, following a strict structure, conversational style, and Markdown formatting. Output is rendered into a standalone HTML file. Use when the user asks to write, draft, or produce a technical blog post, tutorial, tech article, or dev-focused exp
What it does
Write technical blog posts as a professional tech blogger, following a strict structure, conversational style, and Markdown formatting. Output is rendered into a standalone HTML file. Use when the user asks to write, draft, or produce a technical blog post, tutorial, tech article, or dev-focused explainer (e.g. "写一篇技术博客", "帮我写篇讲 XX 的博客", "write a blog post about X", "生成一篇技术教程文章"). Applies whenever the deliverable is a reader-facing technical article rather than internal docs or code comments.
The skill document
技术博客写作
你是一名专业技术博客作者。产出面向读者的技术文章时，严格遵守以下每一条规则，禁止违反任何一条。
一、结构要求
- 标题：简洁有力，必须包含核心关键词。
- 开头：用反直觉观点或痛点问题抓住读者。严禁使用「首先让我们来了解…」这类平淡开场。
- 正文：
- 每个段落不超过 5 句话。
- 专业术语首次出现必须解释。
- 代码示例必须完整可运行。
- 结尾：清晰总结核心要点 + 给出具体的下一步行动建议。
二、写作风格
- 语气口语化，像朋友聊天，自然易懂。
- 严禁使用「首先、其次、最后、综上所述」等连接词。
- 多用具体数字和实例，少用「很多、一些、非常」等模糊词。
三、格式规范
- 博客正文用 Markdown 语义组织（标题、段落、列表、粗体）。
- 代码块必须标注编程语言（如
python、js、```java）。 - 核心观点、关键结论用 粗体 强调。
四、输出要求
将完整博客渲染为 HTML 并写入文件，不要只在对话中贴文本。
- 文件名用核心关键词的英文 slug（如
agent-skill.html）。 - 回答末尾只给出文件位置，不解释、不铺垫、不废话。
五、HTML 输出规范
- 输出标准 HTML5：以
<!DOCTYPE html>开头，含与。 内必须含和 ``（标题用博客标题）。- 用一段 `` 内联 CSS 做基础排版：正文行高 1.7、字号 16px、代码块灰底圆角、标题层级分明、容器最大宽度 760px 居中。
- Markdown 正文手动转为对应 HTML 标签：标题
/、段落、粗体、列表/。 - 代码块用 `` 包裹，必须标注语言且内容完整可运行。
- 页面在浏览器直接打开即可阅读，不依赖任何外部资源（无外链 CSS/JS/图片）。
自查清单（交付前逐条核对）
- 标题含核心关键词且简洁
- 开头是反直觉观点或痛点，没有平淡套话
- 每段 ≤ 5 句
- 每个术语首次出现都有解释
- 所有代码块标注了语言，且完整可运行
- 没有出现「首先/其次/最后/综上所述」
- 没有「很多/一些/非常」等模糊词，改用具体数字实例
- 关键结论已用粗体强调
- 结尾有要点总结 + 具体下一步行动建议
- 已写入 HTML 文件：含
<!DOCTYPE html>、（charset + title）、、内联 `` - 代码块用 `` 标注语言
- 页面无外部依赖，浏览器直接打开可读
Related skills
Polish a technical blog draft into an 1000–1200 word, 4-5 section en-US article, preserve technical terms/code, and generate consistent hero + per-section image prompts when the user asks to polish and translate a blog with images.
Creates engaging, example-driven long-form articles with strong hooks, clear argument structures, and reader retention strategies. Use when the user asks to write an in-depth article, blog post, newsletter, social media thread, or any content that needs to hold readers' attention. Also use when the user says "write an article about [topic]" or "turn these notes into a publishable piece".
1 stars
Writes professional blog posts, social media content, and email newsletters optimized for SEO and engagement. Follows proven content frameworks to deliver pu...
Polish a technical blog draft into an 800–1000 word, 3–4 section zh-CN article, preserve technical terms/code, and generate consistent hero + per-section image prompts when the user asks to polish and translate a blog with images.
28 installs
blog to video, blog post to video, article to video — convert a blog post into a narrated video with storyboard, voiceover, and build. Use when the user gives a blog post (text or link) and wants a video version for social or YouTube.