funnel-planner

Name: funnel-planner
Author: Affitor

6installs184forks

How to install funnel-planner?

affitor/affiliate-skills/funnel-planner

$npx -y skills add Affitor/affiliate-skills --skill funnel-planner

Installs into the current project.

Summary

Plan a complete affiliate funnel from research to revenue. Triggers on: "plan my affiliate funnel", "create a funnel strategy", "affiliate business plan", "how to start affiliate marketing", "full funnel roadmap", "plan from scratch", "week by week affiliate plan", "chain skills

Files · 1

View on GitHub

SKILL.md

1	# Funnel Planner
2
3	Plan a complete affiliate funnel from research to revenue by chaining Affitor skills into a week-by-week execution roadmap. Output is a Markdown plan with skill sequence, time estimates, and exact invocation prompts for each step.
4
5	## Stage
6
7	S8: Meta — Most affiliates fail because they skip steps or work out of order. Funnel Planner solves this by mapping the user's resources (time, channels, experience) to a personalized execution plan that chains S1-S7 skills in the right sequence. It's the onboarding wizard for affiliate marketing via AI agent.
8
9	## When to Use
10
11	- User is starting from scratch and wants a complete plan
12	- User asks "how do I start affiliate marketing?"
13	- User has a niche but no strategy
14	- User wants to know which skills to use and in what order
15	- User says "build me a funnel" or "plan my affiliate business"
16	- User wants a week-by-week roadmap
17	- Chaining: this skill recommends which other skills to run and in what order
18
19	## Input Schema
20
21	```yaml
22	niche: string # OPTIONAL — e.g., "AI tools", "fitness supplements"
23	# If not provided, S1 research will help identify one
24
25	product: string # OPTIONAL — specific product if already chosen
26	# e.g., "HeyGen" or "Semrush"
27
28	experience_level: string # OPTIONAL — "beginner" \| "intermediate" \| "advanced"
29	# Default: "beginner"
30
31	available_channels: # OPTIONAL — platforms the user can use
32	- string # e.g., ["blog", "twitter", "linkedin", "email"]
33	# Default: ["blog", "twitter"]
34
35	weekly_hours: number # OPTIONAL — hours per week available
36	# Default: 5
37
38	goal: string # OPTIONAL — "first_commission" \| "scale_to_1k" \| "scale_to_10k"
39	# Default: "first_commission"
40	```
41
42	Chaining context: If S1 was run earlier, pull niche and product info from conversation. If the user has mentioned their channels or experience, use that context.
43
44	## Workflow
45
46	### Step 1: Assess Starting Point
47
48	Determine where the user is:
49	- Has nothing: Start from S1 (full funnel)
50	- Has a product: Skip S1, start from S2
51	- Has content: Skip S1-S2, start from S3 or S4
52	- Has traffic: Skip to S6 (analytics) or S7 (automation)
53
54	Ask clarifying questions only if truly ambiguous. Default to the most common case (beginner, starting from scratch).
55
56	### Step 2: Select Relevant Skills
57
58	Based on channels, experience, and goal, select 5-8 skills from S1-S7:
59	- Beginner + blog + twitter: S1 → S2 (viral-post-writer) → S3 (affiliate-blog-builder) → S5 (bio-link-deployer) → S6 (seo-audit)
60	- Intermediate + email + blog: S1 → S3 → S4 (landing-page-creator) → S5 (email-drip-sequence) → S6 (performance-report) → S7 (content-repurposer)
61	- Advanced + all channels: Full S1-S7 pipeline with S8 (compliance-checker) at each content step
62
63	### Step 3: Estimate Effort
64
65	For each selected skill, estimate time based on experience level:
66	- Beginner: 2-4 hours per skill
67	- Intermediate: 1-2 hours per skill
68	- Advanced: 30-60 minutes per skill
69
70	Fit into the user's `weekly_hours` to create a week-by-week schedule.
71
72	### Step 4: Create Roadmap
73
74	Build a week-by-week table:
75	- Week number
76	- Skill to run
77	- What it produces
78	- Time estimate
79	- Exact prompt to invoke the skill
80
81	### Step 5: Add Success Metrics
82
83	For each phase, define measurable outcomes:
84	- S1: "You should have 2-3 programs selected"
85	- S2: "You should have 5+ social posts ready"
86	- S3: "You should have 1-2 blog posts published"
87	- S5: "You should have a bio link page live"
88	- S6: "You should know your EPC and conversion rate"
89
90	### Step 6: Self-Validation
91
92	Before presenting output, verify:
93
94	- [ ] Roadmap follows logical sequence (S1→S2→S3... not random order)
95	- [ ] Invocation prompts are copy-paste ready for each skill
96	- [ ] Time estimates realistic for stated experience level
97	- [ ] Success metrics are measurable and specific (not "do well")
98	- [ ] Total weeks feasible given user's weekly hours budget
99
100	If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
101
102	## Output Schema
103
104	```yaml
105	output_schema_

People who liked this also viewed

6 picks

Type

funnel-planner

6installs184forks

View on GitHub

How to install funnel-planner?

affitor/affiliate-skills/funnel-planner

$npx -y skills add Affitor/affiliate-skills --skill funnel-planner

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Funnel Planner
2
3	Plan a complete affiliate funnel from research to revenue by chaining Affitor skills into a week-by-week execution roadmap. Output is a Markdown plan with skill sequence, time estimates, and exact invocation prompts for each step.
4
5	## Stage
6
7	S8: Meta — Most affiliates fail because they skip steps or work out of order. Funnel Planner solves this by mapping the user's resources (time, channels, experience) to a personalized execution plan that chains S1-S7 skills in the right sequence. It's the onboarding wizard for affiliate marketing via AI agent.
8
9	## When to Use
10
11	- User is starting from scratch and wants a complete plan
12	- User asks "how do I start affiliate marketing?"
13	- User has a niche but no strategy
14	- User wants to know which skills to use and in what order
15	- User says "build me a funnel" or "plan my affiliate business"
16	- User wants a week-by-week roadmap
17	- Chaining: this skill recommends which other skills to run and in what order
18
19	## Input Schema
20
21	```yaml
22	niche: string # OPTIONAL — e.g., "AI tools", "fitness supplements"
23	# If not provided, S1 research will help identify one
24
25	product: string # OPTIONAL — specific product if already chosen
26	# e.g., "HeyGen" or "Semrush"
27
28	experience_level: string # OPTIONAL — "beginner" \| "intermediate" \| "advanced"
29	# Default: "beginner"
30
31	available_channels: # OPTIONAL — platforms the user can use
32	- string # e.g., ["blog", "twitter", "linkedin", "email"]
33	# Default: ["blog", "twitter"]
34
35	weekly_hours: number # OPTIONAL — hours per week available
36	# Default: 5
37
38	goal: string # OPTIONAL — "first_commission" \| "scale_to_1k" \| "scale_to_10k"
39	# Default: "first_commission"
40	```
41
42	Chaining context: If S1 was run earlier, pull niche and product info from conversation. If the user has mentioned their channels or experience, use that context.
43
44	## Workflow
45
46	### Step 1: Assess Starting Point
47
48	Determine where the user is:
49	- Has nothing: Start from S1 (full funnel)
50	- Has a product: Skip S1, start from S2
51	- Has content: Skip S1-S2, start from S3 or S4
52	- Has traffic: Skip to S6 (analytics) or S7 (automation)
53
54	Ask clarifying questions only if truly ambiguous. Default to the most common case (beginner, starting from scratch).
55
56	### Step 2: Select Relevant Skills
57
58	Based on channels, experience, and goal, select 5-8 skills from S1-S7:
59	- Beginner + blog + twitter: S1 → S2 (viral-post-writer) → S3 (affiliate-blog-builder) → S5 (bio-link-deployer) → S6 (seo-audit)
60	- Intermediate + email + blog: S1 → S3 → S4 (landing-page-creator) → S5 (email-drip-sequence) → S6 (performance-report) → S7 (content-repurposer)
61	- Advanced + all channels: Full S1-S7 pipeline with S8 (compliance-checker) at each content step
62
63	### Step 3: Estimate Effort
64
65	For each selected skill, estimate time based on experience level:
66	- Beginner: 2-4 hours per skill
67	- Intermediate: 1-2 hours per skill
68	- Advanced: 30-60 minutes per skill
69
70	Fit into the user's `weekly_hours` to create a week-by-week schedule.
71
72	### Step 4: Create Roadmap
73
74	Build a week-by-week table:
75	- Week number
76	- Skill to run
77	- What it produces
78	- Time estimate
79	- Exact prompt to invoke the skill
80
81	### Step 5: Add Success Metrics
82
83	For each phase, define measurable outcomes:
84	- S1: "You should have 2-3 programs selected"
85	- S2: "You should have 5+ social posts ready"
86	- S3: "You should have 1-2 blog posts published"
87	- S5: "You should have a bio link page live"
88	- S6: "You should know your EPC and conversion rate"
89
90	### Step 6: Self-Validation
91
92	Before presenting output, verify:
93
94	- [ ] Roadmap follows logical sequence (S1→S2→S3... not random order)
95	- [ ] Invocation prompts are copy-paste ready for each skill
96	- [ ] Time estimates realistic for stated experience level
97	- [ ] Success metrics are measurable and specific (not "do well")
98	- [ ] Total weeks feasible given user's weekly hours budget
99
100	If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
101
102	## Output Schema
103
104	```yaml
105	output_schema_

People who liked this also viewed

6 picks

Type