SkillAgentSearch skills...

funnel-architect

Design or restructure a marketing funnel matched to the business model — stage architecture with entry/exit criteria and KPIs, a customer journey map with emotions and friction points, gap analysis, an attribution model recommendation, and a 30/60/90 optimization roadmap.

Install / Use

npx skills add indranilbanerjee/digital-marketing-pro --skill funnel-architect

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Our assessment of funnel-architect

funnel-architect scores 85/100 on our quality scale, 50th of 90 Product Management skills we index.

Its SKILL.md is 15 KB long, well organised into 16 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 832 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 26 days ago, so funnel-architect is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

funnel-architect compared with similar skills

All 4 of these similar skills score higher than funnel-architect; compare them before choosing.

SkillScoreStarsUpdatedFormat
funnel-architect (this skill)by indranilbanerjee8583226d agoSKILL.md
Agent-Reachby Panniantong10090.1k18d agoCLAUDE.md
algorithmic-artby anthropics100177.9k11d agoSKILL.md
pptxby anthropics100177.9k11d agoSKILL.md
designby nextlevelbuilder100130.2k12d agoSKILL.md

Frequently asked questions

How do I install funnel-architect?
Run npx skills add indranilbanerjee/digital-marketing-pro --skill funnel-architect. The install tabs above show the steps for each supported agent.
Which AI agents does funnel-architect work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is funnel-architect safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is funnel-architect still maintained?
The repository was last updated 26 days ago, so funnel-architect is actively maintained.

name: funnel-architect description: "Design or restructure a marketing funnel matched to the business model — stage architecture with entry/exit criteria and KPIs, a customer journey map with emotions and friction points, gap analysis, an attribution model recommendation, and a 30/60/90 optimization roadmap. Plans and diagnoses; does not execute campaigns. Triggers on "/digital-marketing-pro:funnel-architect", "map our customer journey", "which attribution model should we use", "where are we losing customers", "design a funnel for our SaaS". Reads the brand profile, industry benchmarks, and campaign history; pairs with /digital-marketing-pro:funnel-audit for data-driven diagnosis."

Funnel Architect

When to Use This Skill

Activate this module when the user's request involves any of the following:

  • Funnel Design: Building or restructuring a marketing/sales funnel for a specific business model
  • Customer Journey Mapping: Visualizing the end-to-end path from first awareness to post-purchase advocacy
  • Attribution Modeling: Determining how credit for conversions should be assigned across touchpoints
  • Funnel Analysis: Diagnosing where prospects drop off and why
  • Conversion Path Optimization: Improving the sequence of interactions that lead to conversion
  • Gap Analysis: Identifying missing stages, touchpoints, or content in an existing funnel
  • Micro-Conversion Strategy: Defining and optimizing the small commitments that lead to macro conversions

Trigger phrases: "funnel," "customer journey," "attribution," "conversion path," "where are we losing customers," "buyer journey," "TOFU/MOFU/BOFU," "lead nurture flow," "drop-off analysis," "touchpoint mapping," "pipeline," "conversion rate by stage"

Brand Context (Auto-Applied)

Before producing any marketing output from this module:

  1. Check session context — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.
  2. If you need the full profile, read: ~/.claude-marketing/brands/{slug}/profile.json
  3. Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
  4. Check compliance — Auto-apply rules for brand's target_markets and industry using skills/context-engine/compliance-rules.md
  5. Reference industry benchmarks — Consult skills/context-engine/industry-profiles.md for the brand's industry
  6. Use platform specs — Reference skills/context-engine/platform-specs.md for character limits and format requirements
  7. Check campaign history — Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns before planning new work
  8. If no brand exists, say: "No brand profile found. Use /digital-marketing-pro:brand-setup to create one, or I can proceed with general best practices."
  9. Check brand guidelines — If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load and enforce: restrictions.md for banned words, restricted claims, and mandatory disclaimers; channel-styles.md for channel-specific tone overrides (may differ from base voice); messaging.md for approved key messages, taglines, and positioning language; voice-and-tone.md for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.

Do not ask the user for information that already exists in their brand profile.

Required Context

Before executing funnel work, gather:

  1. Business Model: SaaS, e-commerce, lead gen, marketplace, subscription, service-based, hybrid, etc.
  2. Current Funnel State: Does a documented funnel exist? What stages are defined? What tools track it?
  3. Revenue Model: How the business makes money (subscription, one-time purchase, freemium, etc.)
  4. Average Deal Size & Sales Cycle Length: Critical for determining funnel complexity
  5. Key Conversion Actions: What counts as a lead, MQL, SQL, opportunity, customer?
  6. Current Metrics: Conversion rates between stages if available
  7. Tech Stack: CRM, marketing automation, analytics platforms in use
  8. Team Structure: Is there a separate sales team? Is it product-led growth? Who owns each funnel stage?

If the user cannot provide all context, use the business model to apply sensible defaults and note assumptions.

Minimum viable context: Business model and what the company sells. Everything else can be inferred from these two inputs and refined as more information surfaces.

Capabilities

  • Business-Model-Adaptive Funnel Design: Custom funnel architectures for 7 distinct business models (B2B SaaS, eCommerce/DTC, B2B services/consulting, local business, marketplace, creator/personal brand, non-profit)
  • Journey Mapping with Emotion & Friction Points: Visual journey maps that capture not just touchpoints but emotional states, friction moments, and decision triggers at each stage
  • Attribution Model Selection & Design: Guidance on choosing the right attribution model (last-click, first-click, linear, time-decay, position-based, data-driven, custom) based on business context
  • Funnel Templates: Pre-built, customizable funnel frameworks for 7 business models with default stages, KPIs, and conversion benchmarks
  • Gap Analysis: Systematic identification of missing stages, content, touchpoints, or automation in an existing funnel
  • Micro-Conversion Definition: Identifying and sequencing the small commitment actions that build toward macro conversion
  • Stage-by-Stage KPI Framework: Defining the right metrics for every funnel stage so performance is measurable
  • Funnel Velocity Analysis: Measuring how quickly prospects move through stages and identifying bottlenecks
  • Multi-Touch Journey Orchestration: Designing coordinated touchpoint sequences across channels
  • Post-Purchase Funnel Extension: Retention, expansion, and advocacy stage design

Process

Primary Workflow: Funnel Design & Optimization

  1. Business Model Classification

    • Identify the business model (or hybrid combination)
    • Determine the revenue model and typical sales cycle
    • Classify as product-led, sales-led, or hybrid growth motion
    • Select the appropriate funnel template as a starting framework
  2. Current State Assessment

    • If an existing funnel is documented, map it stage by stage
    • Identify what metrics are currently tracked at each stage
    • Note where tracking breaks down or data goes dark
    • Document all current touchpoints (ads, content, emails, sales calls, product interactions)
  3. Journey Mapping

    • Map the full customer journey from unaware to advocate
    • For each stage, document:
      • Touchpoints: What the prospect interacts with
      • Actions: What they do (micro-conversions)
      • Emotions: What they feel (excitement, confusion, hesitation, trust)
      • Friction Points: What slows them down or causes drop-off
      • Decision Triggers: What moves them to the next stage
      • Content Needs: What information they need at this moment
    • Include parallel paths (not all journeys are linear)
  4. Gap Analysis

    • Compare current state against the ideal funnel for this business model
    • Identify missing stages or undefined transitions
    • Flag content gaps (stages with no supporting content)
    • Highlight automation gaps (manual handoffs that should be automated)
    • Detect measurement gaps (stages with no KPIs)
    • Spot channel gaps (stages served by only one channel)
  5. Funnel Architecture Design

    • Define each stage with clear entry/exit criteria
    • Assign KPIs and conversion benchmarks to every stage
    • Design the micro-conversion sequence
    • Map content to each stage (existing and needed)
    • Specify automation triggers and rules
    • Define handoff protocols between marketing and sales (if applicable)
  6. Attribution Model Recommendation

    • Based on funnel complexity, sales cycle length, and available data, recommend an attribution model
    • Explain trade-offs of the recommendation vs. alternatives
    • Provide implementation guidance for their tech stack
  7. Optimization Roadmap

    • Prioritize improvements by impact and effort
    • Define A/B testing plan for high-impact stage transitions
    • Set up monitoring cadence for funnel health metrics
    • Create a 30/60/90-day optimization plan

Secondary Workflow: Funnel Diagnosis (When a Funnel Exists but Underperforms)

  1. Data Collection

    • Gather conversion rates between every stage for the last 3-6 months
    • Pull time-to-conversion data (how long prospects spend at each stage)
    • Identify volume at each stage to build the full funnel waterfall
  2. Drop-Off Analysis

    • Calculate the absolute and relative drop-off at each stage transition
    • Identify the single largest drop-off point (the "leaky bucket")
    • Segment drop-off by traffic source, device, geography, and audience segment
    • Determine if drop-off is a volume problem (not enough enter the stage) or a conversion problem (they enter but don't advance)
  3. Root Cause Identification

    • For each high-drop-off transition, investigate:
      • Is the content at this stage compelling enough?
      • Is the CTA clear and the next step obvious?
      • Is there a friction point (long forms, confusing UX, required info the prospect does not have)?
      • Is the timing wrong (asking for too much too early)?
      • Is there a trust gap (insufficient social proof or credibility at this stage)?
    • Cross-reference with qualitative data (customer feedback, sales team input, session recordings) if available
  4. Fix Prioritization

    • Score each identified issue on impact (how much conversion improvement is possible) and effort (how hard is the fix)
    • Focus on the highest-impact, lowest-effort fixes first
    • Design specific experiments to test each fix before full rollout

Reference Files

  • journey-mapping.md — Customer journey mapping methodology, emotion mapping framework, touchpoint cataloging, and journey visualization templates
  • attribution-models.md — Detailed comparison of attribution models, selection criteria decision tree, implementation guides per platform, and custom model design
  • funnel-templates.md — Pre-built funnel architectures for 7 business models with default stages, benchmarks, and customization guides
  • gap-analysis.md — Gap analysis framework, diagnostic questions, common gap patterns by business model, and prioritization scoring
  • sales-marketing-alignment.md — Sales-marketing alignment frameworks, lead handoff definitions (MQL/SQL), SLA design, and funnel-stage ownership mapping

Output Formats

| Deliverable | Format | Description | |---|---|---| | Funnel Architecture | Visual diagram + document | Stage-by-stage funnel with entry/exit criteria, KPIs, and content mapping | | Customer Journey Map | Visual map + narrative | Full journey from awareness to advocacy with emotions, friction, and triggers | | Gap Analysis Report | Document with priorities | All identified gaps with severity, impact score, and fix recommendations | | Attribution Model Spec | Document | Recommended model with rationale, alternatives, and implementation steps | | Stage KPI Dashboard | Table/spreadsheet spec | Metrics, benchmarks, and tracking methodology for every funnel stage | | Micro-Conversion Map | Diagram + document | Sequenced small-commitment actions that build toward macro conversions | | Funnel Optimization Roadmap | Prioritized plan | 30/60/90-day plan with specific actions, owners, and expected impact |

Edge Cases

Hybrid Business Models

  • Situation: Business combines multiple models (e.g., SaaS with a marketplace component, or e-commerce with subscription)
  • **Appro

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars832
CategoryProduct
Updated26d ago
Forks136

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions