shipshitdev/execution-validator
bundles/startup/skills/execution-validator/SKILL.md
Use this skill when users need to validate a launch plan, assess MVP scope, or determine if they're ready to execute. Activates for "validate my plan," "am I ready to launch," "is my scope too big," or when assessing action readiness.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library execution-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:45 AM110.2s1 file scanned
SKILL.md
- name:
- execution-validator
- description:
- Use this skill when users need to validate a launch plan, assess MVP scope, or determine if they're ready to execute. Activates for "validate my plan," "am I ready to launch," "is my scope too big," or when assessing action readiness.
- version:
- 1.0.0
- tags:
- business, hormozi, validation, execution, speed, mvp, launch, action
Execution Validator - Hormozi Speed Scorecard
Overview
Assess whether someone is ready to take action, if their scope is appropriate, and if they're building excuses or building businesses.
Hormozi's Core Principle: "Speed is the only competitive advantage that matters early on."
When This Activates
- "validate my plan" / "am I ready to launch"
- "is my scope too big"
- "should I do X or Y first"
- "I'm still planning" / "I'm not ready yet"
- Been "working on something" for months
- Stuck in analysis paralysis
The Framework: Speed Scorecard
Core Questions:
- What's the fastest path to first customer?
- What can you cut and still test the core assumption?
- What are you waiting for that doesn't matter?
Scoring Dimensions (5 total):
| Dimension | Weight | What It Measures | |-----------|--------|------------------| | Action Bias | 2x | Taking action or planning? | | Scope Minimalism | 2x | Tight or bloated scope? | | Decision Clarity | 1.5x | Decisions made or pending? | | Time to First Value | 2x | How fast to first customer? | | Excuse Detection | 1.5x | Real blockers or fear? |
Max Score: 100 points
Rating Scale
| Score | Rating | Verdict | |-------|--------|---------| | 85-100 | Ready to Execute | Stop planning. Execute now. | | 70-84 | Almost Ready | Minor adjustments, then go. | | 55-69 | Needs Work | Cut scope, make decisions, move faster. | | 40-54 | Stuck | Major mindset/scope issues. | | 0-39 | Analysis Paralysis | One week sprint to launch. |
Hormozi Gut Checks
If you had a gun to your head and had to make money from this in 7 days, what would you do?
If you could only build ONE thing and charge for it tomorrow, what would it be?
If someone offered you $1M to launch in 7 days, could you do it? If yes, your "blockers" are excuses.
Common Excuses Disguised as Blockers
| Excuse | Reality | |--------|---------| | "I need to learn more" | You learn by doing | | "The market isn't ready" | You haven't tested | | "I need more funding" | Start smaller | | "I need a co-founder" | Start solo first | | "I need to finish [feature]" | Launch without it | | "Perfect timing" | There is no perfect timing |
Integration
| Skill | When to Use |
|-------|-------------|
| mvp-architect | Scope the minimum viable product |
| offer-validator | Validate the offer before launch |
| business-model-auditor | After launch, assess scalability |
For complete scoring criteria for all 5 dimensions, red flags for each dimension, decision framework, first value framework, output format template, one week sprint plan template, example validations, and scope surgery guidance, see: references/full-guide.md
Related Skills
shipshitdev/weekly-review
development
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
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.
35SKILL.mdUpdated Aug 31, 2026