Install
$ agentstack add skill-jpeslar1-john-peslar-ai-skills-sales-funnel-systems-auditor ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Sales Funnel Systems Auditor
Use this skill to diagnose a funnel as an operating system, not a pile of tactics. Focus on the path from attention to trust to conversion to delivery to referrals.
Core Principle
Most founder-led funnels do not have a traffic problem first. They have a sales-system problem:
- The offer ladder is unclear.
- Too many CTAs compete for the same buyer.
- Nurture does not route by buyer state.
- Pipeline truth is not visible.
- Sales activity depends on the owner's memory, mood, and spare time.
- Proof from delivery is not packaged back into acquisition.
The goal is to turn the funnel into a visible, measurable, repeatable system.
Audit Workflow
- Map the funnel
- Top-of-funnel channels
- Lead capture assets
- Owned audience
- Trust-building surfaces
- Conversion events
- Offers
- Delivery experience
- Upsells, referrals, reactivation
- Identify buyer states
- Curious learner
- Problem-aware lead
- Ready-to-build operator
- Ready-to-outsource buyer
- Existing customer
- Referral source
- Score the funnel
Use a 1-10 score across:
- Target market clarity
- Message clarity
- Media/channel fit
- Lead capture
- Nurture and segmentation
- Conversion mechanism
- Delivery experience
- Lifetime value path
- Referral system
- Pipeline visibility
- Find the leaks
Look especially for:
- CTA overload
- Traffic sent to the wrong offer
- Lead magnets that do not imply the paid offer
- Newsletter/community nurture with no clear ascension path
- Webinars with weak follow-up
- Launches without opens/clicks/replies/deposits tracked
- Offers that mix DIY, DWY, and DFY without routing logic
- Fake-full pipeline, stale leads, or no qualification criteria
- Design the routing matrix
Every warm lead should have one obvious next step based on current state.
- Recommend the operating cadence
Include weekly review, dashboard metrics, follow-up rules, proof capture, and referral prompts.
Will Barron Source Lens
This skill is partly based on public sales-system lessons from Will Barron and his YouTube channel, @wbarron. Barron is the founder of Salesman.com / Salesman.org and publicly positions his work around coaching 2,000+ business owners and salespeople to large cumulative revenue outcomes. His strongest YouTube content repeatedly diagnoses the same problem in service businesses: the owner does not need more random tactics first; they need a visible, measurable sales system that does not live only in the founder's head.
Why trust this lens:
- His public positioning claims 2,000+ coached business owners and salespeople, plus large cumulative revenue outcomes.
- His best-performing videos center on practical sales-system problems: fake-full pipeline, inconsistent follow-up, feast/famine revenue, owner bottlenecks, and simple sales processes.
- The ideas are directly useful for founder-led funnels, bootcamps, DFY services, communities, and AI SDR offers because they focus on operationalizing sales behavior rather than adding more top-of-funnel noise.
- This skill is not affiliated with or endorsed by Will Barron or Salesman.com. Use the lens as a practical diagnostic pattern, not as a claim of partnership.
Barron-Style Sales System Lens
Use this diagnostic when the user has founder-led sales, a service offer, a bootcamp, a coaching offer, or a DFY/DWY implementation offer.
The repeated pattern:
- The enemy is not low motivation or bad tools. The enemy is a sales process living in the owner's head.
- A clean pipeline beats a fake-full pipeline.
- More leads into a broken sales system just leaks faster.
- The buyer is buying the bridge from painful current reality to desired future reality.
- A simple sales system has four jobs:
- Find someone with a problem you can solve.
- Help them see you can solve it.
- Make the ROI concrete.
- Ask for the business.
- The owner must build the system, make it measurable, install the operator/team layer, and keep improving the bottleneck.
Do not overcomplicate this into a 20-tool stack unless the current stage requires it.
Offer Ladder Rules
When a business has multiple products, communities, cohorts, services, and software offers, simplify the ladder:
| Buyer state | Best offer type | |---|---| | Wants to learn | Free content, newsletter, free community | | Wants roadmap and unblocking | Paid community or membership | | Wants one specific outcome built with them | Bootcamp, cohort, DWY implementation | | Wants outcome without touching the work | DFY managed service | | Already has the workflow and needs tooling | SaaS product | | Bought and won | Upsell, testimonial, referral |
Do not pitch every offer at once. Pick one primary CTA per campaign.
Drip Sequence Rules
For bootcamp, cohort, webinar, or managed-offer campaigns:
- Start with diagnosis before pitching.
- Name the painful current state.
- Show the cost of staying stuck.
- Prove the mechanism.
- Reveal the offer as the implementation container.
- Split Build With Us vs We Run It when both DWY and DFY exist.
- Use proof before urgency.
- Track replies and clicks as pipeline stages.
- Close with a binary future, not generic scarcity.
Useful drip structure:
| Email | Beat | |---:|---| | 1 | Pitch warning + diagnostic hook | | 2 | The real bottleneck | | 3 | Pipeline truth / hidden leak | | 4 | Current reality to future reality | | 5 | Proof or case study | | 6 | Offer reveal | | 7 | Value stack and routing options | | 8 | Objection handling | | 9 | Guarantee / proof / urgency | | 10 | Final binary close |
Output Format
**TLDR**
[direct diagnosis]
**Funnel Map**
| Stage | Current Assets | Job | Leak |
|---|---|---|---|
**Funnel Score**
[score]/10
**Main Leaks**
1. ...
2. ...
3. ...
**Routing Matrix**
| Buyer State | Signal | Next Step | Offer |
|---|---|---|---|
**Offer Ladder**
[recommended ladder from free to premium]
**Drip / Nurture Fix**
[sequence or campaign changes]
**Metrics Dashboard**
- ...
**Next 7 Days**
1. ...
2. ...
3. ...
Rules
- Lead with the leak, not a generic marketing summary.
- Separate traffic problems from conversion-system problems.
- Give one primary money move.
- Make CTAs state-based.
- Include proof capture and referral systems.
- Prefer simple dashboards before complex CRM automation.
- Do not recommend more content, more ads, or more lead magnets until the sales path can handle them.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jpeslar1
- Source: jpeslar1/john-peslar-ai-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.