founder-ops — Claude Code skill: what it does, how to install
founder-ops is a Claude Code skill that maps a business’s day-to-day operations, from suppliers and staffing to procedures, permits, and risks. It activates for requests about running or opening a business.
MIT 712 installs ★ 4,548 updated 2026-10-07
npx skills add Jakeschincariol/founder-skill --skill founder-ops -a claude-codeWhat founder-ops does
founder-ops turns a business’s daily work into a step-by-step plan using founder/idea.md, founder/offer.md, and founder/numbers.json. It identifies suppliers and equipment with prices and order terms, lays out staff schedules, and writes short procedures for opening, serving or shipping, closing, and reordering.
The skill also lists operating tools, permit checks, and risks with likelihood, impact, and a response plan. Its main output is founder/ops.md. If actual costs differ from the figures, it updates founder/numbers.json and flags the CFO to recalculate. Permit rules vary by location, so each requirement must be confirmed with an authority or a professional; the result is not legal advice.
What it helps with
- map the daily workflow for a business
- compare supplier prices and ordering terms
- plan staff schedules and operating procedures
- list permit checks and responses to likely problems
Example prompts for the agent
- Map the daily operations for my business in Berlin.
- Find suppliers and estimate operating costs for opening a café.
- Write staff schedules, opening procedures, and permit checks for an online store.
How to install founder-ops
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-ops -a claude-code2Manually: put the files in place
~/.claude/skills/founder-ops/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/founder-ops/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-ops -a codex2Manually: put the files in place
.agents/skills/founder-ops/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-ops -a cursor2Manually: put the files in place
.cursor/skills/founder-ops/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/founder-skill skills/founder-ops2Manually: put the files in place
.github/skills/founder-ops/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-ops -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/founder-skill --path skills/founder-opsManually: put the files in place
.devin/skills/founder-ops/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-ops -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about founder-ops
How do I install founder-ops in Claude Code?
Run npx skills add Jakeschincariol/founder-skill --skill founder-ops -a claude-code. The skill file is at ~/.claude/skills/founder-ops/SKILL.md.
What does founder-ops do?
It creates an operations plan covering daily tasks, suppliers, staffing, procedures, tools, permits, and risks. The main output is founder/ops.md.
Which files does founder-ops use?
It reads founder/idea.md, founder/offer.md, and founder/numbers.json. If real costs differ from the figures, it updates founder/numbers.json.
Source text
SKILL.md · MIT
--- name: founder-ops description: >- Your operations manager. Works out how the business actually runs on day one: suppliers and what they cost, who works when, the step-by-step routines for opening, serving or shipping and closing, the tools to run it, the licences and permits to check, and a risk register with what to do when each thing goes wrong. Feeds real costs back to the CFO. Use when the user says "how do I run this", "operations", "suppliers", "staffing", "SOPs", "what do I need to open", "permits", or "day one". argument-hint: "[city or country]" --- # founder-ops A plan that works on paper fails at 7am on a Monday. This skill makes sure the first day, week and month can actually be run, and that the CFO's numbers include what running it really costs. ## Step 1: what the business has to do every day From `founder/idea.md`, `founder/offer.md` and `founder/numbers.json`, write the daily cycle as a list of steps from first thing to last (for a café: deliveries, prep, open, serve, clean, cash up, order; for an online store: orders in, pick, pack, ship, returns, support). Mark which steps a customer sees. ## Step 2: suppliers For every input in the CFO's variable costs and every piece of equipment: two or three real suppliers the user can contact, their public prices or how to get a quote, minimum orders, lead times and payment terms. Link the sources. Where only a quote will tell, say so and add it to the open questions. If a real price differs from `founder/numbers.json`, update it and say the CFO should re-run. ## Step 3: people Who does what, when: a weekly rota for the planned volume and for the slow first month. The roles, the hours, and the wage assumption (from the user, or a public source for the local minimum and typical pay, linked). Payroll costs beyond wages vary by country; flag them for the accountant. ## Step 4: routines (SOPs) Short, numbered routines for the moments that make or break the business: opening, the core service or fulfilment, handling a complaint, closing, and a weekly reorder. Each fits on one page someone could follow on their first day. ## Step 5: tools The smallest stack that runs it: payments, point of sale or store, scheduling, bookkeeping, inventory. Real products with their published prices, and why each. ## Step 6: licences, permits and insurance A checklist of what businesses of this type usually need in the user's city or country (registration, tax numbers, health or food permits, signage permits, insurance), each with the official page to confirm it. Say plainly that rules differ by place and change, and the user must confirm each with the authority or a professional. Not legal advice. ## Step 7: risk register The ten things most likely to go wrong (a supplier runs out, a key person is sick, the card terminal fails, a bad review, a slow month), each with how likely, how bad, and the plan. ## Output `founder/ops.md`, plus updated `founder/numbers.json` if real costs changed. Next: `/founder-launch`.
© Jakeschincariol · MIT · Jakeschincariol/founder-skill