skills/marketing/fundraising/SKILL.md
Plan and run an early-stage fundraising process and produce a Fundraising Pack (raise decision memo, round design brief, pitch narrative + deck outline, investor pipeline + tracker, outreach/follow-up scripts, diligence checklist). Use for fundraising, raising capital, venture capital, pitch deck, investor outreach, pre-seed, seed. Category: Career.
npx skillsauth add pedronauck/skills fundraisingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Covers
When to use
When NOT to use
Minimum required
Missing-info strategy
Produce a Fundraising Pack (Markdown in chat; or as files if requested) in this order:
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
Example 1 (pre-seed): “We’re 2 founders building a B2B workflow tool. We have 5 design partners and 2 pilots. We have 6 months runway and want to raise $1.5–2.0M. Use fundraising to produce the full Fundraising Pack including a deck outline and investor pipeline tracker.”
Expected: decision memo + round design + deck outline (strong first slide) + target list + outreach scripts.
Example 2 (seed with traction): “We’re at $60k MRR and growing 10% MoM. We’re debating whether to raise now or wait 6 months. Use fundraising to help us decide and create an outreach plan if we choose to raise.”
Expected: raise-vs-wait decision memo with criteria + round design options + pipeline plan.
Boundary example: “Draft a SAFE agreement and tell me what valuation I should take.”
Response: out of scope for legal/pricing advice; offer to produce the negotiation inputs (round design assumptions, comps proxy approach, questions for counsel) and a fundraising process plan.
development
Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
tools
Orchestrate Claude and Codex worker TUIs from a controller agent through herdr panes and the herdr socket CLI. Use when delegating bounded tasks to herdr worker panes, running user-activated plan-first delegations (Claude Code plan mode, Codex Plan mode), waiting on native agent status (idle, working, blocked, done), or verifying worker reports. Workers launch as interactive TUIs via herdr agent start — never through headless runners (compozy exec, claude -p, codex exec). Not for cmux workspaces (see cmux-orchestration) and not for end-user herdr control.
tools
TanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.