User Input
$ARGUMENTS
You MUST consider the user input before proceeding. User should provide:
- Idea/Topic: The main concept or theme for the blog post
- Resources: URLs, files, or references to research (optional but recommended)
- Target audience: Who the blog post is for (optional)
- Tone/Style: Formal, casual, technical, etc. (optional)
IMPORTANT: If the user is requesting updates to an existing blog post, skip steps 0-8 and start directly at Step 9. Read the existing draft file(s) first, then proceed with the iteration process.
Execution Flow
Follow these steps sequentially. Do not skip steps or proceed without user approval where indicated.
Step 0: Create Project Folder
Generate a folder name using format: YYYY-MM-DD-short-topic-name
- Use today's date
- Create a short, URL-friendly slug from the topic (lowercase, hyphens, max 5 words)
Create the folder structure:
blog-posts/
└── YYYY-MM-DD-short-topic-name/
└── resources/
Confirm folder creation with user before proceeding.
Step 1: Research & Resource Collection
Create resources/ subfolder in the blog post directory
For each provided resource:
- URLs: Fetch and save key information to
resources/ as markdown files
- Files: Read and summarize in
resources/
- Topics: Use web search to gather up-to-date information
For each resource, create a summary file in resources/:
resources/source-1-[short-name].md
resources/source-2-[short-name].md
- etc.
Each summary should include:
# Source: [Title/URL]
## Key Points
- Point 1
- Point 2
## Relevant Quotes/Data
- Quote or statistic 1
- Quote or statistic 2
## How This Relates to Topic
Brief explanation of relevance
Present research summary to user.
Step 2: Brainstorm & Clarify
Based on the idea and researched resources, present:
- Main themes identified from research
- Potential angles for the blog post
- Key points that should be covered
- Gaps in information that need clarification
Ask clarifying questions:
- What is the main takeaway you want readers to have?
- Are there specific points from the research you want to emphasize?
- What's the target length? (short: 500-800 words, medium: 1000-1500, long: 2000+)
- Any points you want to exclude?
Wait for user responses before proceeding.
Step 3: Propose Outline
Create a structured outline including:
# Blog Post Outline: [Title]
## Meta Information
- **Target Audience**: [who]
- **Tone**: [style]
- **Target Length**: [word count]
- **Main Takeaway**: [key message]
## Proposed Structure
### Hook/Introduction
- Opening hook idea
- Context setting
- Thesis statement
### Section 1: [Title]
- Key point A
- Key point B
- Supporting evidence from [source]
### Section 2: [Title]
- Key point A
- Key point B
[Continue for all sections...]
### Conclusion
- Summary of key points
- Call to action or final thought
## Sources to Cite
- Source 1
- Source 2
Present outline to user and ask for approval or modifications.
Step 4: Save Approved Outline
Once user approves the outline, save it to OUTLINE.md in the blog post folder.
Confirm the outline has been saved.
Step 5: Commit Outline (if in git repo)
Check if current directory is a git repository.
If yes:
- Stage the new files: blog post folder, resources, and OUTLINE.md
- Create commit with message:
docs: Add outline for blog post - [topic-name]
- Push to remote
If not a git repo, skip this step and inform user.
Step 6: Write Draft
Based on the approved outline, write the full blog post draft.
Follow the structure from OUTLINE.md exactly.
Include:
- Engaging introduction with hook
- Clear section headers
- Supporting evidence and examples from research
- Smooth transitions between sections
- Strong conclusion with takeaway
- Citations: All comparisons, statistics, data points, and factual claims MUST cite the original source
Save the draft as draft-v0.1.md in the blog post folder.
Format:
# [Blog Post Title]
*[Optional: subtitle or tagline]*
[Full content with inline citations...]
---
## References
- [1] Source 1 Title - URL or Citation
- [2] Source 2 Title - URL or Citation
- [3] Source 3 Title - URL or Citation
Citation Requirements:
- Every data point, statistic, or comparison MUST have an inline citation
- Use numbered references [1], [2], etc., or named citations [Source Name]
- Link citations to the References section at the end
- Example: "Studies show that 65% of developers prefer TypeScript [1]"
- Example: "React outperforms Vue in rendering speed by 20% [React Benchmarks 2024]"
Step 7: Commit Draft (if in git repo)
Check if in git repository.
If yes:
- Stage the draft file
- Create commit with message:
docs: Add draft v0.1 for blog post - [topic-name]
- Push to remote
If not a git repo, skip and inform user.
Step 8: Present Draft for Review
Present the draft content to user.
Ask for feedback:
- Overall impression?
- Sections that need expansion or reduction?
- Tone adjustments needed?
- Missing information?
- Specific edits or rewrites?
Wait for user response.
Step 9: Iterate or Finalize
If user requests changes:
- Note all requested modifications
- Return to Step 6 with the following adjustments:
- Increment version number (v0.2, v0.3, etc.)
- Incorporate all feedback
- Save as
draft-v[X.Y].md
- Repeat Steps 7-8
If user approves:
- Confirm the final draft version
- Optionally rename to
final.md if user requests
- Summarize the blog post creation process:
- Total versions created
- Key changes between versions
- Final word count
- Files created
Version Tracking
All drafts are preserved with incremental versioning:
draft-v0.1.md - Initial draft
draft-v0.2.md - After first round of feedback
draft-v0.3.md - After second round of feedback
- etc.
This allows tracking the evolution of the blog post and reverting if needed.
Output Files Structure
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 (if iterations)
└── draft-v0.3.md (if more iterations)
Tips for Quality
- Hook: Start with a question, surprising fact, or relatable scenario
- Flow: Each paragraph should connect to the next
- Evidence: Support claims with data from research
- Citations: ALWAYS cite sources for:
- All statistics and data points (e.g., "According to [Source], 75% of...")
- Comparisons between products, services, or approaches (e.g., "X performs 2x faster than Y [Source]")
- Factual claims about market trends, research findings, or benchmarks
- Use inline citations with format: [Source Name] or [Author, Year]
- Voice: Maintain consistent tone throughout
- Length: Respect the target word count
- Readability: Use short paragraphs, bullet points where appropriate
- CTA: End with a clear call-to-action or thought-provoking question
Notes
- Always wait for user approval at outlined checkpoints
- Preserve all draft versions for history
- Use web search for up-to-date information when URLs are provided
- If resources are insufficient, ask user for more or suggest additional research
- Adapt tone based on target audience (technical, general, business, etc.)
Last Updated: August 4, 2026
Claude Code Version: 2.1.220
Sources:
1---
2name: blog-draft
3description: Draft a blog post from ideas and resources. Use when users want to write a blog post, create content from research, or draft articles. Guides through research, brainstorming, outlining, and iterative drafting with version control.
4metadata:
5 source: https://skillmd.com/skills/luongnv89/blog-draft
6---
7
8## User Input
9
10```text
11$ARGUMENTS
12```
13
14You **MUST** consider the user input before proceeding. User should provide:
15- **Idea/Topic**: The main concept or theme for the blog post
16- **Resources**: URLs, files, or references to research (optional but recommended)
17- **Target audience**: Who the blog post is for (optional)
18- **Tone/Style**: Formal, casual, technical, etc. (optional)
19
20**IMPORTANT**: If the user is requesting updates to an **existing blog post**, skip steps 0-8 and start directly at **Step 9**. Read the existing draft file(s) first, then proceed with the iteration process.
21
22## Execution Flow
23
24Follow these steps sequentially. **Do not skip steps or proceed without user approval where indicated.**
25
26### Step 0: Create Project Folder
27
281. Generate a folder name using format: `YYYY-MM-DD-short-topic-name`
29 - Use today's date
30 - Create a short, URL-friendly slug from the topic (lowercase, hyphens, max 5 words)
31
322. Create the folder structure:
33 ```
34 blog-posts/
35 └── YYYY-MM-DD-short-topic-name/
36 └── resources/
37 ```
38
393. Confirm folder creation with user before proceeding.
40
41### Step 1: Research & Resource Collection
42
431. Create `resources/` subfolder in the blog post directory
44
452. For each provided resource:
46 - **URLs**: Fetch and save key information to `resources/` as markdown files
47 - **Files**: Read and summarize in `resources/`
48 - **Topics**: Use web search to gather up-to-date information
49
503. For each resource, create a summary file in `resources/`:
51 - `resources/source-1-[short-name].md`
52 - `resources/source-2-[short-name].md`
53 - etc.
54
554. Each summary should include:
56 ```markdown
57 # Source: [Title/URL]
58
59 ## Key Points
60 - Point 1
61 - Point 2
62
63 ## Relevant Quotes/Data
64 - Quote or statistic 1
65 - Quote or statistic 2
66
67 ## How This Relates to Topic
68 Brief explanation of relevance
69 ```
70
715. Present research summary to user.
72
73### Step 2: Brainstorm & Clarify
74
751. Based on the idea and researched resources, present:
76 - **Main themes** identified from research
77 - **Potential angles** for the blog post
78 - **Key points** that should be covered
79 - **Gaps** in information that need clarification
80
812. Ask clarifying questions:
82 - What is the main takeaway you want readers to have?
83 - Are there specific points from the research you want to emphasize?
84 - What's the target length? (short: 500-800 words, medium: 1000-1500, long: 2000+)
85 - Any points you want to exclude?
86
873. **Wait for user responses before proceeding.**
88
89### Step 3: Propose Outline
90
911. Create a structured outline including:
92
93 ```markdown
94 # Blog Post Outline: [Title]
95
96 ## Meta Information
97 - **Target Audience**: [who]
98 - **Tone**: [style]
99 - **Target Length**: [word count]
100 - **Main Takeaway**: [key message]
101
102 ## Proposed Structure
103
104 ### Hook/Introduction
105 - Opening hook idea
106 - Context setting
107 - Thesis statement
108
109 ### Section 1: [Title]
110 - Key point A
111 - Key point B
112 - Supporting evidence from [source]
113
114 ### Section 2: [Title]
115 - Key point A
116 - Key point B
117
118 [Continue for all sections...]
119
120 ### Conclusion
121 - Summary of key points
122 - Call to action or final thought
123
124 ## Sources to Cite
125 - Source 1
126 - Source 2
127 ```
128
1292. Present outline to user and **ask for approval or modifications**.
130
131### Step 4: Save Approved Outline
132
1331. Once user approves the outline, save it to `OUTLINE.md` in the blog post folder.
134
1352. Confirm the outline has been saved.
136
137### Step 5: Commit Outline (if in git repo)
138
1391. Check if current directory is a git repository.
140
1412. If yes:
142 - Stage the new files: blog post folder, resources, and OUTLINE.md
143 - Create commit with message: `docs: Add outline for blog post - [topic-name]`
144 - Push to remote
145
1463. If not a git repo, skip this step and inform user.
147
148### Step 6: Write Draft
149
1501. Based on the approved outline, write the full blog post draft.
151
1522. Follow the structure from OUTLINE.md exactly.
153
1543. Include:
155 - Engaging introduction with hook
156 - Clear section headers
157 - Supporting evidence and examples from research
158 - Smooth transitions between sections
159 - Strong conclusion with takeaway
160 - **Citations**: All comparisons, statistics, data points, and factual claims MUST cite the original source
161
1624. Save the draft as `draft-v0.1.md` in the blog post folder.
163
1645. Format:
165 ```markdown
166 # [Blog Post Title]
167
168 *[Optional: subtitle or tagline]*
169
170 [Full content with inline citations...]
171
172 ---
173
174 ## References
175 - [1] Source 1 Title - URL or Citation
176 - [2] Source 2 Title - URL or Citation
177 - [3] Source 3 Title - URL or Citation
178 ```
179
1806. **Citation Requirements**:
181 - Every data point, statistic, or comparison MUST have an inline citation
182 - Use numbered references [1], [2], etc., or named citations [Source Name]
183 - Link citations to the References section at the end
184 - Example: "Studies show that 65% of developers prefer TypeScript [1]"
185 - Example: "React outperforms Vue in rendering speed by 20% [React Benchmarks 2024]"
186
187### Step 7: Commit Draft (if in git repo)
188
1891. Check if in git repository.
190
1912. If yes:
192 - Stage the draft file
193 - Create commit with message: `docs: Add draft v0.1 for blog post - [topic-name]`
194 - Push to remote
195
1963. If not a git repo, skip and inform user.
197
198### Step 8: Present Draft for Review
199
2001. Present the draft content to user.
201
2022. Ask for feedback:
203 - Overall impression?
204 - Sections that need expansion or reduction?
205 - Tone adjustments needed?
206 - Missing information?
207 - Specific edits or rewrites?
208
2093. **Wait for user response.**
210
211### Step 9: Iterate or Finalize
212
213**If user requests changes:**
2141. Note all requested modifications
2152. Return to Step 6 with the following adjustments:
216 - Increment version number (v0.2, v0.3, etc.)
217 - Incorporate all feedback
218 - Save as `draft-v[X.Y].md`
219 - Repeat Steps 7-8
220
221**If user approves:**
2221. Confirm the final draft version
2232. Optionally rename to `final.md` if user requests
2243. Summarize the blog post creation process:
225 - Total versions created
226 - Key changes between versions
227 - Final word count
228 - Files created
229
230## Version Tracking
231
232All drafts are preserved with incremental versioning:
233- `draft-v0.1.md` - Initial draft
234- `draft-v0.2.md` - After first round of feedback
235- `draft-v0.3.md` - After second round of feedback
236- etc.
237
238This allows tracking the evolution of the blog post and reverting if needed.
239
240## Output Files Structure
241
242```
243blog-posts/
244└── YYYY-MM-DD-topic-name/
245 ├── resources/
246 │ ├── source-1-name.md
247 │ ├── source-2-name.md
248 │ └── ...
249 ├── OUTLINE.md
250 ├── draft-v0.1.md
251 ├── draft-v0.2.md (if iterations)
252 └── draft-v0.3.md (if more iterations)
253```
254
255## Tips for Quality
256
257- **Hook**: Start with a question, surprising fact, or relatable scenario
258- **Flow**: Each paragraph should connect to the next
259- **Evidence**: Support claims with data from research
260- **Citations**: ALWAYS cite sources for:
261 - All statistics and data points (e.g., "According to [Source], 75% of...")
262 - Comparisons between products, services, or approaches (e.g., "X performs 2x faster than Y [Source]")
263 - Factual claims about market trends, research findings, or benchmarks
264 - Use inline citations with format: [Source Name] or [Author, Year]
265- **Voice**: Maintain consistent tone throughout
266- **Length**: Respect the target word count
267- **Readability**: Use short paragraphs, bullet points where appropriate
268- **CTA**: End with a clear call-to-action or thought-provoking question
269
270## Notes
271
272- Always wait for user approval at outlined checkpoints
273- Preserve all draft versions for history
274- Use web search for up-to-date information when URLs are provided
275- If resources are insufficient, ask user for more or suggest additional research
276- Adapt tone based on target audience (technical, general, business, etc.)
277
278---
279
280**Last Updated**: August 4, 2026
281**Claude Code Version**: 2.1.220
282**Sources**:
283- https://code.claude.com/docs/en/skills
284**Compatible Models**: Claude Fable 5, Claude Opus 5, Claude Sonnet 5, Claude Sonnet 4.6, Claude Opus 4.8, Claude Haiku 4.5