bundles/branding/skills/expert-validator/SKILL.md
Validate positioning, authority, and messaging strategy using Expert Secrets principles. Assess Attractive Character, Big Domino, and New Opportunity framing. Activates for "validate my positioning" or authority assessment.
npx skillsauth add shipshitdev/library expert-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 positioning, authority, and messaging against Expert Secrets principles. Expose weak positioning that makes people look like everyone else.
Brunson's Principle: "You don't need to be the most qualified—you need to be the most positioned."
Attractive Character → Epiphany Bridge → Big Domino → New Opportunity
| Dimension | Weight | What It Measures | |-----------|--------|------------------| | Attractive Character | 2x | Is there a compelling persona/story? | | Origin Story | 1.5x | Is there a powerful epiphany bridge? | | Big Domino | 2x | Is there one core belief to shift? | | New Opportunity | 1.5x | Is it framed as new vs. improvement? | | Authority Signals | 1x | Are credentials/proof established? | | Differentiation | 1x | Do they stand out from competitors? |
Max Score: 100 points
| Score | Rating | Verdict | |-------|--------|---------| | 85-100 | Expert Positioned | Refine and scale | | 70-84 | Good Foundation | Strengthen weak areas | | 55-69 | Needs Work | Clarify before scaling | | 40-54 | Commodity Zone | Major repositioning needed | | 0-39 | Invisible | Start from scratch |
| Type | Description | Example | |------|-------------|---------| | Leader | "Follow me, I'll show you" | Coaches, gurus | | Adventurer | "Join me on this journey" | Explorers, testers | | Reporter | "I researched this for you" | Curators, analysts | | Reluctant Hero | "I didn't want to, but..." | Accidental experts |
"If I can get them to believe [ONE THING], then all other objections become irrelevant."
| Improvement (Weak) | New Opportunity (Strong) | |-------------------|-------------------------| | "Better marketing" | "A new way to get customers" | | "Faster results" | "A different approach entirely" | | "We're like X but better" | "Skip the old method" |
| Skill | When to Use |
|-------|-------------|
| expert-architect | Build positioning from scratch |
| copy-validator | Validate positioning translates to copy |
| offer-validator | Validate offer matches positioning |
For detailed scoring criteria, output templates, and complete examples: references/full-guide.md
development
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
development
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
development
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
tools
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.