agentleFS
Sign inStart free
schub-techschub-tech/llm-ideation-wiki/.agents/skills/founder-profile/SKILL.md

founder-profile

Skill11 starsChanged 31 days agoMITView on GitHub

Capture the founder's ambition, end-game, financial target, timeframe, investment willingness, and risk tolerance, then reality-check the answers against themselves. Writes to `wiki/founder` in Notion. Use after onboarding, at wiki start, before creating the first idea, or when the user asks to frame goals, set ambition, capture the founder profile, or reality-check what's possible.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. thisisfatih/apply-yc★ 16same name
    2. Latifox/find-me-saas★ 10same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read first: If scripts/notion_wiki.py find wiki/founder returns a page, fetch it with scripts/notion_wiki.py get wiki/founder and offer to …

    line 8
  2. Distinctive:

    Ask one question at a time: Wait for the answer before moving on — multi-question dumps let the user dodge the hard one.

    line 10
  3. Distinctive:

    Ask these six, in order:

    line 12
  4. Distinctive:

    If the user gives a vague answer (e.g.

    line 21
  5. Distinctive:

    After all six are captured, scan the answers against each other and surface any tensions in 3–6 bullets.

    line 25
  6. Distinctive:

    Do not bring in market or idea-specific facts — this is a self-consistency check on the stated answers.

    line 32
  7. Distinctive:

    If the user wants to revise an answer in light of the tensions, update before writing.

    line 34
  8. Very specific:

    Create the page if missing: scripts/notion_wiki.py create wiki/founder --parent wiki/ --title "Founder" --emoji 🎯 --file <markdown-file>

    line 38
  9. Very specific:

    If it already exists, update it: scripts/notion_wiki.py update wiki/founder <markdown-file>

    line 40
  10. Distinctive:

    Run the ritual (AGENTS.md § Mechanics).

    line 56
  11. Very specific:

    Do not check the profile against any specific idea here.

    line 62

≈ “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

Capture the founder profile that every later idea will be measured against. One Notion page, six questions, then a tension check.

Read first. If scripts/notion_wiki.py find wiki/founder returns a page, fetch it with scripts/notion_wiki.py get wiki/founder and offer to update rather than overwrite.

Ask one question at a time. Wait for the answer before moving on — multi-question dumps let the user dodge the hard one. Reflect each answer back in one short line before asking the next, so the user can correct drift early.

Ask these six, in order:

  1. Team shape — solo founder, small team (≤10), or large organization?
  2. End game — fast exit (growth play), IPO (valuation play), or hold-and-run (profit/lifestyle play)?
  3. Financial success — what's the number? Net to the founder, total enterprise value, or annual income — be specific about which.
  4. Timeframe — by when does (3) need to be true?
  5. Investment willingness — how much of your own time (hours/week, years) and your own money (€/$ ceiling) are you willing to commit before the idea has to pay for itself?
  6. Risk tolerance — what probability of going to zero are you comfortable with? Frame as a number, not "I'm okay with risk."

If the user gives a vague answer (e.g. "a lot", "comfortable", "soon"), ask one clarifying follow-up to pin a number or category. Do not move on without one.

Reality check — tensions in the answers only.

After all six are captured, scan the answers against each other and surface any tensions in 3–6 bullets. Examples of the kind of tension worth flagging:

  • Solo founder + IPO end game + short timeframe.
  • High financial target + low capital willingness + low risk tolerance.
  • Lifestyle/profit end game + fast-exit-sized number.
  • Timeframe shorter than typical category cycle (e.g. 2 years to a regulated-market IPO).

Do not bring in market or idea-specific facts — this is a self-consistency check on the stated answers. If there are no tensions, say so in one line and move on. No manufactured objections, no padding.

If the user wants to revise an answer in light of the tensions, update before writing.

Write to Notion.

  1. Create the page if missing: scripts/notion_wiki.py create wiki/founder --parent wiki/ --title "Founder" --emoji 🎯 --file <markdown-file>
  2. If it already exists, update it: scripts/notion_wiki.py update wiki/founder <markdown-file>

Page body, in this order:

  • One-line lede: who the founder is and what shape company they want.
  • Ambition table or bullets: team shape, end game, financial target (with which metric), timeframe.
  • Willing to invest: time and money ceilings.
  • Risk tolerance: stated probability-of-zero comfort.
  • Tensions (only if any were surfaced): one bullet per tension, plain and direct.
  • Last updated: today's date.

Mark every stated answer as ^[user-claim]. Mark tensions as ^[inferred]. Do not invent numbers the user did not give — if they refused to pin one, write "not pinned" rather than guessing.

Finish.

  1. Run the ritual (AGENTS.md § Mechanics).
  2. Tell the user the page is at wiki/founder in Notion and that the next step is /new-idea.

Rules.

  • One page only: wiki/founder. Never per-idea.
  • Do not check the profile against any specific idea here. Idea-vs-profile fit is the job of later skills (new-idea, grill-me, wiki-lint, idea overview synthesis) once an idea has enough surface area to test.

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.

Check your setup, free