重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
npx skills add https://github.com/mblode/agent-skills --skill blog-post研究、起草并润色达到发表水平的博客文章。
博客文章进度:
- [ ] 步骤 1:明确主题和格式
- [ ] 步骤 2:研究和收集资料
- [ ] 步骤 3:提取关键见解并制定大纲
- [ ] 步骤 4:撰写文章
- [ ] 步骤 5:SEO 优化和润色
- [ ] 步骤 6:质量验证
在写作前确定文章类型。如果不明确,请询问用户:
| 格式 | 最适合 | 结构 |
|---|---|---|
| 清单式文章 | 来自资料的惊人发现 | 带分析的编号见解 |
| 教程 / 操作指南 | 逐步教授一个过程 | 问题 → 步骤 → 结果 |
| 叙述性文章 | 个人经历或旅程 | 带有张力和解决方式的故事弧线 |
| 思想领导力文章 | 行业评论或观点 | 论点 → 证据 → 启示 |
阅读文件、获取 URL 或接受粘贴的文本。如果用户提供了主题但没有资料,请在写作前研究该主题。在制定大纲前完整阅读每个资料。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
接受杂乱的输入——零散的想法、要点、思维转储、随机观察。混乱是输入;结构是输出。
在起草前创建章节大纲。每个章节都应有明确的目的。
从 references/format-templates.md 加载匹配的模板并遵循其结构。只加载所选格式的模板——而不是全部四个。
在最终确定前,请验证:
- [ ] 开头 1-2 句话能抓住注意力
- [ ] 标题具体且兑现了其承诺
- [ ] 每个段落最多 2-4 句话
- [ ] 每个部分都有分析或见解,而不仅仅是总结
- [ ] 块引用总共限制在 2-4 个
- [ ] 结论以问题、行动号召或挑衅性的观点展望未来
- [ ] 全文语气是对话式的——没有学术语言
- [ ] 标题少于 60 个字符并包含主要关键词
- [ ] 文章包含元描述(150-160 字符)
- [ ] Markdown 渲染正确(标题、块引用、粗体、代码)
少于 60 个字符以利于 SEO。句子大小写,末尾无句号。必须兑现其承诺。
| 时机 | 运行 |
|---|---|
| 博客文章撰写完成后,审核文字质量 | docs-writing |
| 如果文章需要变成演示文稿 | presentation-creator |
| 编辑和润色文案 | copy-editing |
| 超越基础优化 SEO | optimise-seo |
每周安装次数
52
代码仓库
GitHub 星标数
20
首次出现
2026 年 2 月 22 日
安全审计
安装于
opencode51
gemini-cli51
github-copilot51
codex51
cursor51
amp50
Research, draft, and polish publication-ready blog posts.
Blog post progress:
- [ ] Step 1: Clarify topic and format
- [ ] Step 2: Research and gather sources
- [ ] Step 3: Extract key insights and outline
- [ ] Step 4: Write the post
- [ ] Step 5: SEO and polish
- [ ] Step 6: Validate quality
Determine the post type before writing. Ask the user if unclear:
| Format | Best for | Structure |
|---|---|---|
| Listicle | Surprising takeaways from sources | Numbered insights with analysis |
| Tutorial / how-to | Teaching a process step by step | Problem → steps → result |
| Narrative | Personal experience or journey | Story arc with tension and resolution |
| Thought leadership | Industry commentary or opinion | Thesis → evidence → implications |
Read files, fetch URLs, or accept pasted text. If the user provides a topic without sources, research the topic before writing. Read every source completely before outlining.
Accept messy input — scattered thoughts, bullet points, brain dumps, random observations. The mess is the input; structure is the output.
Create a section outline before drafting. Each section should have a clear purpose.
Load the matching template from references/format-templates.md and follow its structure. Only load the template for the chosen format — not all four.
Before finalizing, verify:
- [ ] Hook grabs attention in the first 1-2 sentences
- [ ] Headline is specific and delivers on its promise
- [ ] Every paragraph is 2-4 sentences maximum
- [ ] Each section has analysis or insight, not just summary
- [ ] Blockquotes are limited to 2-4 total
- [ ] Conclusion looks forward with a question, CTA, or provocative takeaway
- [ ] Tone is conversational throughout — no academic language
- [ ] Title is under 60 characters with the main keyword
- [ ] Post includes a meta description (150-160 chars)
- [ ] Markdown renders correctly (headings, blockquotes, bold, code)
Under 60 characters for SEO. Sentence case, no trailing period. Must deliver on its promise.
| When | Run |
|---|---|
| After blog post is written, audit prose quality | docs-writing |
| If post needs to become a presentation | presentation-creator |
| Edit and polish the copy | copy-editing |
| Optimize SEO beyond basics | optimise-seo |
Weekly Installs
52
Repository
GitHub Stars
20
First Seen
Feb 22, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
opencode51
gemini-cli51
github-copilot51
codex51
cursor51
amp50
SaaS营销创意库 | 139个已验证营销策略,按阶段/预算/资源智能推荐
39,900 周安装