funnel-architect
Skill0 starsChanged 9 months agoMITView on GitHub
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.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- vikneshwaran16032005-alt/claude-skillstheir own version, first seen Nov 1, 2026
- indranilbanerjee/digital-marketing-proedited, first seen Feb 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- indranilbanerjee/digital-marketing-pro★ 93494% same
Wrote their own version · 1
- vikneshwaran16032005-alt/claude-skills★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository163 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- ad-creativeSkill
- add-integrationSkill
- aeo-auditSkill
- aeo-geoSkill
- agency-dashboardSkill
- analytics-insightsSkill
- anomaly-scanSkill
- attribution-modelSkill
- attribution-reportSkill
- audience-intelligenceSkill
- audience-profileSkill
- autopilot-statusSkill
- backlink-gapSkill
- brand-setupSkill
- budget-optimizerSkill
- budget-trackerSkill
- c2pa-metadataSkill
- campaign-auditSkill
- campaign-orchestratorSkill
- campaign-planSkill
- campaign-statusSkill
- case-study-planSkill
- checkSkill
- churn-riskSkill
- client-onboardingSkill
- client-proposalSkill
- client-reportSkill
- client-validation-documentSkill
- cohort-analysisSkill
- competitor-alertsSkill
- competitor-analysisSkill
- competitor-monitorSkill
- competitor-pagesSkill
- connectSkill
- content-briefSkill
- content-calendarSkill
- content-decay-scanSkill
- content-engineSkill
- content-repurposeSkill
- context-engineSkill
- continuous-improvement-loopSkill
- counter-narrativeSkill
- cowork-setupSkill
- creative-healthSkill
- creative-testing-frameworkSkill
- credential-switchSkill
- crisis-responseSkill
- crm-syncSkill
- croSkill
- dark-funnelSkill
- data-exportSkill
- data-importSkill
- digital-prSkill
- email-sequenceSkill
- emerging-channelsSkill
- engagement-workflowSkill
- entity-auditSkill
- eval-configSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Before producing any marketing output from this module:
- Distinctive: line 36
Do not ask the user for information that already exists in their brand profile.
- Distinctive: line 40
Before executing funnel work, gather:
- Distinctive: line 51
If the user cannot provide all context, use the business model to apply sensible defaults and note assumptions.
- Distinctive: line 79
If an existing funnel is documented, map it stage by stage
- Distinctive: line 82
Document all current touchpoints (ads, content, emails, sales calls, product interactions)
- Very specific: line 120
Create a 30/60/90-day optimization plan
- Distinctive: line 181
Approach: Create explicit "dark funnel" stages where tracking is limited.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- 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.
- If you need the full profile, read:
~/.claude-marketing/brands/{slug}/profile.json - Apply brand voice — Formality, energy, humor, authority levels must shape all content tone and word choices
- Check compliance — Auto-apply rules for brand's target_markets and industry using
skills/context-engine/compliance-rules.md - Reference industry benchmarks — Consult
skills/context-engine/industry-profiles.mdfor the brand's industry - Use platform specs — Reference
skills/context-engine/platform-specs.mdfor character limits and format requirements - Check campaign history — Run
python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaignsbefore planning new work - 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."
- Check brand guidelines — If
~/.claude-marketing/brands/{slug}/guidelines/_manifest.jsonexists, load and enforce:restrictions.mdfor banned words, restricted claims, and mandatory disclaimers;channel-styles.mdfor channel-specific tone overrides (may differ from base voice);messaging.mdfor approved key messages, taglines, and positioning language;voice-and-tone.mdfor 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:
- Business Model: SaaS, e-commerce, lead gen, marketplace, subscription, service-based, hybrid, etc.
- Current Funnel State: Does a documented funnel exist? What stages are defined? What tools track it?
- Revenue Model: How the business makes money (subscription, one-time purchase, freemium, etc.)
- Average Deal Size & Sales Cycle Length: Critical for determining funnel complexity
- Key Conversion Actions: What counts as a lead, MQL, SQL, opportunity, customer?
- Current Metrics: Conversion rates between stages if available
- Tech Stack: CRM, marketing automation, analytics platforms in use
- 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
- 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
- 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)
- 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)
- 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)
- 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)
- 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
- 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)
- 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
- 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)
- 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
- For each high-drop-off transition, investigate:
- 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 templatesattribution-models.md— Detailed comparison of attribution models, selection criteria decision tree, implementation guides per platform, and custom model designfunnel-templates.md— Pre-built funnel architectures for 7 business models with default stages, benchmarks, and customization guidesgap-analysis.md— Gap analysis framework, diagnostic questions, common gap patterns by business model, and prioritization scoringsales-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)
- Approach: Build a primary funnel based on the dominant revenue model, then layer in secondary paths. Identify where the funnels diverge and converge. Create distinct stage definitions for each path but unified attribution. Do not force-fit a single template — hybrid models need hybrid funnels.
Two-Sided Marketplaces
- Situation: Business serves both supply side (sellers, providers) and demand side (buyers, consumers)
- Approach: Design parallel funnels for each side. Map interdependencies (where one side's funnel stage depends on the other side's activity). Identify the "chicken and egg" dynamics and design the funnel to solve for the constrained side first. Track marketplace liquidity metrics alongside conversion metrics.
Offline-to-Online Journeys
- Situation: Significant portion of the journey happens offline (events, retail, phone calls, field sales)
- Approach: Create explicit "dark funnel" stages where tracking is limited. Design bridge mechanisms (QR codes, unique URLs, call tracking numbers, CRM manual entry) to connect offline interactions to the digital funnel. Acknowledge measurement limitations honestly and recommend proxy metrics where direct tracking is impossible.
Very Long B2B Cycles (12+ Months)
- Situation: Enterprise sales with buying committees, RFPs, legal review, and 12-24 month cycles
- Approach: Build a milestone-based funnel rather than a time-based one. Design for buying committee dynamics (champion, economic buyer, technical evaluator, legal). Include "re-engagement" loops for stalled deals. Use account-level scoring rather than individual lead scoring. Attribution must be multi-touch with heavy time-decay weighting. Content needs are deep and stage-specific — exec summaries for C-suite, technical docs for evaluators, ROI models for finance.
Product-Led Growth (PLG) Funnels
- Situation: Product usage IS the primary funnel mechanism — users self-serve through a free tier or trial before converting
- Approach: The funnel is driven by product engagement, not traditional marketing touches. Design around activation milestones (the "aha moments" in the product). Map the progression from signup to activation to engagement to conversion to expansion. Define product-qualified leads (PQLs) based on usage thresholds rather than marketing-qualified leads. Integrate product analytics (Amplitude, Mixpanel, Pendo) as the primary funnel tracking tool. Marketing's role shifts toward driving signups and supporting activation through in-app messaging, onboarding emails, and educational content.
Funnel with No Existing Data
- Situation: New business or new market with no historical funnel data to analyze
- Approach: Build a hypothesis funnel using industry benchmarks and business model templates. Define stage conversion rate assumptions clearly and label them as hypotheses. Design the funnel with measurement baked in from day one so data accumulates quickly. Recommend a 90-day "instrument and learn" phase where the goal is data collection and assumption validation, not optimization. Set minimum traffic/volume thresholds for each stage before drawing conclusions from conversion rates.
Related Skills
- Campaign Orchestrator — For executing the campaigns that drive traffic into the funnel and move prospects through stages
- Audience Intelligence — For understanding who enters the funnel, building personas for each stage, and segmenting by funnel behavior
- Analytics & Insights — For measuring funnel performance, attribution analysis, and anomaly detection in conversion rates
- Content Engine — For creating the stage-specific content mapped to each funnel touchpoint
- AEO/GEO Intelligence — For optimizing the top-of-funnel awareness stage where AI-generated answers drive discovery
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

