bundles/sales/skills/traffic-validator/SKILL.md
Validate traffic strategy against Traffic Secrets principles. Assess Dream 100, Work In vs. Buy In, traffic temperature, and audience ownership. Activates for "validate my traffic plan" or traffic assessment questions.
npx skillsauth add shipshitdev/library traffic-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Assess traffic strategy against Traffic Secrets principles. Expose scattered traffic efforts and unclear audience strategy.
Brunson's Principle: "Your customers are already congregating. Find the watering holes."
Dream 100 → Work In or Buy In → Hook → Funnel → Own the Audience
| Dimension | Weight | What It Measures | |-----------|--------|------------------| | Dream 100 Clarity | 2x | Do you know where audience congregates? | | Hook Strategy | 1.5x | Are you interrupting the scroll? | | Work In vs. Buy In | 1.5x | Is approach clear and appropriate? | | Funnel Alignment | 1.5x | Does traffic match funnel temperature? | | Audience Ownership | 1.5x | Are you building owned audience? | | Conversion Path | 1x | Is traffic turning into customers? |
Max Score: 100 points
| Score | Rating | Verdict | |-------|--------|---------| | 85-100 | Traffic Machine | Scale and optimize | | 70-84 | Good Foundation | Address weak points | | 55-69 | Needs Work | Fix before scaling | | 40-54 | Scattered | Consolidate and focus | | 0-39 | No Strategy | Start from scratch |
| Temp | They Know | Appropriate Funnel | |------|-----------|-------------------| | Cold | Nothing | Lead magnet, free content | | Warm | Problem + solution | Tripwire, webinar | | Hot | Ready to buy | Sales page, booking |
| Skill | When to Use |
|-------|-------------|
| traffic-architect | Design strategy from scratch |
| channel-validator | Validate channel focus |
| funnel-validator | Validate funnel matches traffic |
| copy-validator | Validate hooks |
For detailed scoring criteria, output templates, and complete examples: Load ${CLAUDE_SKILL_DIR}/references/full-guide.md when the user asks for full scoring breakdowns, output templates, or worked examples.
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.