Walks through writing a blog post from an idea and source material: research, brainstorming, outline approval, versioned drafts and optional git commits.
SKILL.md written in Chinese; this summary is our English description.
$ npx skills add luongnv89/claude-howto --skill blog-draft -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install luongnv89/claude-howto blog-draft --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/luongnv89/claude-howto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/zh/03-skills/blog-draft .claude/skills/blog-draft && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "blog-draft" agent skill from https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draft into .claude/skills/blog-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-draft", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draftType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add luongnv89/claude-howto --skill blog-draft -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install luongnv89/claude-howto blog-draft --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luongnv89/claude-howto.git skills-src && mkdir -p .agents/skills && cp -r skills-src/zh/03-skills/blog-draft .agents/skills/blog-draft && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blog-draft" agent skill from https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draft into .agents/skills/blog-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-draft", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add luongnv89/claude-howto --skill blog-draft -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install luongnv89/claude-howto blog-draft --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luongnv89/claude-howto.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/zh/03-skills/blog-draft .cursor/skills/blog-draft && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "blog-draft" agent skill from https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draft into .cursor/skills/blog-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-draft", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/luongnv89/claude-howto.git --path zh/03-skills/blog-draft--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add luongnv89/claude-howto --skill blog-draft -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install luongnv89/claude-howto blog-draft --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luongnv89/claude-howto.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/zh/03-skills/blog-draft .gemini/skills/blog-draft && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "blog-draft" agent skill from https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draft into .gemini/skills/blog-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-draft", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install luongnv89/claude-howto blog-draftInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add luongnv89/claude-howto --skill blog-draft -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/luongnv89/claude-howto.git skills-src && mkdir -p .github/skills && cp -r skills-src/zh/03-skills/blog-draft .github/skills/blog-draft && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "blog-draft" agent skill from https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draft into .github/skills/blog-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-draft", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add luongnv89/claude-howto --skill blog-draft -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install luongnv89/claude-howto blog-draft --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luongnv89/claude-howto.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/zh/03-skills/blog-draft .opencode/skills/blog-draft && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "blog-draft" agent skill from https://github.com/luongnv89/claude-howto/tree/main/zh/03-skills/blog-draft into .opencode/skills/blog-draft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-draft", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
blog-draftWalks through writing a blog post from an idea and source material: research, brainstorming, outline approval, versioned drafts and optional git commits.
This Chinese-language workflow starts from a topic you provide, plus optional URLs, files, a target reader and a tone. The agent creates a dated folder under `blog-posts/` with a `resources/` subfolder, fetches or summarizes each source into its own markdown file, shows you the research summary, then brainstorms with questions about the main takeaway, points to stress, exclusions and target length (short at 500-800 words, medium at 1000-1500, long at 2000 or more).
Once you approve an outline, saved as `OUTLINE.md`, the agent writes the full draft to `draft-v0.1.md` following that structure, with an opening hook, clear headings and supporting evidence from the research. Every statistic or comparison needs an inline citation linked to a references section. In a git repository it commits and pushes the outline and each draft with `docs:` messages. It waits for your approval at marked steps, and a request to update an existing post jumps straight to the iteration step.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 556af8d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blog Draft Workflow loads about 1.1k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 264 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from luongnv89/claude-howto at commit 556af8d, republished under its MIT licence (© luongnv89). 264 words, ~1,057 tokens.
.claude/skills/blog-draft/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.$ARGUMENTS在继续之前，你必须先考虑用户输入。用户应提供：
重要：如果用户是在请求更新一篇已有博客文章，请跳过步骤 0-8，直接从步骤 9 开始。先阅读现有草稿文件，再继续迭代流程。
请按顺序执行以下步骤。不要跳步，也不要在未获得用户批准的情况下继续执行标明需要确认的步骤。
使用以下格式生成文件夹名称：YYYY-MM-DD-short-topic-name
创建文件夹结构：
blog-posts/
└── YYYY-MM-DD-short-topic-name/
└── resources/在继续前，先向用户确认文件夹已创建。
在博客文章目录中创建 resources/ 子文件夹
对于每个提供的资源：
resources/ 下的 markdown 文件中resources/ 中做摘要为每个资源在 resources/ 中创建摘要文件：
resources/source-1-[short-name].mdresources/source-2-[short-name].md每个摘要都应包含：
# 来源：[标题/URL]
## 要点
- 要点 1
- 要点 2
## 相关引文/数据
- 引文或统计 1
- 引文或统计 2
## 与主题的关联
简要说明其相关性向用户展示研究摘要。
基于想法和已研究的资源，展示：
提出澄清问题：
在继续之前，等待用户回复。
创建一个结构化提纲，包括：
# 博客文章提纲：[标题]
## 元信息
- **目标读者**：[谁]
- **语气**：[风格]
- **目标长度**：[字数]
- **核心结论**：[关键信息]
## 建议结构
### 开场/引子
- 开场钩子思路
- 背景铺垫
- 论点陈述
### 第一部分：[标题]
- 关键点 A
- 关键点 B
- 来自 [来源] 的支撑证据
### 第二部分：[标题]
- 关键点 A
- 关键点 B
[继续列出所有部分...]
### 结论
- 关键点总结
- 行动号召或最终思考
## 需要引用的来源
- 来源 1
- 来源 2向用户展示提纲，并请求批准或修改意见。
用户批准提纲后，将其保存为博客文章文件夹中的 OUTLINE.md。
确认提纲已保存。
检查当前目录是否为 git 仓库。
如果是：
OUTLINE.mddocs: Add outline for blog post - [topic-name]如果不是 git 仓库，则跳过此步骤并告知用户。
基于已批准的提纲，撰写完整博客草稿。
严格按照 OUTLINE.md 的结构进行编写。
包含：
将草稿保存为博客文章文件夹中的 draft-v0.1.md。
格式：
# [博客文章标题]
*[可选：副标题或标语]*
[包含行内引用的完整正文...]
---
## 参考资料
- [1] 来源 1 标题 - URL 或引用
- [2] 来源 2 标题 - URL 或引用
- [3] 来源 3 标题 - URL 或引用引用要求：
检查是否处于 git 仓库中。
如果是：
docs: Add draft v0.1 for blog post - [topic-name]如果不是 git 仓库，则跳过并告知用户。
向用户展示草稿内容。
询问反馈：
等待用户回复。
如果用户要求修改：
draft-v[X.Y].md如果用户批准：
final.md所有草稿都会以递增版本号保留：
draft-v0.1.md - 初始草稿draft-v0.2.md - 第一轮反馈后draft-v0.3.md - 第二轮反馈后这可以跟踪博客文章的演变过程，并在需要时回退。
blog-posts/
└── YYYY-MM-DD-topic-name/
├── resources/
│ ├── source-1-name.md
│ ├── source-2-name.md
│ └── ...
├── OUTLINE.md
├── draft-v0.1.md
├── draft-v0.2.md（如果有迭代）
└── draft-v0.3.md（如果还有更多迭代）© luongnv89, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in zh/03-skills/blog-draft of luongnv89/claude-howto.
Open the folder on GitHubat commit 556af8d
Blog Draft Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Blog Draft Workflow this skillluongnv89/claude-howto | 42k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Aboutsecurity Content Ingestionwgpsec/AboutSecurity | 1.8k | — | ~1.4k | Automated safety check: Pass | None | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Figurevectorize-io/hindsight | 47k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SepiaNanako0129/sepia | 3k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Notion To Blogwasp-lang/wasp | 19k | — | ~922 | Automated safety check: Pass | MIT |
wgpsec/AboutSecurity
A skill your agent uses whenever the user asks to add, absorb, migrate, port, update, merge, compare, or extract security knowledge into the AboutSecurity repository from any external resource such…
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
vectorize-io/hindsight
Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
wasp-lang/wasp
Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.
kharmanskyi/open-steps
ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what…
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
luongnv89/claude-howto
Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
luongnv89/claude-howto
Ensure all communication matches brand voice and tone guidelines. Use when creating marketing copy, customer communications, public-facing content, or when…
luongnv89/claude-howto
Reviews code for security, performance, quality and maintainability, using a checklist, a finding template and two metrics scripts.
luongnv89/claude-howto
Runs a quick or deep quiz on Claude Code skills, scores ten feature areas and generates a personalized learning path with prioritized next steps.
Works with
Categories
Walks through writing a blog post from an idea and source material: research, brainstorming, outline approval, versioned drafts and optional git commits. This Chinese-language workflow starts from a topic you provide, plus optional URLs, files, a target reader and a tone. The agent creates a dated folder under `blog-posts/` with a `resources/` subfolder, fetches or summarizes each source into its own markdown file, shows you the research summary, then brainstorms with questions about the main takeaway, points to stress, exclusions and target length (short at 500-800 words, medium at 1000-1500, long at 2000 or more).
Blog Draft Workflow fits situations like: turning an idea plus reference links into a first blog draft; writing a researched post where every claim cites a source; revising an existing draft through numbered versions.
Run `npx skills add luongnv89/claude-howto --skill blog-draft -a claude-code`. Or copy the skill folder (zh/03-skills/blog-draft in luongnv89/claude-howto) into .claude/skills/blog-draft in your project. Claude Code loads it when a task matches its description.
Run `npx skills add luongnv89/claude-howto --skill blog-draft -a codex`. Or copy the skill folder (zh/03-skills/blog-draft in luongnv89/claude-howto) into .agents/skills/blog-draft in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add luongnv89/claude-howto --skill blog-draft -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-draft, .gemini/skills/blog-draft, .github/skills/blog-draft and .opencode/skills/blog-draft in your project.
SKILL.md names no scripts, command-line tools or credentials: Blog Draft Workflow is instructions for the agent only. Our summary lists: Web access to fetch source URLs; A git repository, only if you want the outline and drafts committed.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Blog Draft Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Blog Draft Workflow: Aboutsecurity Content Ingestion (wgpsec/AboutSecurity, 1.8k stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 47k stars) and Sepia (Nanako0129/sepia, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
luongnv89 (a GitHub user) maintains it in luongnv89/claude-howto, which has 41,779 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 30, 2026.
Source: luongnv89/claude-howto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
