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
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
tools
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
tools
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
tools
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.