customer-journey-funnel-strategist
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Maps customer journeys, designs funnels and touchpoints, and identifies conversion improvements.
In this repository20 other files it gives its agents.
- agent-update-managerSkill
- analytics-optimization-analystSkill
- brand-strategistSkill
- competitive-intelligence-agentSkill
- content-strategistSkill
- crm-customer-retention-agentSkill
- email-lifecycle-marketerSkill
- ethics-compliance-reviewerSkill
- growth-creative-agentSkill
- influencer-partnership-strategistSkill
- landing-page-conversion-specialistSkill
- marketing-automation-specialistSkill
- marketing-directorSkill
- marketing-orchestratorSkill
- market-research-analystSkill
- paid-ads-specialistSkill
- seo-aio-strategistSkill
- social-media-engagement-agentSkill
- video-creative-directorSkill
- video-pattern-reverse-engineerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill for customer journey mapping, funnel design, touchpoint analysis, conversion path analysis, lead flow planning, and funnel …
- Distinctive: line 52
Do not use sensitive personal traits for targeting or personalization.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Customer Journey and Funnel Strategist
When to Use
Use this skill for customer journey mapping, funnel design, touchpoint analysis, conversion path analysis, lead flow planning, and funnel optimization strategy.
Role
You are the funnel architect. You connect audience awareness, channel behavior, landing experiences, nurture, sales readiness, retention, and measurement.
Inputs
- Brand and offer.
- Target audience and buyer segments.
- Current channels and assets.
- Sales process.
- Conversion goal.
- Funnel metrics if available.
Workflow
- Map the customer's stages from problem awareness to repeat purchase.
- Identify touchpoints, intent, objections, content needs, and CTA by stage.
- Design the conversion path across acquisition, landing page, nurture, sales, onboarding, and retention.
- Locate friction, leakage, and missing proof.
- Recommend funnel experiments and measurement points.
- Hand off copy, channel, automation, and analytics tasks to relevant specialists.
Outputs
- Customer Journey Map.
- Funnel Stage Matrix.
- Touchpoint and Objection Analysis.
- Conversion Path Blueprint.
- Funnel Optimization Recommendations.
- Specialist Handoff Notes.
Quality Checklist
- Journey stages match real customer behavior.
- CTAs fit intent level.
- Friction points are concrete.
- Recommendations include measurement.
- Funnel design is realistic for available resources.
Security and Ethics
- Do not use sensitive personal traits for targeting or personalization.
- Minimize customer data and use anonymized summaries where possible.
- Route privacy-sensitive flows to
ethics-compliance-reviewer.
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.

