Orchestrate startup work by spawning specialized agents and applying stage-appropriate priorities.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add lxyeternal/MalSkillBench --skill startup --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Startup?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lxyeternal-startup)More formats (shields.io, HTML) on the badges page.
---
name: Startup
description: Orchestrate startup work by spawning specialized agents and applying stage-appropriate priorities.
metadata: {"clawdbot":{"emoji":"🦄","os":["linux","darwin","win32"]}}
---
# Startup Orchestration
## How to Work
When the user requests help, spawn specialized agents for each function:
- Product decisions → product manager agent
- Code/technical → developer or engineer agent
- Design/UX → designer agent
- Growth/marketing → marketing agent
- Financial modeling → analyst or CFO agent
- Hiring/people → recruiter agent
- Legal/contracts → lawyer agent
- Sales/deals → sales agent
For complex requests, run multiple agents in parallel and synthesize their outputs.
## Stage Awareness
Identify the startup's stage first — it changes everything:
- **Pre-PMF**: Prioritize learning speed. Reject anything that doesn't help validate faster.
- **Post-PMF**: Prioritize scaling. Reject anything that doesn't help grow efficiently.
Ask about current stage if unclear. Never apply post-PMF advice to pre-PMF startups.
## Critical Priorities
Pre-PMF: Only three questions matter:
1. Are users coming back?
2. Would they be upset if it disappeared?
3. Are they telling others?
Everything else is distraction until these are yes.
## Decision Routing
- Reversible decisions → decide fast, in hours
- Irreversible decisions → spawn analyst agent to model scenarios
- Cross-functional decisions → spawn relevant agents, synthesize recommendations
- Unclear ownership → ask user who should own the outcome
## Resource Constraints
Startups have limited time, money, and attention. When recommending actions:
- Always consider founder time cost, not just dollar cost
- Prioritize high-leverage activities over thorough-but-slow approaches
- Suggest scrappy alternatives before expensive ones
- Default to manual-first, automate when it hurts
## Common Traps to Flag
- Building features when retention is broken
- Hiring before founder is overwhelmed doing the role
- Optimizing revenue before product-market fit
- Scaling sales before the sales process is repeatable
- Spending on brand before distribution works
When you detect these patterns, pause and flag before proceeding.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!