accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When a founder needs to create a sales proposal, statement of work, contract, NDA, or master service agreement. Activate when the user mentions proposal, SOW, quote, contract, NDA, MSA, or needs to formalize a deal.
$ npx -y skills add shawnpang/startup-founder-skills --skill proposal-generation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/proposal-generationContext preview
The summary Claude sees to decide when to auto-load this skill.
When a founder needs to create a sales proposal, statement of work, contract, NDA, or master service agreement. Activate when the user mentions proposal, SOW, quote, contract, NDA, MSA, or needs to formalize a deal.
name: proposal-generation description: When a founder needs to create a sales proposal, statement of work, contract, NDA, or master service agreement. Activate when the user mentions proposal, SOW, quote, contract, NDA, MSA, or needs to formalize a deal. related: [sales-script, cold-outreach] reads: [startup-context]
From `startup-context` or the user:
1. **Gather requirements** — Read startup-context if available. Collect all eight inputs listed above. Flag any missing item as REQUIRED. 2. **Select document type** — Match the engagement to the right format: fixed-price contract, consulting retainer, SaaS partnership, NDA, SOW, or full proposal. 3. **Apply jurisdiction rules** — Select clause variants based on governing law. US uses work-for-hire doctrine; EU requires explicit IP assignment deeds; DACH requires transfer of Nutzungsrechte since authors retain moral rights under BGB. 4. **Draft the document** — Fill all sections using structured Markdown with bracketed placeholders for client-specific data. Include the key clauses table below. 5. **Add GDPR addendum if needed** — For EU/DACH engagements handling personal data, attach a Data Processing Addendum per Art. 28 GDPR covering data categories, sub-processors, and cross-border transfer mechanisms. 6. **Review for common pitfalls** — Check for missing IP assignment language, vague acceptance criteria, no change order process, jurisdiction mismatches, and missing liability caps. 7. **Provide conversion instructions** — Include Pandoc commands for DOCX output with legal-style numbered sections.
Deliver a complete document in structured Markdown containing: 1. **Header block** — Effective date, party names, addresses 2. **Services / scope** — Detailed deliverables with acceptance criteria and dates 3. **Payment terms** — Milestone-based, net-30, or retainer schedule with late payment interest 4. **Intellectual property** — Ownership assignment, pre-existing IP licenses, portfolio rights 5. **Confidentiality** — Duration (2-5 years standard, perpetual for trade secrets) 6. **Warranties** — As-is disclaimer or limited fix warranty (30/90-day) 7. **Liability cap** — 1x contract value standard, 3x for high-risk engagements 8. **Termination** — For cause (14-day cure) and for convenience (30/60/90-day notice) 9. **Dispute resolution** — Jurisdiction-appropriate arbitration (AAA/ICC/LCIA/DIS) 10. **Signature block** — Both parties with date lines
| Clause | Options | |--------|---------| | Payment terms | Net-30, milestone-based, monthly retainer | | IP ownership | Work-for-hire (US), assignment (EU/UK), Nutzungsrechte transfer (DACH) | | Liability cap | 1x contract value (standard), 3x (high-risk) | | Termination | For cause (14-day cure), convenience (30/60/90-day notice) | | Confidentiality | 2-5 year term, perpetual for trade secrets | | Dispute resolution | AAA (US), ICC (EU), LCIA (UK), DIS (DACH) |
Present three tiers to anchor the prospect and make the middle option feel natural:
| | Starter | Recommended | Premium | |---|---------|-------------|---------| | Scope | Core deliverables | Core + integrations | Everything + custom work | | Best for | Teams getting started | Most teams | Enterprise needs | | Price | $X | $Y | $Z |
Always lead with value before cost. Show ROI math: "This investment of $X saves $Y, paying for itself in Z months."
A Statement of Work is operational, not persuasive. Key sections:
1. **Missing IP assignment language** — "Work for hire" alone is insufficient in EU; DACH needs explicit Nutzungsrechte transfer 2. **Vague acceptance criteria** — Always define what "accepted" means with written sign-off and rejection windows 3. **No change order process** — Scope creep kills fixed-price projec
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…