The actual prompts, skill files, and step-by-step guides I used to build the tools I run at Raspberry Ventures. No coding experience needed. Just Claude and an afternoon.
Pick a tool and follow the step-by-step guide to build it
Skill files, CLAUDE.md configs, prompt templates. The building blocks
The accounts and tools you need. All free, all connected to Claude
Track portfolio performance and MOIC, generate LP reports. Includes a heatmap dashboard, investor views, and diary integration.
Log meetings, decisions, and deal notes in one place. The operational backbone of a running syndicate.
Quickly assess whether an inbound deal fits your syndicate's thesis before spending time on diligence.
Run a structured deal analysis from first look through to a shareable investment memo.
These are real files, skills, and connectors you can use today. Some are useful for anyone building with Claude. Others are specific to syndicate leads and investors.
A markdown file at the root of your project that Claude reads automatically. Mine tells it my deployment pattern (GitHub to Cloudflare Pages), my design choices (Lora + DM Sans fonts, violet/coral palette), and what not to do (things I've learned the hard way). Every session starts with Claude already knowing the rules.
ConfigBuilt-in skills that teach Claude how to create professional outputs: xlsx for spreadsheets and financial models, pdf for extracting and generating documents, pptx for investor decks, docx for memos and reports. Claude picks the right skill automatically based on what you ask for.
SkillsConnectors that let Claude operate your tools directly. I use three daily: Supabase MCP for database queries and migrations, GitHub MCP for pushing code and managing repos, and Cloudflare MCP for checking deployments. Claude doesn't tell you what to type. It runs the commands itself.
Connectorsclaude mcp add in the terminal.
Setup guide →
SQL table structures for Supabase that Claude builds around. The Portfolio Tracker uses schemas for companies, investments, valuations, and diary entries. The Scope Check uses deal criteria and thesis parameters. Copy-paste a schema, and Claude generates the app to match.
DatabaseNot generic "write me a tool" prompts. These are the exact sequences that built what I'm running in production. Each recipe includes the prompts I used, in order, with notes on what to tweak for your syndicate (thesis, check sizes, LP base).
PromptsCloudflare Pages settings, _headers files, wrangler.toml. The config files that mean pushing to GitHub = live site in seconds. Each recipe includes these so you're not guessing at deployment. Static HTML, no build step, zero cost.
A Claude plugin for financial work: variance analysis (budget vs. actual across your portfolio), financial statements (generate P&L, balance sheet, cash flow with period comparisons), and reconciliation (match your records against bank statements or SPV accounts). Installable from the plugin registry.
PluginTurn raw deal data into dashboards and analysis: SQL queries across your Supabase tables, interactive dashboards built as HTML, statistical analysis for portfolio performance, and data visualization with charts. Point it at your investor CSV or deal tracker and ask questions in plain English.
PluginAutomate recurring work: weekly portfolio snapshots, monthly LP report generation, deal pipeline reviews. Set a schedule and Claude runs it. It pulls fresh data from Supabase, generates the output, and saves it where you need it. No cron jobs or scripts to maintain.
AutomationConnected to Claude, these let you draft investor updates, search past deal correspondence, and manage your calendar without switching between apps. I use them for LP communications: Claude pulls portfolio data from Supabase, drafts the update email, and queues it as a Gmail draft for me to review.
ConnectorsA skill pattern for matching and scoring. Originally built for real estate (buyer-seller matching by budget, location, features) but directly applicable to syndicate deal flow. Score inbound deals against your thesis criteria, match investors to opportunities by check size and sector preference. The pattern works; you just change the domain.
Skill pattern.claude/skills/.
Examples →
A meta-skill for building your own custom skills. Define a capability (e.g. "generate a CMA for a deal" or "score a startup against my thesis"), test it with evals, and refine until it works consistently. This is how you go from following recipes to writing your own.
MetaThe accounts and tools that make everything work. All free tier. The thing that changed everything for me: once you connect these to Claude via MCPs, Claude can operate them directly. No more copy-pasting between browser tabs.
The real unlock was connecting these tools to Claude via MCPs. Instead of building in one tab, checking the database in another, and deploying in a third, Claude now does it all. That single change cut my build-to-deploy time from hours to minutes.