Case Study Builder
BrianRWagner/ai-marketing-claude-code-skills
Turns a client win into case studies, proposal blurbs, social proof quotes and sales stories, after collecting the details and at least one concrete number.
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks.
Install Sales Script
$ npx skills add shawnpang/startup-founder-skills --skill sales-script -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shawnpang/startup-founder-skills sales-script --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales-script .claude/skills/sales-script && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sales-script" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-script into .claude/skills/sales-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-script", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-scriptType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shawnpang/startup-founder-skills --skill sales-script -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shawnpang/startup-founder-skills sales-script --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sales-script .agents/skills/sales-script && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sales-script" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-script into .agents/skills/sales-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-script", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shawnpang/startup-founder-skills --skill sales-script -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shawnpang/startup-founder-skills sales-script --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sales-script .cursor/skills/sales-script && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sales-script" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-script into .cursor/skills/sales-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-script", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shawnpang/startup-founder-skills.git --path skills/sales-script--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shawnpang/startup-founder-skills --skill sales-script -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shawnpang/startup-founder-skills sales-script --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sales-script .gemini/skills/sales-script && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sales-script" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-script into .gemini/skills/sales-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-script", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shawnpang/startup-founder-skills sales-scriptInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shawnpang/startup-founder-skills --skill sales-script -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sales-script .github/skills/sales-script && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sales-script" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-script into .github/skills/sales-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-script", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shawnpang/startup-founder-skills --skill sales-script -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shawnpang/startup-founder-skills sales-script --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sales-script .opencode/skills/sales-script && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sales-script" agent skill from https://github.com/shawnpang/startup-founder-skills/tree/main/skills/sales-script into .opencode/skills/sales-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-script", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sales-script- GitHub stars
- 341
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,164 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks.
- Works in 4 steps: Discovery & Research → Solution Design & Positioning → Script & Demo Preparation → …
- Tasks that involve Proposals and quotes
- SKILL.md covers When to Use, Context Required, Workflow and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sales Script is an agent skill from shawnpang/startup-founder-skills. When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks. Activate for sales calls, demo prep, talk tracks, bid responses, competitor comparisons, or pre-sales engineering.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Proposals and quotes, Sales call preparation and Sales enablement. The repository describes itself as: AI agent skills for tech startup founders — fundraising, sales, product, recruiting, engineering, legal, ops, and growth. Works with Claude Code, Cursor, Codex, and any Agent… The licence is MIT.
When your agent uses it
- Tasks that involve Proposals and quotes
- Tasks that involve Sales call preparation
- Tasks that involve Sales enablement
Example prompts
- “/sales-script”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4ad31b4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sales Script loads about 2.4k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 1,164 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from shawnpang/startup-founder-skills at commit 4ad31b4, republished under its MIT licence (© shawnpang). 1,164 words, ~2,363 tokens.
Download SKILL.mdSave it as
.claude/skills/sales-script/SKILL.md (or your agent's skills folder).- name
- sales-script
- description
- When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks. Activate for sales calls, demo prep, talk tracks, bid responses, competitor comparisons, or pre-sales engineering.
- related
- cold-outreach, proposal-generation
- reads
- startup-context
Sales Script
When to Use
- Preparing for a discovery call, product demo, or closing meeting
- Responding to an RFP/RFI and need coverage gap analysis
- Building a competitive feature comparison matrix against rivals
- Planning or scoring a proof-of-concept (POC) engagement
- Preparing a technical demo script with stakeholder-specific talking points
- Handling objections or conducting win/loss analysis
Context Required
From startup-context or the user:
- Product/service — What you sell, who it is for, key capabilities
- Target persona — Role, seniority, typical pain points
- Deal context — Stage, deal size, stakeholders involved, known objections
- Competitive landscape — Who else they are evaluating, your differentiators
- Proof points — Metrics, case studies, customer quotes
- RFP/RFI details — If responding to a formal request, the requirement categories and priorities
Workflow
Phase 1: Discovery & Research
- Gather context — Read startup-context. Identify the script type needed: discovery call, demo, RFP response, competitive analysis, or POC plan.
- Map customer requirements — Document the prospect's current architecture, pain points, integration requirements, security/compliance needs, and business drivers.
- Assess competitive landscape — Identify competitors in the deal. Map your product capabilities against theirs to find differentiators and vulnerabilities.
- Score requirement coverage — For RFP/RFI responses, categorize each requirement as Full (100%), Partial (50%), Planned (25%), or Gap (0%). Weight by priority: Must-Have 3x, Should-Have 2x, Nice-to-Have 1x.
Phase 2: Solution Design & Positioning
- Map pain to value — Connect each prospect pain point to a specific product capability with proof (metrics, case studies).
- Build competitive differentiation — Identify at least one strong differentiator per customer priority. If none exist, flag for product team escalation.
- Design the talk track — Structure the conversation or document around their priorities, not your feature list.
Phase 3: Script & Demo Preparation
- Draft the script — Write the full script with timing, talk tracks, questions, transition cues, and stakeholder-specific talking points.
- Prepare objection handling — Anticipate likely objections and write response frameworks using the LAER model.
- Build demo environment — Create a pre-demo checklist: environment tested, sample data loaded, backup environment prepared, customer-specific branding applied.
Phase 4: POC & Closing (if applicable)
- Define POC scope — Set success criteria, timeline (typically 5 weeks), phased testing plan. Evaluate across functionality, performance, integration, usability, support. Require >60% for a go recommendation.
- Close the deal — Package POC results, demo feedback, and competitive positioning. Apply closing techniques appropriate to the deal stage.
Output Format
Deliver the format matching the request: Discovery call script (SPIN-phase questions, qualifying criteria, next-step framing), Demo script (scene-by-scene with timing, per-role talk tracks, pre-demo checklist, objection table), RFP response analysis (coverage score, gap count, bid/no-bid recommendation), Competitive matrix (feature comparison with weighted scores, differentiators, vulnerabilities), POC plan (phased timeline, success criteria, scorecard), Objection handling doc (table: objection, concern, response, proof, follow-up), or Closing playbook (decision criteria, techniques, timeline).
Frameworks & Best Practices
Discovery Call Framework (30 min)
| Phase | Duration | What to Do |
|---|---|---|
| Rapport & agenda | 3 min | Set the agenda, confirm time, build quick rapport |
| Situation questions | 7 min | Understand their current state and workflow |
| Problem questions | 8 min | Dig into pain points, frequency, and impact |
| Implication questions | 5 min | Explore the cost of not solving the problem |
| Need-payoff questions | 4 min | Let them articulate the value of a solution |
| Next steps | 3 min | Summarize, confirm fit, schedule the demo |
Demo Script Structure
Pre-demo checklist: Environment tested, sample data loaded, backup environment ready, screen sharing tested, browser tabs pre-loaded, network/VPN verified, customer branding applied.
Attendee mapping: For each attendee, document their title, role in evaluation (decision maker / champion / technical evaluator / end user), and key interest area.
| Segment | Duration | Content |
|---|---|---|
| Opening | 5 min | Thank attendees, recap discovery findings, set agenda |
| Use Case 1 | 7 min | Primary pain point demo with business context and differentiator highlights |
| Check-in | 2 min | "How does this compare to how you handle it today?" |
| Use Case 2 | 7 min | Secondary pain point demo |
| Use Case 3 | 6 min | Differentiator or delight feature they did not expect |
| Integration demo | 10 min | Show connector setup, data flow, end-to-end workflow |
| Admin & security | 5 min | RBAC, audit logs, SSO |
| Q&A | 5 min | Handle live questions |
| Close | 5 min | Summarize value, propose next steps with specific dates |
Demo principles: Demo after discovery, never before. Use their terminology and data. Leave time for questions. Share why you built the feature — origin stories resonate more than feature walkthroughs.
Show full SKILL.md (458 more words)Show less
RFP Bid/No-Bid Framework
- Bid: Coverage >70% AND must-have gaps <=3
- Conditional Bid: Coverage 50-70% OR must-have gaps 2-3
- No-Bid: Coverage <50% OR must-have gaps >3
Objection Handling (LAER Model)
- Listen — Let them finish. Do not interrupt or get defensive.
- Acknowledge — "That makes sense" or "I hear that a lot."
- Explore — Ask a follow-up to understand the real concern.
- Respond — Address the real concern with proof, then confirm.
| Category | Example Objection | Response Strategy |
|---|---|---|
| Price | "Too expensive" | Reframe as ROI. "What is the cost of not solving this?" |
| Timing | "Not the right time" | Uncover the real blocker. "What would need to change?" |
| Competition | "We use X already" | Differentiate on their specific pain point |
| Authority | "Need to check with my boss" | Enable the champion with materials they need |
| Status quo | "What we have works" | Quantify hidden cost. Share a peer story. |
| Trust | "You are too small" | Lead with proof: customers, metrics, investors, team |
Demo Recovery
If demo breaks: switch to backup, explain what they would have seen, offer recorded follow-up. If question derails: acknowledge, note for follow-up, return to script. If audience disengages: pause and ask "Is this addressing what you need?", skip to most relevant section.
Closing Techniques for Founders
- Summary close: "We agreed [pain] costs [amount], our solution addresses [needs]. What would it take to move forward?"
- Timeline close: "You want this solved by Q3. Working backward, we need to start by [date]."
- Pilot close: "Start with a focused pilot on [use case], prove the value, expand from there."
- Founder close: "I will personally ensure your onboarding goes smoothly. You work directly with me for 30 days."
Post-Demo Actions
Send thank-you email with recording within 24 hours. Share demo environment access. Send follow-up addressing unanswered questions. Schedule next meeting. Update CRM with demo notes and next steps. Log objections for battlecard updates.
Related Skills
cold-outreach— Use to generate the meetings that lead to these sales conversationsproposal-generation— Use after a successful demo to create the formal proposal, SOW, or contract
Examples
Prompt: "I have a demo tomorrow with the Head of Engineering at a fintech. They care about reducing deployment failures."
Good demo opening output:
"Thanks for making time, [Name]. Last week you mentioned your team spends about 8 hours per sprint dealing with failed deployments and rollbacks. You said the biggest pain is that it slows release velocity and frustrates the team. Is that still the top priority, or has anything changed?
Great. I want to show you three specific workflows that address deployment reliability. About 25 minutes, with time for your questions. Sound good?
Let me start with how [Similar Fintech Customer] handled this before switching to us..."
Prompt: "We got an RFP from a large enterprise. Should we bid?"
Good output snippet:
RFP Coverage Analysis:
- Overall coverage score: 68% (Conditional Bid range)
- Must-have gaps: 2 (within threshold)
- Recommendation: CONDITIONAL BID
Action items before proceeding:
1. Confirm planned roadmap items cover the 2 must-have gaps
2. Build differentiator narrative around your 3 strongest categories
3. Flag gaps to product team for timeline confirmation© shawnpang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sales-script of shawnpang/startup-founder-skills.
Open the folder on GitHubat commit 4ad31b4
Compare with similar skills
Sales Script next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sales Script this skillshawnpang/startup-founder-skills | 341 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Case Study BuilderBrianRWagner/ai-marketing-claude-code-skills | 440 | — | ~1.8k | Automated safety check: Pass | None | |
| Discovery Call Playbookgtmagents/gtm-agents | 413 | 1 repos | ~368 | Automated safety check: Pass | Apache-2.0 | |
| Proposal PricingTheCraigHewitt/skills | 157 | — | ~6k | Automated safety check: Pass | MIT | |
| Deal Playbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Enterprise Customer Visit Playbookzj-unicom-ai/UniEmployee | 358 | — | ~458 | Automated safety check: Pass | MIT |
Similar skills
Discovery Call Playbook
gtmagents/gtm-agents
Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.
Proposal Pricing
TheCraigHewitt/skills
When the user wants to build a proposal, structure pricing, create an SOW, or present a deal to a prospect.
Deal Playbook
jeremylongshore/tons-of-skills-marketplace
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
Enterprise Customer Visit Playbook
zj-unicom-ai/UniEmployee
Prepares account managers for visits to government and enterprise customers: looks up the customer file, matches products, builds a Word solution document and files visit minutes.
- Official
Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
More from shawnpang/startup-founder-skills
All 50 skills in this repoContract Review
shawnpang/startup-founder-skills
When the user needs to review an existing contract, assess risk in proposed terms, or evaluate a contract before signing.
Accelerator Application
shawnpang/startup-founder-skills
When the user wants to apply to startup accelerators, incubators, or fellowship programs.
Architecture Design
shawnpang/startup-founder-skills
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis.
Board Update
shawnpang/startup-founder-skills
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
Churn Analysis
shawnpang/startup-founder-skills
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.
Cicd Setup
shawnpang/startup-founder-skills
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".
Related
Categories
Questions about Sales Script
What does Sales Script do?
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks. Sales Script is an agent skill from shawnpang/startup-founder-skills. When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks.
When should I use Sales Script?
Sales Script fits situations like: tasks that involve Proposals and quotes; tasks that involve Sales call preparation; tasks that involve Sales enablement.
How do I install Sales Script in Claude Code?
Run `npx skills add shawnpang/startup-founder-skills --skill sales-script -a claude-code`. Or copy the skill folder (skills/sales-script in shawnpang/startup-founder-skills) into .claude/skills/sales-script in your project. Claude Code loads it when a task matches its description.
How do I install Sales Script in Codex?
Run `npx skills add shawnpang/startup-founder-skills --skill sales-script -a codex`. Or copy the skill folder (skills/sales-script in shawnpang/startup-founder-skills) into .agents/skills/sales-script in your project. Codex loads it when a task matches its description.
Can I use Sales Script in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shawnpang/startup-founder-skills --skill sales-script -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-script, .gemini/skills/sales-script, .github/skills/sales-script and .opencode/skills/sales-script in your project.
What does Sales Script need to run?
SKILL.md names no scripts, command-line tools or credentials: Sales Script is instructions for the agent only.
Does Sales Script access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sales Script safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sales Script use?
Sales Script is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sales Script use?
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sales Script?
Skills that share tags, products or a category with Sales Script: Case Study Builder (BrianRWagner/ai-marketing-claude-code-skills, 440 stars), Discovery Call Playbook (gtmagents/gtm-agents, 413 stars), Proposal Pricing (TheCraigHewitt/skills, 157 stars) and Deal Playbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sales Script?
shawnpang (a GitHub user) maintains it in shawnpang/startup-founder-skills, which has 341 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on March 16, 2026.
Source: shawnpang/startup-founder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.