shipshitdev/early-hiring-advisor
bundles/startup/skills/early-hiring-advisor/SKILL.md
Use this skill when users need to make early hires, build their founding team, determine compensation/equity, decide who to hire first, or scale from founders to first employees. Activates for "who should I hire first," "early hiring," "equity for employees," or team building questions.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library early-hiring-advisorInstall 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 AM135.5s3 files scanned
SKILL.md
- name:
- early-hiring-advisor
- description:
- Use this skill when users need to make early hires, build their founding team, determine compensation/equity, decide who to hire first, or scale from founders to first employees. Activates for "who should I hire first," "early hiring," "equity for employees," or team building questions.
- version:
- 1.0.0
- tags:
- business, hexa, hiring, team, equity, compensation, startup
Early Hiring Advisor - First 10 Hires Playbook
Overview
Help indie founders make critical first hires using Hexa's methodology. Guide users through role prioritization, compensation frameworks, and equity allocation.
Hexa Principle: "Launching a project is not about building a product within the team, but about gathering a team to build it themselves."
When This Activates
- "Who should I hire first"
- Making first hires
- Equity for employees
- Compensation/salaries
- "Should I hire or outsource"
- Building team
- Contractor vs. full-time
Hiring Readiness Check
| Criterion | If No | |-----------|-------| | PMF signal | Wait for traction | | 18+ months runway | Extend first | | Clear scope of work | Define first | | Tried it yourself | Do it first | | Time to manage | Founders must manage |
If 2+ "No": Wait or outsource.
Role Prioritization
Score roles: Revenue Impact + Time Saved + Urgency - Difficulty Hire highest score first.
| Company Type | First Hire | |--------------|------------| | Technical, B2B | Sales/BD | | Technical, B2C | Growth/Marketing | | Non-technical | Technical CTO | | Solo technical | Designer |
Hire vs. Outsource
Always Hire: Core engineering, sales, customer success Outsource First: Legal, accounting, PR, recruiting
Compensation Ranges (Seed)
| Role | Cash | Equity (First 10) | |------|------|-------------------| | Engineer | $100K-150K | 0.5%-2% | | Designer | $90K-130K | 0.25%-1% | | Sales | $80K-120K + comm | 0.25%-1% | | Marketing | $80K-120K | 0.25%-0.75% |
Equity Guidelines
| Hire # | Range | |--------|-------| | 1-2 | 1-2% | | 3-5 | 0.5-1% | | 6-10 | 0.25-0.75% |
First Engineer: 1-3% pre-seed, 0.5-1.5% seed Vesting: 4 years, 1-year cliff
Sourcing Channels
- Personal network (best for first 3-5)
- Investor intros
- Communities
- Job boards (last resort)
Don't Hire If
- Don't know week 1 work
- Haven't done job yourself
- Can't afford 18+ months
- No time to manage
- Hiring to "figure it out"
Integration
cofounder-evaluator- Founding team firstfinancial-operations-expert- Plan runway
For complete interview framework, offer scripts, negotiation handling, onboarding plans, and output templates, 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