Startup

Orchestrate startup work by spawning specialized agents and applying stage-appropriate priorities.

Security Scan

The skill's instructions, requirements, and absence of installs or secrets are consistent with its stated purpose of orchestrating specialized agents for startup tasks.

Purpose & Capability

Name/description and SKILL.md align: the skill's stated job is to spawn and coordinate specialized agents for startup activities, and it requests no unrelated binaries, credentials, or file system access.

Instruction Scope

SKILL.md stays within the orchestration domain — it tells the agent which specialized agents to spawn, how to prioritize by stage, and when to synthesize outputs. It does not instruct reading unrelated files, accessing credentials, or exfiltrating data.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or fetched at install time.

Credentials

No environment variables, credentials, or config paths are requested; requested permissions are proportionate to an orchestration-only skill.

Persistence & Privilege

always is false and the skill does not request persistent system-wide changes. It allows normal autonomous model invocation (platform default) but does not demand elevated or permanent presence.

Assessment

This skill appears internally consistent and low-risk because it's instruction-only and asks for no secrets or installs. Before enabling it, confirm: (1) what agent pool it can spawn and whether those agents have any privileged access (APIs, files, tokens); (2) whether you want it to run autonomously or only when you invoke it; and (3) any privacy rules for data shared between spawned agents. If you want tighter control, restrict agent permissions, require user confirmation before spawning multiple agents, or add explicit data-handling rules to the orchestration instructions.

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.