how-to-tutorial-writer

Name: how-to-tutorial-writer
Author: Affitor

5installs184forks

How to install how-to-tutorial-writer?

affitor/affiliate-skills/how-to-tutorial-writer

$npx -y skills add Affitor/affiliate-skills --skill how-to-tutorial-writer

Installs into the current project.

Summary

Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "begin

Files · 1

View on GitHub

SKILL.md

1	# How-To Tutorial Writer
2
3	Write practical, step-by-step tutorial blog posts that solve a real reader problem and naturally recommend affiliate products as the best tool for the job. Uses the "problem → solution → tool" pattern: establish what the reader wants to do, show them exactly how to do it, and position the affiliate product as the right instrument for each step.
4
5	## When to Use
6
7	- User wants to create educational content that drives affiliate conversions indirectly
8	- User says "how to", "tutorial", "guide", "walkthrough", "step by step"
9	- User wants to rank for "how to [task]" keywords (high traffic, lower competition than "best" keywords)
10	- User has a product that is best understood through demonstration, not just description
11	- User wants to build authority and trust in a niche before making a sale
12
13	## Workflow
14
15	### Step 1: Define the Tutorial Goal
16
17	Parse the request to identify:
18	- The task: what the reader wants to accomplish (e.g., "create AI videos for YouTube")
19	- The tool: which affiliate product enables the task (e.g., HeyGen)
20	- The audience: who is asking this question (beginner / intermediate / advanced)
21	- The end state: what the reader will have built or achieved by the end
22
23	If the task is vague ("write a tutorial about HeyGen"), default to the most popular use case for that tool — search for it: `"[product name] tutorial" OR "how to use [product name]"` — pick the highest-traffic query.
24
25	Tutorial types — detect from user's phrasing:
26	\| Signal \| Type \| Format \|
27	\|---\|---\|---\|
28	\| "How to get started", "beginners guide", "first time" \| `quickstart` \| 5-8 steps, 1,500-2,000 words \|
29	\| "Step by step", "complete guide", "full tutorial" \| `deep-dive` \| 8-15 steps, 2,500-3,500 words \|
30	\| "How to [specific feature]" \| `feature-focus` \| 5-8 steps on one feature, 1,500-2,000 words \|
31	\| "How to [goal] without [product]" → redirect to product \| `problem-solution` \| 6-10 steps, 2,000-2,500 words \|
32
33	### Step 2: Research the Tutorial Content
34
35	Use `web_search` to gather:
36	1. The actual step-by-step process for accomplishing the task
37	2. Common mistakes or gotchas beginners encounter
38	3. Official documentation or help articles for the product
39	4. What the top-ranking tutorials already cover (identify gaps)
40
41	Search queries:
42	- `"how to [task] with [product]"` — understand existing guides
43	- `"[product] tutorial [year]"` — find current instructions
44	- `"[product] [feature] settings"` — get accurate step names
45	- `"[task] mistakes beginners make"` — find pain points to address
46
47	Content accuracy rule: Never invent product UI details. If unsure about a specific button name or menu path, describe the action generically ("navigate to the settings section") rather than naming something that may be wrong.
48
49	### Step 3: Plan the Tutorial Structure
50
51	Map every section before writing. A well-structured tutorial follows this flow:
52
53	What readers need before starting (Prerequisites):
54	- Account requirements (free plan vs. paid tier needed for tutorial steps)
55	- Technical requirements
56	- Assets they should have ready (images, scripts, data)
57
58	The steps themselves:
59	- Each step = one atomic action (not a cluster of actions)
60	- Steps should be numbered, not just bulleted
61	- Each step has: action verb headline + explanation + expected result
62	- Decision points get callout boxes: "If you see X, do Y instead"
63
64	Affiliate integration points (natural, not forced):
65	1. In the Prerequisites section: "You'll need a [Product] account. [Sign up free here →](url)"
66	2. At the step where the product's key feature is used: contextual CTA
67	3. After showing the final result: "You just did X with [Product]. Here's what else it can do: [affiliate CTA]"
68	4. In the "Next Steps" section at the end
69
70	Rule: Never interrupt a step sequence with a hard sell. CTAs belong at natural pause points — before the reader starts, after they finish a major phase, and at the very end.
71
72	### Step 4: Write the Full Tutorial
73
74	Title formula:
75	- `How to [Task] with [Product]: Step-by-Step Guide ([Year])`
76	- `How to [Task]: A Beginner's Guide Using [Product]`
77	- `[Goal]: How to [Task] in [N] Steps (Even If You're New to [Topic])`
78
79	Introduction (150-200 words):
80	- Open with the reader's problem/

People who liked this also viewed

6 picks

Type

how-to-tutorial-writer

5installs184forks

View on GitHub

How to install how-to-tutorial-writer?

affitor/affiliate-skills/how-to-tutorial-writer

$npx -y skills add Affitor/affiliate-skills --skill how-to-tutorial-writer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# How-To Tutorial Writer
2
3	Write practical, step-by-step tutorial blog posts that solve a real reader problem and naturally recommend affiliate products as the best tool for the job. Uses the "problem → solution → tool" pattern: establish what the reader wants to do, show them exactly how to do it, and position the affiliate product as the right instrument for each step.
4
5	## When to Use
6
7	- User wants to create educational content that drives affiliate conversions indirectly
8	- User says "how to", "tutorial", "guide", "walkthrough", "step by step"
9	- User wants to rank for "how to [task]" keywords (high traffic, lower competition than "best" keywords)
10	- User has a product that is best understood through demonstration, not just description
11	- User wants to build authority and trust in a niche before making a sale
12
13	## Workflow
14
15	### Step 1: Define the Tutorial Goal
16
17	Parse the request to identify:
18	- The task: what the reader wants to accomplish (e.g., "create AI videos for YouTube")
19	- The tool: which affiliate product enables the task (e.g., HeyGen)
20	- The audience: who is asking this question (beginner / intermediate / advanced)
21	- The end state: what the reader will have built or achieved by the end
22
23	If the task is vague ("write a tutorial about HeyGen"), default to the most popular use case for that tool — search for it: `"[product name] tutorial" OR "how to use [product name]"` — pick the highest-traffic query.
24
25	Tutorial types — detect from user's phrasing:
26	\| Signal \| Type \| Format \|
27	\|---\|---\|---\|
28	\| "How to get started", "beginners guide", "first time" \| `quickstart` \| 5-8 steps, 1,500-2,000 words \|
29	\| "Step by step", "complete guide", "full tutorial" \| `deep-dive` \| 8-15 steps, 2,500-3,500 words \|
30	\| "How to [specific feature]" \| `feature-focus` \| 5-8 steps on one feature, 1,500-2,000 words \|
31	\| "How to [goal] without [product]" → redirect to product \| `problem-solution` \| 6-10 steps, 2,000-2,500 words \|
32
33	### Step 2: Research the Tutorial Content
34
35	Use `web_search` to gather:
36	1. The actual step-by-step process for accomplishing the task
37	2. Common mistakes or gotchas beginners encounter
38	3. Official documentation or help articles for the product
39	4. What the top-ranking tutorials already cover (identify gaps)
40
41	Search queries:
42	- `"how to [task] with [product]"` — understand existing guides
43	- `"[product] tutorial [year]"` — find current instructions
44	- `"[product] [feature] settings"` — get accurate step names
45	- `"[task] mistakes beginners make"` — find pain points to address
46
47	Content accuracy rule: Never invent product UI details. If unsure about a specific button name or menu path, describe the action generically ("navigate to the settings section") rather than naming something that may be wrong.
48
49	### Step 3: Plan the Tutorial Structure
50
51	Map every section before writing. A well-structured tutorial follows this flow:
52
53	What readers need before starting (Prerequisites):
54	- Account requirements (free plan vs. paid tier needed for tutorial steps)
55	- Technical requirements
56	- Assets they should have ready (images, scripts, data)
57
58	The steps themselves:
59	- Each step = one atomic action (not a cluster of actions)
60	- Steps should be numbered, not just bulleted
61	- Each step has: action verb headline + explanation + expected result
62	- Decision points get callout boxes: "If you see X, do Y instead"
63
64	Affiliate integration points (natural, not forced):
65	1. In the Prerequisites section: "You'll need a [Product] account. [Sign up free here →](url)"
66	2. At the step where the product's key feature is used: contextual CTA
67	3. After showing the final result: "You just did X with [Product]. Here's what else it can do: [affiliate CTA]"
68	4. In the "Next Steps" section at the end
69
70	Rule: Never interrupt a step sequence with a hard sell. CTAs belong at natural pause points — before the reader starts, after they finish a major phase, and at the very end.
71
72	### Step 4: Write the Full Tutorial
73
74	Title formula:
75	- `How to [Task] with [Product]: Step-by-Step Guide ([Year])`
76	- `How to [Task]: A Beginner's Guide Using [Product]`
77	- `[Goal]: How to [Task] in [N] Steps (Even If You're New to [Topic])`
78
79	Introduction (150-200 words):
80	- Open with the reader's problem/

People who liked this also viewed

6 picks

Type