shipshitdev/cofounder-evaluator
bundles/startup/skills/cofounder-evaluator/SKILL.md
Use this skill when users need to evaluate potential co-founders, assess founder compatibility, design equity splits, or navigate co-founder relationships. Activates for "should I work with this person," "co-founder fit," "equity split," or founding team questions.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library cofounder-evaluatorInstall 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 AM126.7s3 files scanned
SKILL.md
- name:
- cofounder-evaluator
- description:
- Use this skill when users need to evaluate potential co-founders, assess founder compatibility, design equity splits, or navigate co-founder relationships. Activates for "should I work with this person," "co-founder fit," "equity split," or founding team questions.
- version:
- 1.0.0
- tags:
- business, hexa, cofounder, team, equity, partnership, founding
Co-Founder Evaluator - Founding Team Assessment
Overview
Help founders make the critical decision of choosing (or validating) a co-founder using Hexa's methodology. Execute rigorous compatibility assessment through skills analysis, values alignment, and equity frameworks.
Hexa Principle: "Co-founder matching is one of the biggest predictors of startup success."
When This Activates
- "Should I work with this person"
- Finding a co-founder
- Co-founder fit/compatibility
- Equity splits
- "Do I need a co-founder"
- Co-founder conflict/concerns
- Solo vs. partnering
Evaluation Stack (Bottom Up)
- Skills Complement - What each brings
- Vision Alignment - Where you want to go
- Values Alignment - What you believe matters
- Working Style - How you collaborate daily
Solo vs. Co-founder
| Favors Solo | Favors Co-founder | |-------------|-------------------| | 80%+ skills covered | Major skill gaps | | Move fast alone | Need parallel execution | | Prefer autonomy | Value debate/input | | Strong network | Need complementary network | | Bootstrapping | Raising (investors like teams) |
5+ either way: Follow that direction
Skills Matrix
Rate 1-5 for: Technical, Sales, Marketing, Finance/Ops, Leadership, Domain, Fundraising, Recruiting
Ideal: No overlaps >4, no gaps <2
Founder Archetypes
| Type | Best Paired With | |------|------------------| | Builder | Seller or Operator | | Seller | Builder or Operator | | Operator | Builder or Seller | | Visionary | Executor |
Vision Alignment Questions
- 5-year vision?
- Company size goal?
- Exit preference ($10M vs $1B)?
- Time commitment?
Red Flag: Different answers = discuss before proceeding
Trial Period (8-12 weeks)
- Coffee chats (2-4 weeks)
- Mini project (2-4 weeks)
- Full immersion (4-8 weeks)
- Decision
Must pass: Delivered commitments, proactive communication, resolved disagreement, excited to continue
Equity Split Rules
- When in doubt: 50/50
- Always vest (4yr/1yr cliff)
- Get it in writing
| Situation | Split | |-----------|-------| | Equal contribution | 50/50 | | Idea + domain vs. execution | 55/45 - 60/40 | | Full-time vs. part-time | 60/40 - 70/30 |
Red Flags (Stop)
- History of co-founder disputes
- Different commitment levels
- Can't resolve disagreements
- Reference concerns
- Gut says no
- Unwilling to vest
The 7-10 Year Question
"Would I want to work closely with this person, through extreme stress, for 7-10 years?"
If not enthusiastic yes, keep looking.
Integration
early-hiring-advisor- Build team after foundingidea-validator- Validate idea togetherexecution-accelerator- Make the decision
For complete assessment matrices, reference questions, agreement checklist, output templates, and common mistakes, see: references/full-guide.md
Related Skills
shipshitdev/worktree
development
VerifiedTrustedCommunity
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.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
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.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
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.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
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.
27SKILL.mdUpdated Jun 13, 2026