form-fill
Skill16 starsChanged 7 months agoMITView on GitHub
Auto-fill the YC application form using Playwright. Requires a completed FOUNDER_PROFILE from the founder-profile skill. Trigger when a founder says "fill out the form", "fill in my YC application", "let's submit", or "open the YC form". Claude fills every field, founder approves each section, founder clicks all submit/save/advance buttons.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- apsethicsbowl20026-collab/open-computer-skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- apsethicsbowl20026-collab/open-computer-skills★ 2same 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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- founder-profileSkill
- apply-yc-onboardingSkill
- yc-applicationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 16 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Claude fills fields. Founder clicks buttons: No exceptions.
- Distinctive: line 25
Never click: Submit, Save changes, Save & return to application, or any button that changes form state.
- Distinctive: line 26
Batch-fill entire sections, then screenshot for review: Never fill one field, confirm, fill next.
- Distinctive: line 28
If a field has a character limit and the drafted answer exceeds it, truncate and flag: "I truncated this to fit the [N]-char limit.
- Very specific: line 29
Never fabricate a value. If the profile has TBD for a field, leave the field blank and flag it.
- Distinctive: line 30
If the founder corrects an answer mid-fill, update the draft file and refill.
- Distinctive: line 98
After filling all profile fields:
- Distinctive: line 108
After returning to main application:
- Distinctive: line 125
After founder uploads: "Founder video uploaded.
- Distinctive: line 156
If Yes: reveals "How many active users or customers do you have?
- Distinctive: line 158
If Yes: reveals three fields: a.
- Distinctive: line 190
If Yes: reveals two fields: a.
- Distinctive: line 194
If Yes: reveals five fields: a.
- Distinctive: line 206
If equity split looks unusual (e.g.
- Distinctive: line 234
Before the founder submits:
- Distinctive: line 270
Field not found: Use browser_snapshot to re-read the page, try alternate selectors.
- Distinctive: line 274
Anti-bot block: Stop immediately. Tell founder: "The page may be blocking automated input.
≈ “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.
Files
YC Application Form Filler
Fill the YC application form field by field. Claude types everything. The founder reviews and approves each section. The founder clicks every button that advances or submits - Claude never clicks those.
Prerequisites
Before starting:
- A completed
FOUNDER_PROFILEblock from the founder-profile skill, or a draft file at.temp/yc-application-draft.md. If neither exists, runfounder-profilefirst. - Playwright MCP must be active.
Do not ask the founder to open or navigate the browser. Navigate there yourself. Pause only if the page shows a login screen - then say: "You need to log in at apply.ycombinator.com, then let me know and I'll continue."
Never output working notes, field status, or analysis to the terminal. Write everything to .temp/form-fill-status.md. Terminal output should be: one-line status + screenshots only.
Rules (never break these)
- Claude fills fields. Founder clicks buttons. No exceptions.
- Never click: Submit, Save changes, Save & return to application, or any button that changes form state.
- Batch-fill entire sections, then screenshot for review. Never fill one field, confirm, fill next. Fill the whole section, take a screenshot, ask: "Does this look right? Anything to change, or click [button name] to continue."
- Use the field selector map. Load
references/field-map.mdbefore filling any field. All textarea names, input names, and toggle IDs are pre-mapped. Do not discover them via trial and error. - If a field has a character limit and the drafted answer exceeds it, truncate and flag: "I truncated this to fit the [N]-char limit. Review the cut before continuing."
- Never fabricate a value. If the profile has
TBDfor a field, leave the field blank and flag it. - If the founder corrects an answer mid-fill, update the draft file and refill.
Form structure (Summer 2026)
The YC application has two layers:
- Main application at
apply.ycombinator.com/apps/[id]/edit- contains Founders, Founder Video, Company, Progress, Idea, Equity, Curious, Batch Preference - Founder Profile sub-pages at
apply.ycombinator.com/bio/[id]/edit- one per founder, contains Basics, Role & Responsibilities, Background, Social Media, Accomplishments
Fill founder profiles FIRST, then return to fill the main application.
Startup
1. Write a blank .temp/form-fill-status.md with today's date and "Status: starting"
2. Use browser_navigate to go to https://apply.ycombinator.com
3. Use browser_snapshot to check the page state
- If login screen: say "Log in at apply.ycombinator.com then let me know"
- If dashboard: navigate to the application edit URL from the FOUNDER_PROFILE
or find the active application link on the dashboard
4. Confirm you're on the application form (URL contains /apps/.../edit)
5. Tell the founder in one line: "Connected. Filling your profile first, then
main form. You click all save/submit buttons - I'll tell you which and when."
6. Load references/field-map.md before filling any fieldsFounder Profile(s) - fill first, one per founder
Navigate to each founder's profile via the "Edit profile" link on the Founders section.
Basics
- Name
- Age (dropdown)
- Phone number (country selector + number)
- Gender
- City (location autocomplete - type city name, select from dropdown)
Role & Responsibilities
- Title / main responsibility (CEO, CTO, etc.)
- Equity percent
- Technical founder: Yes/No
- Currently in school: Yes/No
- Exclusive commitment to this project if accepted: Yes/No
Background
- LinkedIn URL
- Education: add entries (school name, degree, dates)
- Work History: add entries (company, role, dates, description)
Social Media
- Personal website URL
- GitHub URL
- Twitter URL
Accomplishments
These are the highest-stakes fields in the founder profile. Fill carefully.
- "Please tell us about a time you most successfully hacked some (non-computer) system to your advantage." - the wildcard/hacker question. Specific, surprising, shows creative problem-solving outside software.
- "Please tell us in one or two sentences about the most impressive thing other than this startup that you have built or achieved." - PG calls this the most important question. Hard achievements with real results. Not the current startup.
- "Tell us about things you've built before." - apps, sites, OSS. Include URLs.
- "List any competitions/awards you have won, or papers you've published." - include patents, grants, press.
After filling all profile fields:
- Take screenshot
- Output: "Founder profile filled. Review above. Click 'Save & return to application' to continue."
Repeat for each additional co-founder.
Section: Founders (main form)
After returning to main application:
- "Who writes code, or does other technical work on your product? Was any of it done by a non-founder? Please explain." - be specific: name the founder(s), what they built, any contractor work
- "Are you looking for a cofounder?" - fill only if actively looking; leave blank if team is complete
- "How long have the founders known one another and how did you meet? Have any of the founders not met in person?" - appears when a second founder is on the application (confirmed). Single textbox covering all three sub-questions.
- "Please tell us about an interesting project or thing you have built or achieved together." - appears after co-founder accepts invite and completes profile. Include URLs.
After filling:
- Take screenshot
- Output: "Founders section filled. Review above. Scroll down to Founder Video."
Section: Founder Video
- File upload - founder must upload the video file themselves (Claude cannot upload files)
- Flag: "This requires a file upload - I can't do this part. Upload your 1-minute video here. Max 100MB. All founders should appear on camera."
- After founder uploads: "Founder video uploaded. Continuing to Company section."
Section: Company
Fill in order:
- Company name
- "Describe what your company does in 50 characters or less." - count chars, flag if over
- Company URL (skip if none)
- Demo: file upload - flag same as video: "Upload your demo here if you have one. Max 3 min / 100MB."
- "Please provide a link to the product, if any." - URL
- Login credentials for product link (skip if not needed)
- "What is your company going to make? Please describe your product and what it does or will do."
- "Where do you live now, and where would the company be based after YC?" - format: "City A, Country A / City B, Country B"
- "Explain your decision regarding location."
After filling:
- Take screenshot
- Output: "Company section filled. 50-char pitch: '[value]' ([N] chars). Review above."
Section: Progress
Fill in order:
- "How far along are you?" - current stage, what's shipped, user/revenue state
- "How long have each of you been working on this? How much of that has been full-time? Please explain."
- "What tech stack are you using, or planning to use, to build this product? Include AI models and AI coding tools you use." - list specific stack; explicitly mention Claude Code, Cursor, or other AI coding tools if used
- "Optional: attach a coding agent session you're particularly proud of." - .md or .txt file, 25MB max. Flag: "YC is asking for a Claude Code or Cursor session export. If you have a session transcript showing good AI-assisted work, upload it here. Use /export in Claude Code to get a transcript."
- "Are people using your product?" - Yes/No radio
- If Yes: reveals "How many active users or customers do you have? How many are paying? Who is paying you the most, and how much do they pay you?" - fill with specific numbers from profile
- "Do you have revenue?" - Yes/No radio
- If Yes: reveals three fields: a. 6-month revenue table (auto-labeled last 6 months). Fill one USD$ cell at a time, oldest first. Enter 0 for zero-revenue months. Confirm each cell before moving to next. b. "Where does your revenue come from?" - fill if multiple revenue sources; skip if single c. "Anything else regarding revenue or growth rate?" - fill if context matters (e.g. one-time grant, throttled growth, pilots closing soon)
- "If you are applying with the same idea as a previous batch, did anything change? If you applied with a different idea, why did you pivot and what did you learn from the last idea?" - fill only if reapplying; leave blank if first application
- "If you have already participated or committed to participate in an incubator, 'accelerator' or 'pre-accelerator' program, please tell us about it." - fill if applicable
After filling:
- Take screenshot
- Output: "Progress section filled. Review above."
Section: Idea
Fill in order:
- "Why did you pick this idea to work on? Do you have domain expertise in this area? How do you know people need what you're making?"
- "Who are your competitors? What do you understand about your business that they don't?"
- "How do or will you make money? How much could you make?"
- Category dropdown - select the closest match
- "If you had any other ideas you considered applying with, please list them." - list 1-3 alternatives; YC says they sometimes fund founders on ideas listed here, not the main one
After filling:
- Take screenshot
- Output: "Idea section filled. Review above."
Section: Equity
Fill:
- "Have you formed ANY legal entity yet?" - Yes/No
- If Yes: reveals two fields: a. "Please list all legal entities..." - free text. List each with type and country/state. E.g. "Delaware C Corp (incorporated Jan 2025), German GmbH (Mar 2025 for EU ops)." b. "Please describe equity ownership in percentages among founders, employees and stockholders." - free text, not a table. Format: "[Name] ([Title]) X%, [Name] ([Title]) Y%, option pool Z%." Pull founder equity from each founder's profile.
- "Have you taken any investment yet?" - Yes/No
- If Yes: reveals five fields: a. "List any investments received" - name, amount, valuation cap, type (convertible note / SAFE / stock), date. One investment per line. b. "How much raised total in USD?" - number only c. "How much money in the bank now?" - number only d. "How much do you spend per month?" - number only e. "How long is your runway?" - e.g. "5 months"
- "Are you currently fundraising?" - Yes/No
Equity percent per founder is captured in each founder's profile (Role & Responsibilities) and referenced here in the free-text equity description.
After filling:
- Take screenshot
- If equity split looks unusual (e.g. >70/30 between two founders): flag it. "Your equity split is [X/Y]. YC prefers roughly equal splits - worth reviewing before submitting."
- Output: "Equity section filled. Review above."
Section: Curious
Fill:
- "What convinced you to apply to Y Combinator? Did someone encourage you to apply? Have you been to any YC events?"
- "How did you hear about Y Combinator?"
After filling:
- Take screenshot
- Output: "Curious section filled. Review above."
Section: Batch Preference
Select: Summer 2026 OR A batch after Summer 2026
After filling:
- Output: "Batch preference set. All sections filled."
Pre-submit review
Before the founder submits:
Completeness check - before taking any screenshot, compare the FOUNDER_PROFILE block against every required field in this skill. Flag any field that is: (a) absent from the profile, (b) an empty string, (c)
TBD, or (d)N/Awhen the question is not optional. List each gap with the field name and section. Do not proceed to step 2 until the founder has resolved or explicitly accepted each gap.Required fields that must not be blank or TBD at submission:
pitch_50_char,product_description,how_far_along,working_duration,tech_stackwhy_this_idea,competitors,monetizationequity_description,legal_entitywhy_yc,how_heard- Each founder:
name,email,most_impressive_thing,who_writes_code
- Take screenshot of the top of the application
- Run final check:
- Any
TBDvalues that were never filled? Flag them. - 50-char pitch within limit?
- Founder video uploaded?
- Founder profile(s) complete?
- Any
- Output:
Pre-submit checklist:
[ ] 50-char pitch: [value] ([N] chars)
[ ] Founder video: [uploaded / MISSING]
[ ] Founder profiles complete: [yes / MISSING for whom]
[ ] Coding agent session: [uploaded / skipped]
[ ] Reapply question: [answered / N/A]
[ ] TBD fields remaining: [list or NONE]
If everything looks correct, click 'Submit application'.
I will not click Submit - that's yours.Error handling
- Field not found: Use browser_snapshot to re-read the page, try alternate selectors. If still not found, flag: "I can't find the [field name] field. Please click into it and tell me what you see."
- Character limit exceeded: Truncate to limit, flag exact cut point, ask founder to review.
- Login session expired: Tell founder to re-login and refresh - then resume from current section.
- Page changed unexpectedly: Take screenshot, describe what changed, ask founder how to proceed.
- Anti-bot block: Stop immediately. Tell founder: "The page may be blocking automated input. Try filling [field] manually or reload the page."
- File upload fields: Claude cannot trigger file uploads. Always hand these to the founder with exact instructions on what to upload and where.
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
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.

