multi-program-manager

Name: multi-program-manager
Author: Affitor

4installs184forks

How to install multi-program-manager?

affitor/affiliate-skills/multi-program-manager

$npx -y skills add Affitor/affiliate-skills --skill multi-program-manager

Installs into the current project.

Summary

Manage and compare multiple affiliate programs as a portfolio. Triggers on: "manage my affiliate programs", "compare my programs", "portfolio overview", "which program should I focus on", "diversify my affiliate income", "program switching", "affiliate portfolio", "program compar

Files · 1

View on GitHub

SKILL.md

1	# Multi-Program Manager
2
3	Manage and compare multiple affiliate programs as a portfolio — overview, performance comparison, diversification strategy, program switching decisions, and revenue allocation. Output is a portfolio dashboard with strategic recommendations and a weekly action plan.
4
5	## Stage
6
7	S7: Automation — Most affiliates either promote too few programs (concentration risk) or too many (effort dilution). This skill applies portfolio thinking to affiliate marketing: analyze your programs like investments, identify which to double down on, maintain, or drop, and allocate your limited time for maximum ROI.
8
9	## When to Use
10
11	- User manages multiple affiliate programs and wants a strategic overview
12	- User asks "which program should I focus on?" or "should I drop this program?"
13	- User wants to diversify their affiliate income
14	- User says "compare my programs", "portfolio review", "program strategy"
15	- User is deciding whether to add or remove programs
16	- Chaining from S6.3 (performance-report): take performance data and make strategic decisions
17
18	## Input Schema
19
20	```yaml
21	programs:
22	- name: string # REQUIRED — program name
23	affiliate_url: string # OPTIONAL — affiliate link
24	reward_value: string # OPTIONAL — commission (e.g., "30% recurring")
25	reward_type: string # OPTIONAL — "cps_recurring" \| "cps_one_time" \| "cpl" \| "cpc"
26	monthly_revenue: number # OPTIONAL — avg monthly revenue ($)
27	monthly_clicks: number # OPTIONAL — avg monthly clicks
28	niche: string # OPTIONAL — product category
29	status: string # OPTIONAL — "active" \| "paused" \| "new" \| "considering"
30
31	goal: string # OPTIONAL — "maximize_revenue" \| "diversify"
32	# \| "reduce_risk" \| "find_gaps"
33	# Default: "maximize_revenue"
34
35	budget_hours: number # OPTIONAL — weekly hours available for content
36	# Default: 10
37	```
38
39	Chaining context: If S1 program research or S6.3 performance data exists in conversation, pull program details and metrics automatically.
40
41	## Workflow
42
43	### Step 1: Build Portfolio Overview
44
45	Compile all programs into a dashboard:
46	- Program name, niche, commission type, commission value
47	- Monthly revenue, clicks, EPC
48	- Status (active/paused/new)
49	- Revenue share (% of total)
50
51	### Step 2: Calculate Per-Program Metrics
52
53	For each program with data:
54	- EPC: revenue / clicks
55	- Revenue Share: program revenue / total revenue × 100
56	- Effort-to-Revenue Ratio: estimated hours spent / revenue generated
57	- Commission Quality Score: recurring > one-time > per-lead > per-click
58
59	### Step 3: Apply Portfolio Analysis
60
61	Concentration Risk:
62	- If top program > 50% of revenue → HIGH RISK
63	- If top 2 programs > 80% → MODERATE RISK
64	- If no program > 30% → WELL DIVERSIFIED
65
66	Niche Overlap:
67	- Multiple programs in same niche → competing for same audience
68	- Different niches → healthy diversification
69
70	Revenue Stability:
71	- Recurring commissions → stable
72	- One-time commissions → volatile (need constant new traffic)
73
74	### Step 4: Generate Recommendations
75
76	For each program, assign an action:
77	- Double Down: High EPC, room to grow → create more content, scale traffic
78	- Maintain: Solid performer, no changes needed → keep existing content fresh
79	- Optimize: High traffic but low conversion → improve CTAs, landing pages, test variants
80	- Phase Out: Low EPC, low growth potential → redirect effort to better programs
81	- Add: Gap identified → research new programs with S1
82
83	### Step 5: Create Action Plan
84
85	Based on `budget_hours`, allocate weekly time:
86	- Double-down programs get 50% of time
87	- Maintain programs get 20%
88	- Optimize programs get 20%
89	- New program research gets 10%
90
91	Provide specific weekly tasks tied to Affitor skills.
92
93	### Step 6: Self-Validation
94
95	Before presenting output, verify:
96
97	- [ ] Revenue share percentages sum to ~100%
98	- [ ] EPC calculations correct (revenue ÷ clicks per program)
99	- [ ] Concentration risk accurate (flag if top program >50% of revenue)
100	- [ ] Actions match performance: double_down (Star), maintain (Cash Cow), optimize (Question Mark), phase_out (Dog)
101	- [ ] Weekly time allocation sums to user's st

People who liked this also viewed

6 picks

Type

multi-program-manager

4installs184forks

View on GitHub

How to install multi-program-manager?

affitor/affiliate-skills/multi-program-manager

$npx -y skills add Affitor/affiliate-skills --skill multi-program-manager

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Multi-Program Manager
2
3	Manage and compare multiple affiliate programs as a portfolio — overview, performance comparison, diversification strategy, program switching decisions, and revenue allocation. Output is a portfolio dashboard with strategic recommendations and a weekly action plan.
4
5	## Stage
6
7	S7: Automation — Most affiliates either promote too few programs (concentration risk) or too many (effort dilution). This skill applies portfolio thinking to affiliate marketing: analyze your programs like investments, identify which to double down on, maintain, or drop, and allocate your limited time for maximum ROI.
8
9	## When to Use
10
11	- User manages multiple affiliate programs and wants a strategic overview
12	- User asks "which program should I focus on?" or "should I drop this program?"
13	- User wants to diversify their affiliate income
14	- User says "compare my programs", "portfolio review", "program strategy"
15	- User is deciding whether to add or remove programs
16	- Chaining from S6.3 (performance-report): take performance data and make strategic decisions
17
18	## Input Schema
19
20	```yaml
21	programs:
22	- name: string # REQUIRED — program name
23	affiliate_url: string # OPTIONAL — affiliate link
24	reward_value: string # OPTIONAL — commission (e.g., "30% recurring")
25	reward_type: string # OPTIONAL — "cps_recurring" \| "cps_one_time" \| "cpl" \| "cpc"
26	monthly_revenue: number # OPTIONAL — avg monthly revenue ($)
27	monthly_clicks: number # OPTIONAL — avg monthly clicks
28	niche: string # OPTIONAL — product category
29	status: string # OPTIONAL — "active" \| "paused" \| "new" \| "considering"
30
31	goal: string # OPTIONAL — "maximize_revenue" \| "diversify"
32	# \| "reduce_risk" \| "find_gaps"
33	# Default: "maximize_revenue"
34
35	budget_hours: number # OPTIONAL — weekly hours available for content
36	# Default: 10
37	```
38
39	Chaining context: If S1 program research or S6.3 performance data exists in conversation, pull program details and metrics automatically.
40
41	## Workflow
42
43	### Step 1: Build Portfolio Overview
44
45	Compile all programs into a dashboard:
46	- Program name, niche, commission type, commission value
47	- Monthly revenue, clicks, EPC
48	- Status (active/paused/new)
49	- Revenue share (% of total)
50
51	### Step 2: Calculate Per-Program Metrics
52
53	For each program with data:
54	- EPC: revenue / clicks
55	- Revenue Share: program revenue / total revenue × 100
56	- Effort-to-Revenue Ratio: estimated hours spent / revenue generated
57	- Commission Quality Score: recurring > one-time > per-lead > per-click
58
59	### Step 3: Apply Portfolio Analysis
60
61	Concentration Risk:
62	- If top program > 50% of revenue → HIGH RISK
63	- If top 2 programs > 80% → MODERATE RISK
64	- If no program > 30% → WELL DIVERSIFIED
65
66	Niche Overlap:
67	- Multiple programs in same niche → competing for same audience
68	- Different niches → healthy diversification
69
70	Revenue Stability:
71	- Recurring commissions → stable
72	- One-time commissions → volatile (need constant new traffic)
73
74	### Step 4: Generate Recommendations
75
76	For each program, assign an action:
77	- Double Down: High EPC, room to grow → create more content, scale traffic
78	- Maintain: Solid performer, no changes needed → keep existing content fresh
79	- Optimize: High traffic but low conversion → improve CTAs, landing pages, test variants
80	- Phase Out: Low EPC, low growth potential → redirect effort to better programs
81	- Add: Gap identified → research new programs with S1
82
83	### Step 5: Create Action Plan
84
85	Based on `budget_hours`, allocate weekly time:
86	- Double-down programs get 50% of time
87	- Maintain programs get 20%
88	- Optimize programs get 20%
89	- New program research gets 10%
90
91	Provide specific weekly tasks tied to Affitor skills.
92
93	### Step 6: Self-Validation
94
95	Before presenting output, verify:
96
97	- [ ] Revenue share percentages sum to ~100%
98	- [ ] EPC calculations correct (revenue ÷ clicks per program)
99	- [ ] Concentration risk accurate (flag if top program >50% of revenue)
100	- [ ] Actions match performance: double_down (Star), maintain (Cash Cow), optimize (Question Mark), phase_out (Dog)
101	- [ ] Weekly time allocation sums to user's st

People who liked this also viewed

6 picks

Type