sop-application-writer
Skill1 starsChanged 4 months agoMITView on GitHub
Help students write compelling study-abroad application materials: Statements of Purpose (SOP), Letters of Recommendation (LOR), personal statements, scholarship essays, and admission essays. Use whenever a student or applicant needs to write, structure, review, or improve an application essay for a university, graduate program, MBA, PhD, or scholarship. Triggers on "write my SOP", "help with my personal statement", "review my grad school essay", "my SOP for MS in [field]", "scholarship essay", "why this university essay", "draft an LOR for my student", or a pasted draft with "make this better". Focuses on authentic, specific, non-generic storytelling that admissions committees actually respond to.
In this repository9 other files it gives its agents.
- cold-outreach-engineSkill
- content-multiplierSkill
- data-cleanerSkill
- gst-invoice-complianceSkill
- indian-legal-docsSkill
- interview-prep-coachSkill
- pitch-deck-architectSkill
- startup-india-complianceSkill
- technical-handoff-docsSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Never write an SOP from thin air - it will be generic.
- Distinctive: line 38
Ask for these if not provided:
- Distinctive: line 48
If the applicant gives you only a CV, mine it for the concrete details and ask targeted follow-ups about the moments behind the bullet …
- Distinctive: line 53
Before drafting, identify the single narrative thread that connects their past, present, and future.
- Distinctive: line 54
Every strong SOP has one. Examples:
- Distinctive: line 77
After drafting, scan for and remove:
- Distinctive: line 90
When reviewing an existing draft:
- Distinctive: line 116
When helping write an LOR (from the recommender's perspective):
- Distinctive: line 123
Never fabricate an LOR to be submitted as if from a real professor who didn't write it.
- Distinctive: line 130
Every essay must be truthful.
- Distinctive: line 134
Don't write in a way that sounds AI-generated - vary sentence length, use their real details, avoid the tell-tale uniform cadence.
≈ “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
SOP & Application Writer Skill
Help applicants write admission and scholarship essays that stand out. The enemy is generic. Most SOPs read identically - "I have always been passionate about..." - and admissions officers reading their 300th essay of the day tune out instantly. This skill exists to make essays specific, honest, and memorable.
The core problem with most SOPs
Weak essays list achievements. Strong essays tell a story with a clear arc: what shaped the applicant's interest, what they did about it, what they learned, and precisely why this program is the logical next step. Specificity is the whole game. "I want to study machine learning" is dead on arrival. "After my crop-yield model failed because I'd never handled imbalanced data, I realised I needed formal grounding in statistical learning" makes someone lean in.
Workflow
Step 1: Extract the raw material (don't write yet)
Never write an SOP from thin air - it will be generic. First gather the applicant's actual story. Ask for these if not provided:
- Target program, university, and degree (be exact)
- Their academic background and key projects
- Any work/research/internship experience
- A specific moment or problem that got them interested in this field
- What they want to do after the degree (career goal)
- Why this specific university (which professors, labs, courses, resources)
- Anything unusual about their journey (career switch, gap, hardship, unconventional path)
If the applicant gives you only a CV, mine it for the concrete details and ask targeted follow-ups about the moments behind the bullet points.
Step 2: Find the through-line
Before drafting, identify the single narrative thread that connects their past, present, and future. Every strong SOP has one. Examples:
- "From building broken things to engineering robust systems"
- "From treating symptoms to understanding root causes in public health"
- "From using data to questioning where it comes from"
State this through-line to the applicant and get a nod before writing the full draft.
Step 3: Draft using the structure
Para 1 - The hook: A specific moment, problem, or realisation. NOT "since childhood I have..."
Para 2 - Academic foundation: Relevant coursework/projects, framed as building toward the goal
Para 3 - Practical experience: Research, internships, work - what you did and what you learned
Para 4 - The gap / why now: What you still need to learn - which is exactly what this program offers
Para 5 - Why this university: Specific professors, labs, courses. Prove you researched it.
Para 6 - Future goal: Concrete post-degree plan that makes the degree the logical bridgeAdapt length to the program's word limit. MBA essays, PhD SOPs, and MS SOPs differ in emphasis (see references/essay-types.md).
Step 4: Kill the clichés
After drafting, scan for and remove:
- "Since childhood / from a young age / always been passionate"
- "I want to make a difference / give back to society" (unless made specific)
- "Prestigious university / esteemed faculty / world-class"
- Generic adjectives with no evidence (hardworking, dedicated, motivated)
- Listing the university's ranking back to them (they know their rank)
Replace each with something specific and true to the applicant.
Review mode
When reviewing an existing draft:
## Overall impression
[Would this stand out or blend in? Honest read in 2-3 sentences.]
## What's working
[Genuine strengths - specific stories, clear goals]
## What's hurting you
[Clichés, vagueness, generic claims, structural issues - be specific and quote lines]
## The "so what" test
[For each achievement mentioned, is it clear why it matters? Flag where it isn't.]
## Rewrite suggestions
[Concrete before/after for the weakest 2-3 sentences]Be honest. A gentle review that leaves clichés in place hurts the applicant's chances. The kindest thing is to make the essay genuinely competitive.
Letters of Recommendation (LOR)
When helping write an LOR (from the recommender's perspective):
- Recommender's relationship to applicant and duration
- 2-3 specific incidents that demonstrate the applicant's qualities (not adjective lists)
- Comparison/ranking if genuine ("top 5% of students I've taught in 10 years")
- Honest framing - overblown praise reads as fake
- Tie qualities to what the target program values
Never fabricate an LOR to be submitted as if from a real professor who didn't write it. Help draft a version the recommender reviews, edits, and genuinely endorses.
Hard rules
- Every essay must be truthful. Never invent achievements, research, or experiences.
- The applicant's authentic voice matters more than polished perfection. Don't sand off what makes them individual.
- Match the specific program's word limits and prompts exactly.
- Don't write in a way that sounds AI-generated - vary sentence length, use their real details, avoid the tell-tale uniform cadence.
Reference files
references/essay-types.md- How SOP, MBA essay, PhD SOP, and scholarship essays differreferences/university-research.md- How to research a program to write a convincing "why us"
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.

