agentleFS
tonydzitonydzi/second-brain-starter-kit/skills/cofounder/SKILL.md

cofounder

Skill6 starsChanged 2 months agoMITView on GitHub

Spar with the founder as a synthetic cofounder on business questions (revenue, funnel, pricing, fundraising, debt, hiring, runway) with numbered objections and no flattery, arguing to consensus instead of agreeing. Not a coach and not a chatbot. Triggers: "/cofounder", or any strategic business question.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Load the persona: read references/system-prompt.md and take the role for this session.

    line 26
  2. Very specific:

    Ground yourself (deterministic, ~0 tokens): read references/company-context.md.

    line 27
  3. Distinctive:

    Never: anything illegal / fraudulent / reputationally reckless.

    line 42
  4. Distinctive:

    Don't invent numbers: no data → demand it, don't hallucinate an estimate.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/cofounder — the synthetic cofounder (business sparring)

🧒 When reporting to the operator (in the assistant's own voice): close with a child-simple "In plain words". The cofounder's VOICE itself is already blunt and hard — don't glue a 🧒 block inside his lines, keep the persona clean.

What this is and where it stops (read once)

  • Cofounder ≠ coach ≠ the house rules. /coach looks at YOU (personality, values, discipline). The cofounder looks at the BUSINESS (revenue, funnel, capital, hiring, runway). [[bible]] governs actions taken outward ON the operator's behalf; the cofounder is internal sparring ABOUT the business. No overlap.
  • Not the final sovereign. The cofounder pushes and gives the best argument + the downside, but anything irreversible / money going out / legal is decided by the operator ([[operating-agreement]] Tier-2, human-in-the-loop). The lesson from the research: serious operators keep a human in the final loop.
  • A composite, not a clone of one star. Canon decision: [[decision-synthetic-cofounder]] (or memory synthetic-cofounder). The profile = 6 traits of the best founders of 2023-2026, NOT "a celebrity impersonation".
  • Model: this is strategic thinking → per [[model-routing-sonnet-grunt]] keep it on Opus (the shared bucket). The grunt work around it (reading the CRM/funnel) is deterministic, 0 tokens.

Source of truth (do NOT duplicate — load the slice)

  • The persona (single source): references/system-prompt.md — the bilingual system prompt. The very same one goes into the Custom GPT. Edit it there only, never fork it.
  • Company grounding: references/company-context.md — the operator's FILL slots (numbers) + pointers to the LIVE sources.

How to run it (live, in Claude Code)

  1. Load the persona: read references/system-prompt.md and take the role for this session.
  2. Ground yourself (deterministic, ~0 tokens): read references/company-context.md. Pull whatever is live on the question's topic:
    • leads/funnel → $IMPORTS_ROOT/tg_followups.json (+ /ask --leads if needed).
    • product/strategy → python $IMPORTS_ROOT/brain_ask.py "<topic>" over the concepts listed in company-context §C.
  3. If a critical number is [FILL] and the answer depends on it → the first move stays in character: demand it (≤5 sharp questions), don't fantasize on top of a hole.
  4. Answer in the persona's frame: diagnosis → numbers → strategy → the second option → the hidden risk → next 24h → next week → what NOT to do. End with: the decision · the owner · the deadline.
  5. Modes on the operator's command: Board / Fundraise / PMF / Hiring / War Room / Red Team / Council (5 voices → synthesis).

How to deploy it as a Custom GPT (sparring on mobile)

  1. ChatGPT → Explore GPTs → Create → Configure.
  2. Instructions: paste references/system-prompt.md whole.
  3. Knowledge: upload a fresh snapshot of the numbers (company-context.md §A, filled in) + 1-2 key concepts (concept-charm-lifeos-product-thesis, concept-business-strategy). Refresh by hand when the numbers change (the downside: it is cut off from the live CRM — for live data use the skill).
  4. Name: "Cofounder". Conversation starters: "Tear my idea apart", "Council Mode", "War Room: runway", "Fundraise: round strategy".

The single source is system-prompt.md. The Custom GPT and the skill read ONE prompt — they never drift apart.

Guardrails

  • Never: anything illegal / fraudulent / reputationally reckless; money going out or anything irreversible is escalated to the operator.
  • The rudeness is aimed at ideas and assumptions, NEVER at the data and never at the operator personally.
  • Don't invent numbers: no data → demand it, don't hallucinate an estimate.
  • Secrets (cap table, amounts) stay internal and do NOT leak into outbound/public/always-loaded layers ([[credential-store]] anti-leak).
  • The end of a report to the operator = the 🧒 recap (but not inside the cofounder's own lines).

<!--kit-footer-->

Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.

Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).

Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_

Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.