Funnel Planner

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2515ce9634da · 15 Oct 2026Report an issue or request a re-scan

• PublisherAffitor GitHub organizationOwner of the repository this skill is read from
• Source folderAffitor/affiliate-skills/skills/meta/funnel-plannerThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict2515ce9634daA new audit runs when the source changes
• Repository statusNot archivedLast push 2 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: funnel-planner
description: >
  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 together", "build my funnel",
  "affiliate marketing roadmap", "step by step affiliate plan", "onboarding plan".
license: MIT
version: "1.0.0"
tags: ["affiliate-marketing", "meta", "planning", "compliance", "funnel", "strategy"]
compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent"
metadata:
  author: affitor
  version: "1.0"
  stage: S8-Meta
---

# Funnel Planner

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.

## Stage

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.

## When to Use

- User is starting from scratch and wants a complete plan
- User asks "how do I start affiliate marketing?"
- User has a niche but no strategy
- User wants to know which skills to use and in what order
- User says "build me a funnel" or "plan my affiliate business"
- User wants a week-by-week roadmap
- Chaining: this skill recommends which other skills to run and in what order

## Input Schema

```yaml
niche: string                  # OPTIONAL — e.g., "AI tools", "fitness supplements"
                               # If not provided, S1 research will help identify one

product: string                # OPTIONAL — specific product if already chosen
                               # e.g., "HeyGen" or "Semrush"

experience_level: string       # OPTIONAL — "beginner" | "intermediate" | "advanced"
                               # Default: "beginner"

available_channels:            # OPTIONAL — platforms the user can use
  - string                     # e.g., ["blog", "twitter", "linkedin", "email"]
                               # Default: ["blog", "twitter"]

weekly_hours: number           # OPTIONAL — hours per week available
                               # Default: 5

goal: string                   # OPTIONAL — "first_commission" | "scale_to_1k" | "scale_to_10k"
                               # Default: "first_commission"
```

**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.

## Workflow

### Step 1: Assess Starting Point

Determine where the user is:
- **Has nothing**: Start from S1 (full funnel)
- **Has a product**: Skip S1, start from S2
- **Has content**: Skip S1-S2, start from S3 or S4
- **Has traffic**: Skip to S6 (analytics) or S7 (automation)

Ask clarifying questions only if truly ambiguous. Default to the most common case (beginner, starting from scratch).

### Step 2: Select Relevant Skills

Based on channels, experience, and goal, select 5-8 skills from S1-S7:
- **Beginner + blog + twitter**: S1 → S2 (viral-post-writer) → S3 (affiliate-blog-builder) → S5 (bio-link-deployer) → S6 (seo-audit)
- **Intermediate + email + blog**: S1 → S3 → S4 (landing-page-creator) → S5 (email-drip-sequence) → S6 (performance-report) → S7 (content-repurposer)
- **Advanced + all channels**: Full S1-S7 pipeline with S8 (compliance-checker) at each content step

### Step 3: Estimate Effort

For each selected skill, estimate time based on experience level:
- Beginner: 2-4 hours per skill
- Intermediate: 1-2 hours per skill
- Advanced: 30-60 minutes per skill

Fit into the user's `weekly_hours` to create a week-by-week schedule.

### Step 4: Create Roadmap

Build a week-by-week table:
- Week number
- Skill to run
- What it produces
- Time estimate
- Exact prompt to invoke the skill

### Step 5: Add Success Metrics

For each phase, define measurable outcomes:
- S1: "You should have 2-3 programs selected"
- S2: "You should have 5+ social posts ready"
- S3: "You should have 1-2 blog posts published"
- S5: "You should have a bio link page live"
- S6: "You should know your EPC and conversion rate"

### Step 6: Self-Validation

Before presenting output, verify:

- [ ] Roadmap follows logical sequence (S1→S2→S3... not random order)
- [ ] Invocation prompts are copy-paste ready for each skill
- [ ] Time estimates realistic for stated experience level
- [ ] Success metrics are measurable and specific (not "do well")
- [ ] Total weeks feasible given user's weekly hours budget

If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.

## Output Schema

```yaml
output_schema_version: "1.0.0"  # Semver — bump major on breaking changes
plan:
  niche: string
  product: string
  experience: string
  goal: string
  total_weeks: number
  total_skills: number

roadmap:
  - week: number
    skill: string              # skill slug
    stage: string              # e.g., "S1: Research"
    action: string             # what to do this week
    time_estimate: string      # e.g., "2-3 hours"
    invocation_prompt: string  # exact prompt to give your AI agent
    success_metric: string     # how to know this step is done

milestones:
  - week: number
    name: string               # e.g., "First content published"
    description: string
```

## Output Format

1. **Plan Overview** — niche, goal, timeline, total skills
2. **Week-by-Week Roadmap** — table with week, skill, action, time, and prompt
3. **Milestones** — key checkpoints with expected outcomes
4. **Entry Points** — where to jump in if user is not starting from scratch

## Error Handling

- **No niche or product

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-15
   ✓SAFE B 89 / 100

   first audit · source 2515ce9634da

Questions about Funnel Planner

• github.com/Affitor/affiliate-skills/tree/main/skills/meta/funnel — the audited source at commit 2515ce9634da and every finding aboveObserved · 15 Oct 2026

Spotted something wrong? Report a correction · Methodology