apply
Skill501 starsChanged 7 months agoMITView on GitHub
Help fill out a job application form. Generates personalized answers for every field using your profile and evaluation. Never auto-submits. Use when someone says 'help me apply', 'fill out this application', or 'application for'.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- priyansh1210/shirotheir own version, first seen Nov 8, 2026
- matthewwong525/WongStacktheir own version, first seen Nov 8, 2026
- galiprandi/job-seekertheir own version, first seen Nov 5, 2026
- hiddenjobs/job-search-mcptheir own version, first seen Nov 1, 2026
- ChadPapineau/espn-fantasy-football-mcptheir own version, first seen Nov 1, 2026
- ankul5/internship-hunt-skilltheir own version, first seen Nov 1, 2026
Used with
Projects with it also use hunt, Daily and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ninehillsSkillhunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.
Also in 3 projects that use this
kstonekuanSkillDaily
Documentation and capabilities reference for Daily
Also in 3 projects that use this
julienamorganSkillprofile
Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).
Also in 3 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 4 projects that use this
dazuckSkillinterview
Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.
Also in 4 projects that use this
AnthropicSkillinterview-prep
Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 1
Edited · 0
None found.
Wrote their own version · 24
- proficientlyjobs/proficiently-claude-skills★ 389same name
- galiprandi/job-seeker★ 120same name
- hiddenjobs/job-search-mcp★ 25same name
- 1carusalwayswa/apply★ 18same name
- kirkchen/beat★ 9same name
- iliasedelkin/jobissimo★ 8same name
- matthewwong525/WongStack★ 7same name
- qbeka/jev-job-search★ 5same name
- atharh/career-corpus-kit★ 4same name
- tydev-new/10xjobs-careercoach★ 3same name
14 more not listed
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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 13 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
CRITICAL: NEVER auto-submit an application: Always show the user every answer and get explicit confirmation before any form interaction.
- Very specific: line 24
Read data/profile.yml for structured background
- Very specific: line 25
Read data/resume.md for full resume text
- Very specific: line 27
Check data/research/{company}.md for company intel
- Very specific: line 28
Check data/resumes/ for a tailored resume file
- Distinctive: line 30
If no evaluation exists for this company:
- Distinctive: line 38
"Help me with this application": Ask which company/role, or if computer use is available, take a screenshot to identify the form
- Distinctive: line 71
Every claim must be backed by real experience from the profile
- Distinctive: line 83
Use STAR format from evaluation Block F stories
- Distinctive: line 87
Use target from profile, informed by Block D market data
- Distinctive: line 88
If range requested, give profile target range
- Distinctive: line 89
If single number requested, give midpoint of target range
- Distinctive: line 93
If not in profile, ask the user
- Distinctive: line 131
If computer use is available AND the user explicitly asks for help filling the form:
- Distinctive: line 142
If no computer use:
- Distinctive: line 148
After the user confirms submission:
- Very specific: line 149
Update data/applications.md: Status -> "Applied", Date Applied -> today
- Distinctive: line 150
Add note with any relevant details
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Application Form Assistant
Help fill out job application forms with personalized, honest answers.
CRITICAL: NEVER auto-submit an application. Always show the user every answer and get explicit confirmation before any form interaction. Always stop before any submit button.
Step 0: Load Context
- Read
data/profile.ymlfor structured background - Read
data/resume.mdfor full resume text - Find the relevant evaluation in
data/evaluations/ - Check
data/research/{company}.mdfor company intel - Check
data/resumes/for a tailored resume file
If no evaluation exists for this company:
"I haven't evaluated this role yet. Want me to evaluate the posting first? That gives me better context for your application answers."
Step 1: Identify the Application
Parse user input:
- Company/role name: Find the matching evaluation
- "Help me with this application": Ask which company/role, or if computer use is available, take a screenshot to identify the form
Step 2: Map Common Form Fields
Generate answers for standard application fields:
| Field | Source | How to Fill |
| Name / Email / Phone | profile.yml | Direct copy |
| Resume upload | Point to file | "Upload data/resumes/{file}.html (or PDF if you printed it)" |
| Cover letter | Generate below | Tailored to this role |
| "Why this company?" | Research + evaluation | Specific, referencing company details |
| "Why this role?" | Evaluation Block C + narrative | Connect background to role requirements |
| Years of experience | profile.yml | Honest number |
| Salary expectations | Evaluation Block D | Use target from profile, informed by market data |
| Work authorization | profile.yml visa_status | Direct answer |
| Willing to relocate | profile.yml work_preference | Direct answer |
| Start date | Ask user | "When can you start?" |
Step 3: Cover Letter (when needed)
Structure:
- Opening: Specific hook about the company (NOT "I'm excited to apply")
- Bridge: How your specific background connects to their specific need
- Evidence: 2-3 concrete accomplishments from your experience relevant to this role
- Close: Forward-looking, confident but not presumptuous
Rules:
- 250-350 words
- Match JD language and keywords
- Match company tone (formal for law firms, conversational for startups)
- Reference specific details from research (if available)
- Every claim must be backed by real experience from the profile
Step 4: Handle Custom Questions
For each custom application question:
Short answer (< 500 chars):
- Draw from evaluation blocks, profile, or research
- Be specific, not generic
- Include a number or concrete detail when possible
"Tell me about a time..." (behavioral):
- Use STAR format from evaluation Block F stories
- Match the most relevant story to the question
"What are your salary expectations?":
- Use target from profile, informed by Block D market data
- If range requested, give profile target range
- If single number requested, give midpoint of target range
Yes/No questions (authorization, relocation, etc.):
- Answer directly from profile data
- If not in profile, ask the user
EEO / demographic questions:
- Tell the user these are optional and legally cannot affect their candidacy
- Let them answer themselves
Step 5: Present All Answers
Show EVERY generated answer before any action:
## Application Answers: {Company} - {Role}
**Cover letter:**
{full text}
**"Why this company?"**
{answer}
**"Why this role?"**
{answer}
**Salary expectations:** {answer}
**Custom questions:**
1. "{question}" - {answer}
2. "{question}" - {answer}
---
Review these answers. You can:
- Ask me to revise any answer
- Copy them into the application form
- Tell me to adjust the toneStep 6: Computer Use Assistance (only if available and user requests)
If computer use is available AND the user explicitly asks for help filling the form:
- Navigate to the application page
- Fill each field with the APPROVED answers only
- Upload resume file if the form accepts it
- STOP before the Submit button. Take a screenshot. Say:
"Everything is filled in. Please review the form carefully and click Submit when you're ready. I won't click it for you."
If no computer use:
"Copy the answers above into the application form. Let me know when you've submitted and I'll update your tracker."
Step 7: Update Tracker
After the user confirms submission:
- Update
data/applications.md: Status -> "Applied", Date Applied -> today - Add note with any relevant details
"Tracked! Your application to {company} is logged. I'll remind you to follow up if you haven't heard back in a week."
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.

