bundles/sales/skills/channel-validator/SKILL.md
Use this skill when users need to validate their marketing channel strategy, assess channel focus, or determine lead gen priorities. Activates for "validate my channels," "am I on the right platforms," "should I focus on X or Y channel," or when assessing marketing spread.
npx skillsauth add shipshitdev/library channel-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.
Validate channel strategy against Hormozi's One Channel Rule—master one before adding more.
Core Principle: "One avatar, one channel, one offer. Master it before you add."
One Channel + One Avatar + One Offer = Mastery → Then Expand
| Dimension | Weight | What It Measures | |-----------|--------|------------------| | Channel Focus | 2x | Focused or spread thin? | | Channel Mastery | 2x | Mastered primary channel? | | Avatar Clarity | 1.5x | Crystal clear customer? | | ROI Awareness | 1.5x | Know what's working? | | Expansion Readiness | 1x | Ready for channel #2? |
Max Score: 100 points
| Score | Rating | Verdict | |-------|--------|---------| | 85-100 | Focused & Ready | Scale primary, consider expansion | | 70-84 | Good Focus | Continue mastering, don't add | | 55-69 | Needs Focus | Cut channels, double down | | 40-54 | Sprawled | Major consolidation needed | | 0-39 | Scattered | Stop everything, pick ONE |
If you could only use ONE channel for the next 6 months, which would it be?
If they struggle to answer, focus is the problem.
| Skill | When to Use |
|-------|-------------|
| lead-channel-optimizer | Optimize chosen channel |
| traffic-validator | Validate traffic strategy |
| traffic-architect | Design traffic strategy |
| offer-validator | Validate offer for channel |
For detailed scoring criteria, output templates, and mastery indicators: references/full-guide.md
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.